Authorize.net

Authorize.net

Authorize.Net is an online payment service that offers comprehensive security measures for users and businesses of all sizes, ensuring maximum protection of sensitive data and reliable uptime when handling transactions. It goes above and beyond with its range of features, like recurring billing solutions to suit the needs of merchants offering subscription services, mobile compatibility, and integration options with popular e-commerce platforms. All these features work together to provide a seamless payment processing experience.

Payment Processor Comparison

When it comes to selecting the best payment processor for your business, Stripe, PayPal and Authorize.net are all top contenders. 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 providing reliable and secure payment processing services. 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 recommended to compare each processor's features, fees, and support options before deciding.

Please 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. In addition, multiple currencies are supported through this service, making it a great option for international merchants as well. To confirm that Authorize.net will work for your business, make sure you visit their website to read up on what browsers support their services before you proceed to incorporate the platform into your business operations.

List of supported and tested browsers

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​

Utilize 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/version which could cause incompatibility issues. For this reason, we recommend updating to a newer version or switching to a supported brand of browser.

Examples of Outdated browsers:

Internet Explorer (IE) 11

Edge (Legacy)

Opera

Browser Block/Out of Date

In the event that 'Browser Block/Out of Date' is displayed, Authorize.net has encountered benchmarked issues with the currently used version, and require that a newer version is used or a different type of supported digital system is employed.

How to integrate Authorize.Net as a Payment Gateway

1. Once you are 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. Click Here for more details on Sandbox vs. Live Mode in Authorize.Net.
2. Then you can proceed to Payments in 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. \

Sandbox And you can input the Sandbox API Keys in the Sandbox Fields.

Save Button Once inputting the desired API Keys, click on the Save Button.

3. Default Payment Gateway 

It will show you a quick prompt asking whether you want to make Authorize.Net your Default Payment Gateway. Clicking on Cancel will still integrate Authorize.Net, but it will not make it the Default Gateway. Clicking on Confirm will integrate Authorize.net and make it the Default Payment Gateway.

Please 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

Side 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/pending transactions with Stripe, they will continue to run as is until the Stripe connection is in place. We encourage you to not disconnect any gateway. Defining the default gateway will run new transactions through the desired choice and keep the existing subscriptions running through Stripe and PayPal integrations in place.

Please Note: You need to make use of this feature.

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 (JCB)

38000000000006 (Diners Club/ Carte Blanche)

FAQ

Why don't I see Paypal among the default gateway options?

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. 

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

There will be no change in the reporting of Orders/Subscriptions/Transactions. All the payments done via Authorize.net will be available under Payments ➝ Transactions.

Also, there will be no change in the functioning of workflow triggers/attribution associated. All the functionalities will work the same with Authorize.net.

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.

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 - 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 canceled 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 which are created on Authorize.net. Cancellation of subscriptions for Stripe and PayPal will be added soon.

The following flow describes the handling of subscription statuses and payment retry logics 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 for the subscription and will move to "Expired" after the completion of payments.
• If the credit card expires for the end customer in the middle of the subscription, or the payment requires authentication from the end customer, or for any reason the last payment didn't go through successfully, the status will move over 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." Else will stay with "Unpaid" status.
• The subscription status will move to "Expired" after all the retries have been made for the last transaction.
• If the merchant disconnected the gateway account and there is an ongoing subscription, the transaction cannot be processed; hence the subscription will move to unpaid. The retry attempts will continue according to the retry logic.

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

Subscriptions created using Authorize.net can be canceled within the Subscriptions page using the 'Cancel Subscription' Action.

We do not create subscriptions using the Automatic Recurring Billing of Authorize.net; hence only charges corresponding to a subscription, in the transaction will be visible in the merchant portal.

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

No, we do not have the refund functionality within the application. You should use the merchant portal for refunding transactions.

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?

Yes, If you are holding transactions submitted on order forms for review based on any FDS filters. In that case, your transaction will be held for review (or declined as per the setting that you have configured) and will be visible in your merchant portal. Additionally, the corresponding status will be updated on the Transactions page. When you approve or decline the transaction.

In the case of recurring invoice payments/calendar appointment booking payments, we treat the transaction as declined and do not book the calendar appointment or schedule the auto payment, since it introduces complications as to when the payment will be approved by the business owner.

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

As the next step, 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.