Authorize.Net is an online payment service with comprehensive security features for users and businesses of all sizes, keeping sensitive data protected and ensuring reliable uptime during transactions. It covers a solid range of features including recurring billing for subscription services, mobile compatibility, and integrations with popular e-commerce platforms, all working together to keep payment processing smooth.

How To Integrate Authorize.Net As A Payment Gateway

To get started, navigate to the Payment section in your CRM, and visit the integrations tab, there you will find the Authorize.net option, click Connect to get started.

Make sure you are using a supported browser and that you are operating from within one of the supported countries, you will need to acquire Live and Sandbox API keys from Authorize.net. For sandbox API keys, log into the sandbox Merchant Interface. For Live API keys, log into the Live Merchant Interface.

Proceed to Manage Payment Integrations, and drop the 3 API Keys you got from your Merchant Interface in Authorize.Net. You can input the Live API Keys in the Live fields and click on Save.

You can also input the Sandbox API Keys in the Sandbox Fields. Once you've inputted the desired API Keys, click on the Save Button.

Default Payment Gateway

Clicking on Set as Default will integrate Authorize.net and make it the Default Payment Gateway.

NOTE: You are not required to disconnect Stripe to connect to Authorize.net. You can connect to both gateways on the integrations page. However, since you have connected two different gateways for processing payments, you will need to define a default gateway for processing payments. PayPal will continue to function alongside Authorize.net/Stripe in order forms, whichever is set as the default.

Payment Processor Comparison

When it comes to selecting the best payment processor for your business, Stripe, PayPal and Authorize.net are all strong options. Here's a comparison:

Stripe: A popular choice for online businesses and startups, Stripe offers a developer-friendly platform, custom integrations, and transparent pricing.

PayPal: PayPal is a well-established payment processor with a global presence and a wide range of features, including a secure payment gateway, invoicing, and recurring payments.

Authorize.net: Authorize.net is a trusted payment processor with a long history of reliable and secure payment processing. It offers comprehensive features including fraud detection and mobile compatibility.

Ultimately, the best choice depends on the specific needs of your business, such as the types of payments you need to accept, your target market, and your budget. It's worth comparing each processor's features, fees, and support options before deciding.

NOTE: The data for fees is accurate as of when this article is being published, for more information please check out the Pricing pages of the three options listed:

  • Stripe
  • Paypal
  • Authorize.net

Requirements To Use Authorize.Net

Authorize.net is a payment gateway solution that can be used to process transactions from U.S., Australian, and Canadian merchants. Multiple currencies are supported as well, making it a viable option for international merchants. To confirm Authorize.net will work for your business, visit their website to check which browsers support their services before incorporating it into your operations.

List Of Supported and Tested Browsers

Browser NameRecommend VersionChromev80 or higherEdge (Chromium)v85 or higherFirefoxv78 or higherSafariv12 or higher

You can check and verify the browser and version you are using by using the below help/about information when inside the respective browser:

  • Chrome​
  • ​Edge​
  • ​Firefox​
  • ​Safari​

Utilise sites like:

  • ​https://www.whatsmybrowser.org/​
  • ​https://www.whatismybrowser.com/​

For the Merchant Interface inside Authorize.net, if an unsupported browser or version is detected, two possible messages may display depending on how low the browser version is.

Browser Warning/Out Of Date

If your browser shows 'Browser Warning/Out of Date', it may have detected a browser or version that could cause compatibility issues. We recommend updating to a newer version or switching to a supported browser.

Examples Of Outdated Browsers

  • Internet Explorer (IE) 11
  • Edge (Legacy)
  • Opera

Browser Block/Out Of Date

If 'Browser Block/Out of Date' is displayed, Authorize.net has encountered benchmarked issues with the currently used version and requires a newer version or a different supported browser.

Important Notes For Using Authorize.Net

If Authorize.net is connected and set as the default gateway, other product areas like memberships and SAAS payment links will continue to process payments using Stripe.

If there are recurring subscriptions or pending transactions with Stripe, they will continue to run as they are until the Stripe connection is in place. We encourage you not to disconnect any gateway. Defining the default gateway will run new transactions through your chosen option and keep existing subscriptions running through the Stripe and PayPal integrations.

Test Cards For Authorize.net Integration.

