How to Setup Authorize.Net With Your BigCommerce Store
Last Updated on August 17, 2026 by Dimitri Akhrin
Connect Authorize.Net to Your BigCommerce Store
An Authorize.Net BigCommerce setup connects your online store to a payment gateway so customers can submit card payments at checkout. Visa provides a helpful overview of how payment processing works across merchants, acquirers and issuers.
BigCommerce is one of the top eCommerce platforms currently available and is the #1 enterprise cloud solution for companies doing $1 million or more annually. Based on that success it’s no surprise that BigCommerce is specifically designed to make it as easy as possible to integrate leading payment gateways, including Authorize.Net.
PayPal Powered by Braintree is BigCommerce’s default gateway, so to use Authorize.Net you’ll have to manually change over. Don’t worry, it’s extremely easy. Follow the three simple steps listed below to launch BigCommerce’s setup function and enable your store to accept credit card payments via Authorize.Net.
Current interface note: BigCommerce has updated its payment settings since this article was first published. The current interface directs merchants to Settings > Payments to locate Authorize.Net. The steps below preserve the original setup instructions, so your current dashboard may use different menu labels.
Connect Authorize.Net to BigCommerce through payment settings, gateway configuration and account credentials.
Three Steps to Configure Your Payment Gateway
Step One: In your BigCommerce dashboard go to the “store setup” tab in the left sidebar, and then select “payments.”
The payments page will provide access to the settings for all payment types, including the default gateway, offline (in-store) payment methods, additional online methods and digital wallets.
Step Two: Click the “Online Payment Methods” tab.
Selecting this tab will open a dropdown list with a full alphabetical list of all the payment gateways and online processors that BigCommerce integrates with, including Authorize.Net.
Step Three: Find the Authorize.Net line and click the “Set Up” button on the far-right.
This will open the Authorize.Net settings page. Clicking “get started now” begins the setup process. BigCommerce will supply a set of simple instructions to guide you through the process. You will then enter the relevant information to connect your Authorize.Net account.
Information Needed for the Connection
Setting up Authorize.Net payments with your BigCommerce store will require the following pieces of information:
Display Name: The display name determines how the payment method will appear at checkout. You can leave it as “Authorize.Net,” but to provide clarity to your customers, it’s recommended to set it to something like “credit/debit.”
Merchant ID: This is the identifier for your merchant account. This will either have been assigned by Authorize.Net or, for businesses with their own outside merchant accounts that have been set up to integrate with Authorize.Net, this ID will be assigned by the merchant account provider.
Username/Password: You will need your Authorize.Net login to maintain an active connection. Incorrect login details will cause transactions to fail upon attempted payment.
Transaction Key: If checkout errors occur, you may need to generate a new transaction key. You can generate a new transaction key through Authorize.Net’s merchant portal. Full instructions are available via BigCommerce support.
Current credential note: BigCommerce’s current Authorize.Net setup lists Display Name, API Login ID, Transaction Key and Payment Gateway ID as its general settings. These labels differ from some of the older fields above. Authorize.Net explains that the API Login ID and Transaction Key authenticate payment gateway requests. Review the Authorize.Net API documentation before entering or regenerating these credentials.
Keep Your Gateway Credentials Secure
Connect Authorize.Net to BigCommerce through payment settings, gateway configuration and account credentials.
Treat your API Login ID and Transaction Key as sensitive account information. Limit access to people who need the credentials for the integration. The PCI Security Standards Council provides merchant resources for protecting payment data and maintaining a secure payment environment.
Once you complete the account setup, you can change or manage your settings at any time through the same Authorize.Net panel, and, if you enter the correct login information, you can also launch the Authorize.Net merchant portal directly within BigCommerce.
If you don’t yet have a merchant account and are in search of the right electronic payments solution for your company, contact BAMS today and speak to one of our experts about how we can use our industry-leading experience to help you get set up with the best payment solution at the lowest possible cost.
Frequently Asked Questions
Where do I find Authorize.Net in BigCommerce?
Current BigCommerce stores place payment gateway settings under Settings and Payments. From there, locate Authorize.Net among the available online payment methods.
What credentials does the current setup require?
Current BigCommerce documentation lists Display Name, API Login ID, Transaction Key and Payment Gateway ID among the Authorize.Net general settings.
Where can I find my API Login ID and Transaction Key?
Authorize.Net provides these credentials through its Merchant Interface. Store them securely because they help authenticate your payment gateway connection.
What should I check if transactions fail?
Start by checking the credentials entered in your gateway settings. An incorrect or outdated Transaction Key can prevent the connection from authenticating correctly.
Can I change the settings after setup?
Yes. Once you complete the setup, you can return to the Authorize.Net settings panel in BigCommerce to manage the connection.
Do I still need a merchant account?
A payment gateway handles the technical connection for online payment transactions. Your merchant account supports the processing and settlement side of accepting those payments.
