Authorize.Net offers a powerful online payment solution that ensures sensitive customer data is protected while maintaining reliable uptime for transactions of all sizes. This service stands out for its extensive features, including recurring billing to support subscription-based merchants, mobile compatibility, and seamless integration with major e-commerce platforms. These tools work together to ensure a smooth payment experience for both the merchant and customer.
Comparing Popular Payment Processors: Stripe, PayPal, and Authorize.Net
When evaluating payment processors, consider key factors like security, integration, and pricing. Here is a comparison of three prominent processors:
Stripe: A favorite for online businesses and startups, Stripe is known for its developer-centric tools, easy integrations, and transparent fee structure.
PayPal: As a globally recognized brand, PayPal offers a secure payment gateway, invoicing capabilities, and options for recurring payments.
Authorize.Net: A long-standing player in the payment processing space, Authorize.Net provides reliable and secure transaction handling, fraud prevention tools, and mobile support.
Ultimately, your choice will depend on the specific needs of your business, such as the types of transactions you handle, your target audience, and your budget. Always compare features and fees across providers to ensure the best fit.
Requirements for Using Authorize.Net
Authorize.Net is available for merchants based in the U.S., Canada, and Australia. It supports multiple currencies, making it a strong option for international merchants. To ensure your system works smoothly with Authorize.Net, confirm that your browser is compatible by referencing the supported versions.
Supported Browsers for Authorize.Net
You can verify your browser version by visiting these helpful tools:
If you’re using an outdated browser version, you may see warnings such as “Browser Out of Date” or “Browser Blocked.” To avoid compatibility issues, upgrade to the latest browser version.
How to Set Up Authorize.Net as a Payment Gateway
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.
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.
Important Note: There is no need to disconnect Stripe in order to connect Authorize.net. Both payment gateways can be connected simultaneously from the integrations page. However, with two gateways linked for payment processing, you will need to set one as the default. PayPal will continue to work alongside Authorize.net or Stripe in your order forms, depending on which gateway is chosen as the default.
Completing the Authorize.Net Integration
After entering the required API keys, click the “Save” button. A prompt will appear asking if you would like to set Authorize.Net as your default payment gateway. If you choose “Cancel,” the integration will still be active, but Authorize.Net won’t be the default gateway.
Notes on Using Authorize.Net with Other Payment Gateways
If Authorize.Net is selected as your default gateway, it will process payments for areas like memberships or SaaS payment links. Any ongoing subscriptions or pending transactions through Stripe will continue unaffected as long as the Stripe connection remains active. For testing purposes, you can use the following test cards:
Visa: 4007000000027, 4012888818888, 4111111111111111
American Express: 370000000000002
Mastercard: 5424000000000015, 2223000010309703
Discover: 6011000000000012
Expiration dates can be any date in the future, and any 3- or 4-digit CVC value can be used.
Frequently Asked Questions About Authorize.Net
Why is PayPal not listed as a default gateway option?
Although PayPal can be integrated with Authorize.Net and Stripe, a default gateway must be selected between Stripe and Authorize.Net for credit card transactions. PayPal will still function alongside these gateways as a separate payment method.
How will Authorize.Net transactions appear in my reports?
Transactions processed through Authorize.Net will be visible in the "Payments ➝ Transactions" section of your dashboard. No changes are made to existing transaction reports.
Where can I find subscriptions created via Authorize.Net?
Subscriptions processed through Authorize.Net are listed under "Payments ➝ Subscriptions." Subscription statuses include:
Pending: Held for merchant review.
Trial: In the trial period.
Active: Payment received, and the next one is scheduled.
Expired: All payments have been made, and the subscription has ended.
Canceled: Subscription was canceled, and no further payments will be processed.
Unpaid: The last payment was unsuccessful, and the subscription is still active but pending resolution.
Subscription Management and Payment Status
The table below details which subscription statuses allow cancellations:
Subscriptions will attempt payment retries twice after each failed transaction. If a payment goes through, the subscription moves back to “Active”; otherwise, it will remain in “Unpaid” status until all retries fail, at which point it will expire.
How to Cancel Authorize.Net Subscriptions
You can cancel subscriptions created through Authorize.Net by using the "Cancel Subscription" action on the Subscriptions page. Refunds must be processed through the Authorize.Net Merchant Portal, as this functionality is not available within the application.
Upcoming Authorize.Net Features for SaaS and Memberships
We are actively working on enabling Authorize.Net for SaaS and membership areas. This integration is expected to be available later this quarter. To support this development, you can vote for it on our ideas board.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article