Expiry Date can be any future date, and any 3/4 digits value can be the CVC:

  • 4007000000027 (Visa)
  • 4012888818888 (Visa)
  • 4111111111111111 (Visa)
  • 370000000000002 (American Express)
  • 5424000000000015 (Mastercard)
  • 2223000010309703 (Mastercard)
  • 2223000010309711 (Mastercard)
  • 6011000000000012 (Discover)
  • 3088000000000017 (JC😎
  • 38000000000006 (Diners Club/ Carte Blanche)

FAQ

Q: Why don't I see PayPal among the default gateway options?

  • A: You can connect to Paypal and use it as a payment method alongside a credit card payment method using Stripe/Authorize.net. This means the default has to be chosen among Stripe/Authorize.net when connected. PayPal can be used independently and alongside credit card payment methods on order forms.

Q: What will change in the reporting of transactions done with Authorize.net? Where will I be able to keep track of all payments?

  • A: There will be no change in the reporting of Orders/Subscriptions/Transactions. All payments made via Authorize.net will be available under Payments ➝ Transactions. There will also be no change in the functioning of workflow triggers or attribution. All functionalities will work the same with Authorize.net.

Q: Where will I be able to find the subscriptions created via Authorize.net? I cannot relate to the subscription status defined on the Subscriptions page.

  • A: All subscriptions created on the order forms can be tracked under Payments ➝ Subscriptions.

The following list represents subscription statuses and their inferences:

  • Pending - When held for merchant review due to FDS
  • Trial - Subscription is in trial mode
  • Active - The last payment was made, and there is an upcoming payment as well
  • Expired - All the subscription payments have been completed, and the subscription no longer exists
  • Canceled - The subscription was cancelled by the merchant using the Cancel action, and no further payments are to be processed.
  • Unpaid - The last payment for the subscription was not paid successfully. The subscription is still ongoing, but the final payment has not been made successfully.

Cancellation will be possible for the subscriptions according to the status:

Cancel Action is provided only against those subscriptions that are created on Authorize.net. Cancellation of subscriptions for Stripe and PayPal will be added soon.

StatusCancelPendingNoTrialYesActiveYesExpiredNoCanceledNoUnpaidYes

The following flow describes the handling of subscription statuses and payment retry logic in case of a subsequent payment failure:

  • If the first subscription payment is successful while purchasing the subscription on the order form, the subscription will move into the active state
  • It can also move into the trial status if there is a trial period attached to the recurring product
  • The subscription will remain active until every recurring payment is made successfully and will move to "Expired" after all payments are complete.
  • If the credit card expires for the end customer during the subscription, or the payment requires authentication from the end customer, or for any reason the last payment doesn't go through successfully, the status will move to "Unpaid."
  • The payment will be attempted two more times after 24 hrs each. The status will remain "Unpaid."
  • The subscription will remain in the Unpaid state and will attempt the following subsequent transactions, each with two retries.
  • The next subsequent payment will also be attempted, and if any payment becomes successful, the subscription will move into "Active." Otherwise it will stay as "Unpaid."
  • The subscription status will move to "Expired" after all retries have been made for the last transaction.
  • If the merchant disconnects the gateway account and there is an ongoing subscription, the transaction cannot be processed and the subscription will move to unpaid. The retry attempts will continue according to the retry logic.

Q: How do I Cancel/End a subscription created via Authorize.net? I am not able to do so in the merchant portal.

  • A: Subscriptions created using Authorize.net can be cancelled within the Subscriptions page using the 'Cancel Subscription' Action.
  • We do not create subscriptions using the Automatic Recurring Billing of Authorize.net, so only charges corresponding to a subscription will be visible in the merchant portal.

To confirm the cancellation, click the Yes, Cancel button.

Q: Will I be able to refund transactions as well within the application itself?

  • A: No, refund functionality is not available within the application. You should use the merchant portal for refunding transactions.

Q: I am using FDS filters with Authorize.net to hold transactions for review if the address is not submitted or the card code is not submitted etc. Is the system compatible with handling those cases?

  • A: Yes. If you are holding transactions submitted on order forms for review based on FDS filters, your transaction will be held for review (or declined as per the setting you have configured) and will be visible in your merchant portal. The corresponding status will also be updated on the Transactions page when you approve or decline the transaction.
  • In the case of recurring invoice payments or calendar appointment booking payments, we treat the transaction as declined and do not book the calendar appointment or schedule the auto payment, as this could introduce complications around when the payment will be approved by the business owner.

Q: When will Authorize.net be available for SaaS and Memberships?

  • A: We are working towards enabling Authorize.net integration in the Memberships area this quarter. Please vote on the ideas board for enabling this integration for selling SaaS.