New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Payment Methods


  • Payment Methods Overview
  • Cards
  • Direct Debit
  • Bank Based Payments
  • Wallets
  • Vouchers
  • Articles and FAQ

Payment Gateways and Configuration


  • Payment Gateways Overview
  • Chargebee Test Gateway
  • Stripe
  • PayPal Payment Services
  • Chargebee Pay
  • Adyen
  • Authorize.net
    • ACH Payments via Authorize.Net
    • Authorize.net Direct Integration
    • Authorize.net via Spreedly
  • Bambora (formerly Beanstream)
  • Bank of America
  • BluePay
  • BlueSnap
  • Braintree
  • Checkout.com
  • CyberSource
  • dLocal
  • EBANX
  • Ecentric
  • Elavon
  • E-xact Direct Integration
  • eWay Rapid
  • Global Payments
  • GoCardless
  • J.P. Morgan Mobility Payment Solutions
  • Metrics Global
  • Mollie
  • Moneris
  • Network Merchants Incorporated (NMI)
  • Nuvei
  • Orbital (Chase Paymentech)
  • Pay.com
  • Paymill
  • Paystack
  • Pin Payments
  • QuickBooks Payments
  • Razorpay
  • Sage Pay
  • Solidgate
  • Twikey
  • Windcave
  • Worldline Online Payments(formerly Ingenico)
  • Worldpay
  • Articles and FAQ

Level 2/3 Data Support


  • Level 2/3 Data Support

Advanced Routing


  • Advanced Routing

Dunning


  • Dunning
  • Articles and FAQ

Offline Checkout


  • Offline Checkout
  • Articles and FAQ

Transaction Sync & Invoice Mapping


  • Transaction Sync and Invoice Mapping

Fraud Management


  • Fraud Management

Error Handling


  • Errors with Root Cause and Troubleshooting

Payment Lifecycle Logs


  • Payment Intents
  • Transactions
  • Gateway Activity Logs
  • Gateway Webhook Logs
  • Articles and FAQ

Others


  • Reach (Merchant of Record)
  • Payment Verification
  • Bulk Deletion of Payment Methods
  • Custom Payment Methods
  • Payment Initiator Parameter
  • PSD2 and Strong Customer Authentication
  • RBI e-Mandate
  • RBI Tokenization Regulations
  • Chargeback Management
  • Transaction Descriptors
  • Payment Preferences
  • Visa Trial Rules
  • Mastercard Trial Rules
  • Co-badged Card Compliance
  • Articles and FAQ
  1. Payments
  2. Payment Gateways and Configuration
  3. Authorize.net
  4. Authorize.net via Spreedly
  1. Payments
  2. Payment Gateways and Configuration
  3. Authorize.net
  4. Authorize.net via Spreedly

Authorize.net via Spreedly

Authorize.net via Spreedly is now deprecated. Existing users can continue using the integration without interruption. However, new onboarding is no longer available.

Alternatively, you can explore the native Authorize.net integration.

If you want to migrate your existing Authorize.net via Spreedly setup to the Authorize.net Direct Integration, reach out to Chargebee support team.

Authorize.Net is a payment processing solution that simplifies online payments and provides the complex infrastructure and security necessary to ensure fast, reliable, and secure transmission of transaction data.

Authorize.Net allows you to choose between its merchant account plus payment gateway plan or its payment gateway only plan.

Choosing Authorize.Net

Consider the following factors before choosing Authorize.Net as a payment solution:

  • Countries: Authorize.Net is currently available for companies based in the United States, Canada, the United Kingdom, Europe, and Australia.
  • Payment methods: Authorize.Net supports major credit and debit cards such as Visa, MasterCard, American Express, Discover, Diner's Club, JCB, and more.
  • Pricing: Authorize.Net has service fees which include setup, monthly, and per-transaction fees. More details about pricing here.

Note

3D Secure is not supported for this integration.

Types of Account

Authorize.Net is supported only on Chargebee's live site. You would require a payment gateway account or a payment gateway plus merchant account.

Since Chargebee handles card information storage and recurring payments, you would not require the CIM(Customer Information Manager) and ARB(Automated Recurring Billing) modules in your Authorize.Net account.

If you plan on using Authorize.Net with Chargebee but would want to test the workflow, you can make use of Chargebee's test payment gateway.

