Connect Authorize.Net for payment processing
Connect Authorize.Net in JourneyCARE to accept card payments for invoices, order forms, subscriptions, and membership checkouts. Authorize.Net supports merchant transactions for organizations in the United States, Australia, and Canada.
Get your Authorize.Net API keys
Get the Live and Sandbox API keys you plan to connect from the corresponding Authorize.Net Merchant Interface before opening JourneyCARE.
Open the Live Authorize.Net Merchant Interface to obtain your Live API keys.
Open the Sandbox Authorize.Net Merchant Interface to obtain your Sandbox API keys.
Connect Authorize.Net in JourneyCARE
Use Payments > Integrations to add the three API keys to the matching Live or Sandbox fields.
In JourneyCARE, go to Payments > Integrations.
Enter the three Live API keys in their corresponding Live fields, or enter the three Sandbox API keys in their corresponding Sandbox fields.
Click Save.
Choose whether to make Authorize.Net the default payment gateway. Select Cancel to connect Authorize.Net without making it the default, or select Confirm to connect it and make it the default.
You can connect Stripe and Authorize.Net at the same time. When multiple gateways are connected, you must define a default gateway for payment processing. PayPal can function on order forms alongside whichever default card gateway you choose.
Use Authorize.Net payments after connecting
Review Authorize.Net activity, manage order-form subscriptions, cancel eligible Authorize.Net subscriptions, and issue refunds from the Payments area.
Transactions: Open Payments > Transactions to view transaction reporting and issue refunds.
Order-form subscriptions: Open Payments > Subscriptions to track subscriptions created on order forms.
Authorize.Net subscription cancellation: On the Subscriptions page, use Cancel Subscription for subscriptions created with Authorize.Net. The action is available for Trial, Active, and Unpaid subscriptions; it is not available for Pending, Expired, or Canceled subscriptions.
Understand FDS review and recurring payment behavior
FDS rules can place order-form transactions on hold for review or decline them according to the settings configured in Authorize.Net. Held transactions are visible in the Authorize.Net Merchant Interface, and their status is updated on the Payments > Transactions page after approval or decline.
Recurring invoice payments and calendar appointment booking payments are treated as declined when they are held for review. JourneyCARE does not book the calendar appointment or schedule the automatic payment in that case.
For a recurring subscription, a successful first payment moves the subscription to Active, or to Trial when the recurring product includes a trial period. A later failed payment moves the subscription to Unpaid; this can happen when a card expires, customer authentication is required, or the payment does not go through.
JourneyCARE attempts the failed payment two more times at 24-hour intervals while the subscription remains Unpaid.
Each subsequent transaction also receives two retries. If a later payment succeeds, the subscription returns to Active; otherwise, it remains Unpaid.
After all retries for the last transaction are exhausted, the subscription moves to Expired.
If the connected gateway is disconnected while a subscription is ongoing, its transaction cannot be processed. The subscription moves to Unpaid and continues through the documented retry behavior.
Check feature requirements
Upgrade to Funnels version 2 to use this feature. Authorize.Net is available for membership checkouts and for SaaS v2 functionality.