Prerequisite

  • Chargebee currently uses Spreedly, a third party card vault, to store card information with Authorize.Net. However, if you're integrating with Chargebee via Spreedly, you need to migrate your card information from Authorize.Net to Spreedly. Contact Chargebee support for more information on the migration process.
  • Fraud settings such as Address Verification Service and Card code verification are not supported in this integration via Spreedly and these settings must be disabled on your Authorize.net Merchant account.

Due to recent world events, you may experience failures for payments originating from Russian financial institutions or instruments. We recommend reviewing guidelines issued by respective payment gateways for additional information.

Integration Options

Authorize.Net can be integrated with Chargebee only on the LIVE site. Testing with Authorize.Net is discussed in later sections.

Chargebee offers the following options to integrate with Authorize.Net:

Option A Chargebee's hosted payment pages + Authorize.Net Gateway

In this method the card information of the customers are collected by Chargebee's secure hosted pages and passed on to Spreedly for storage.

PCI Compliance Requirements: Low

Your PCI compliance requirements are greatly reduced because of Chargebee's hosted pages. As a merchant using Chargebee's hosted pages, all you have to do is fill a Self Assessment Questionnaire (SAQ-A) and submit it to the payment gateway, if requested.

Option B Chargebee's API + Authorize.Net Gateway

In this method, collecting card information will have to be handled at your end and has to be passed on to Chargebee. Chargebee then routes this card information to Spreedly.

PCI Compliance Requirements: High

Since card information will be collected by you directly, you will have to take care of PCI Compliance requirements.

Configuring Authorize.Net

Configuring Authorize.Net with Chargebee involves setup in both your Chargebee and Authorize.Net accounts.

Follow these steps to setup Authorize.Net on Chargebee's live site:

Step 1: In your Chargebee LIVE Site, go to Settings > Configure Chargebee > Payment Gateways > Add a Gateway > Authorize.net.

Step 2: Enter your API Login Id, Transaction Key and Public Client Key and click Connect. You have now configured Authorize.net.

Step 3: Enable the necessary Card settings by clicking the Manage link in the Cards section.

Additional Configurations in Authorize.Net

Apart from the configuration in Chargebee, the following details have to be configured in your Authorize.Net account as well:

Turn off Test Mode

Authorize.Net has a Test Mode in its production account which lets you test your connection with the payment gateway without carrying out actual charges. By default, your payment gateway account is set to "Test Mode". To carry out live transactions, ensure your Live Mode is turned on. To do this, in your Authorize.Net account, navigate to Account > Settings > Security Settings > General Security Settings and set the mode to Live as shown below:

image

Testing Authorize.Net with Chargebee

Authorize.Net can be integrated with Chargebee only on Chargebee's live site. If you are on Chargebee's test site and want to run test transactions, you can make use of Chargebee's test payment gateway. Chargebee's test gateway is designed to simulate all payment related scenarios. Test cards for testing with Chargebee's test gateway can be found here.

The following test credit card numbers will only work in the Authorize.Net's sandboxenvironment.

 Card Type

 Card Number

 Expiry Date 

  Security Code** **

American Express

 3700 000000 00002

Any expiration date after today's date

Any 4-digit combination

 Visa

 4111 1111 1111 1111

Any expiration date after today's date

Any 3-digit combination

For more card number detials, see Test Card Numbers

Currencies supported

Authorize.Net and Chargebee support different currencies for charging customers across different geographical locations. If you intend to use Authorize.Net+Chargebee for your business, ensure that your transactional currencies are supported by both.

Find the complete list of currencies supported by:

  • Chargebee
  • Authorize.Net

Information

The currency configured in your Authorize.Net account will be used for transactions, irrespective of the currency configured in Chargebee. Hence, ensure the currency configured in your Authorize.Net account matches with that of your Chargebee account.

FAQ

1) Is it possible to save customer card information in Auth.Net vault instead of Spreedly?

Chargebee supports storing cards in Auth.Net's vault. However, after integrating Auth.Net with Chargebee, your customer's card details would be stored in Spreedly's vault by default. To store them in Auth.Net's vault, contact support.

Articles & FAQs

What if I have issues with the migrated cards data from Spreedly to Authorize.net?
Can I continue to use the Authorize.net integration Spreedly?
How long will the migration of cards from Spreedly to Authorize.net take?

Was this article helpful?