Authorize.Net is a payment gateway that can be used to process credit card payments for ecommerce stores. Magento and Adobe Commerce stores can connect to payment gateways so customers can pay securely during checkout.
In this guide, we explain how to configure Authorize.Net in Magento, where to obtain your API credentials, how to test the integration, and what to check if payments do not work as expected.
Important compatibility note: The Magento/Adobe Commerce payment integration landscape has changed over time. Adobe states that the core Authorize.Net integration was deprecated in Adobe Commerce 2.3.4 and completely removed in 2.4.0. Stores running newer Adobe Commerce or Magento Open Source versions may therefore need a compatible third-party Authorize.Net extension rather than the legacy built-in method described in older Magento installations.
What Is Authorize.Net?
Authorize.Net is a payment gateway that allows online businesses to accept electronic payments through their websites. A Magento integration connects the store checkout with Authorize.Net so that payment information can be submitted for transaction processing.
For a Magento store owner, configuring a payment gateway involves more than simply entering an API key. You should also verify the correct environment, credentials, payment action, checkout behavior, and transaction testing before enabling live payments.
What You Need Before Configuring Authorize.Net in Magento
Before starting the configuration, make sure you have:
- An active Authorize.Net merchant or sandbox account.
- Your Authorize.Net API Login ID.
- Your Authorize.Net Transaction Key.
- Access to the Magento Admin Panel.
- A Magento/Adobe Commerce version or Authorize.Net extension that supports the integration you intend to use.
- A test environment where you can safely verify checkout and payment transactions.
The API Login ID and Transaction Key are authentication credentials used by an application to connect to the Authorize.Net payment gateway. They are different from the credentials used to log into the Authorize.Net Merchant Interface.
How to Get an Authorize.Net API Login ID and Transaction Key
If you are testing your Magento payment integration, you can use the Authorize.Net sandbox environment instead of processing real payments.
1. Create a test account on Authorize.Net:
2. Save your API credentials securely.
Depending on your account setup, you will need the following credentials:
- API Login ID
- Transaction Key
Authorize.Net's current documentation explains that API credentials are used to authenticate API requests. For a sandbox account, credentials are managed through the sandbox Merchant Interface.
For existing accounts, you can generally find the API credentials under Account > Account and API Settings > API Credentials and Keys. Authorize.Net also requires verification when generating a new Transaction Key.
Magento Authorize.Net Configuration
On older Magento installations that still provide the legacy Authorize.Net configuration, log in to your Magento Admin Panel and navigate to:
System > Configuration > Payment Methods
Expand the Authorize.net section.
Enter your:
- API Login ID
- Transaction Key
Review the remaining payment settings according to your store's requirements and save the configuration.
Note: The exact menu names and available Authorize.Net settings depend on the Magento/Adobe Commerce version and the payment extension installed on the store. Newer Adobe Commerce versions may not contain the legacy built-in Authorize.Net method.
Choose the Correct Payment Environment
One of the most common configuration mistakes is mixing sandbox and production credentials.
Authorize.Net maintains separate sandbox and production environments. Sandbox credentials should be used with the sandbox environment, while production credentials should be used with the live payment environment.
Authorize.Net states that using production credentials with the sandbox, or sandbox credentials with production, can result in authentication errors. Sandbox transactions are designed for testing and do not represent real financial transactions.
Test Authorize.Net Before Going Live
Do not immediately switch a new payment integration to live mode. First verify the complete checkout process in a safe testing environment.
Test the following:
- Product selection and cart functionality.
- Checkout page loading.
- Credit card fields.
- Billing and shipping information.
- Successful test transactions.
- Declined transactions.
- Order creation in Magento.
- Payment and invoice status.
- Email notifications.
- Refund or cancellation workflows where applicable.
Authorize.Net provides dedicated sandbox testing resources and test card numbers for integration testing. Sandbox transactions do not process real payments.
Authorize vs. Authorize and Capture
Depending on the payment integration you are using, you may encounter payment actions such as Authorize and Authorize and Capture.
Authorize
An authorization verifies the transaction and places a hold on the applicable funds. The merchant captures the payment separately.
Authorize and Capture
This option authorizes the transaction and captures the payment as part of the payment process.
The appropriate payment action depends on how your store handles order fulfillment, invoicing, inventory, and payment capture.
Security Best Practices for Magento Payment Credentials
Your API Login ID and Transaction Key should be treated as sensitive configuration values. Do not publish them in blog posts, screenshots, Git repositories, JavaScript files, or publicly accessible configuration files.
When managing a production Magento installation:
- Never expose payment credentials in frontend code.
- Do not commit sensitive credentials to public repositories.
- Use secure administrative access.
- Restrict access to payment configuration to authorized team members.
- Use HTTPS throughout the checkout process.
- Keep Magento, payment extensions, and server software maintained.
- Use separate credentials for testing and production.
- Review logs carefully and avoid exposing sensitive payment information.
Adobe Commerce also provides configuration mechanisms for sensitive values, including environment variables and sensitive configuration commands, which can be useful when managing production deployments.
Common Authorize.Net Problems in Magento
1. Authorize.Net Is Missing From Magento
If you cannot find Authorize.Net under your Magento payment configuration, first check your Magento or Adobe Commerce version.
The legacy core Authorize.Net integration was removed from Adobe Commerce 2.4.0. If you are using a newer version, you may need a compatible third-party payment extension.
2. Payment Credentials Are Rejected
Check that the API Login ID and Transaction Key belong to the same Authorize.Net environment being used by the Magento integration.
For example, do not use sandbox credentials with a production endpoint.
3. Checkout Gets Stuck
Checkout problems can be caused by incorrect payment configuration, JavaScript errors, extension conflicts, missing client-side configuration, caching issues, or compatibility problems.
Adobe has documented a historical Authorize.Net checkout issue involving the Public Client Key and recommends checking the payment configuration and clearing Magento cache after making the required changes.
4. Payment Works in Testing but Not in Production
If testing succeeds but live transactions fail, verify that all production settings have been updated. This includes the production credentials, live payment environment, API endpoint, webhooks where applicable, and Authorize.Net account mode.
Before accepting real orders, perform a controlled production test and verify that the order, payment status, invoice, and customer notifications behave as expected.
Magento Authorize.Net Configuration Checklist
Use this checklist before considering your payment integration complete:
- Authorize.Net account is active.
- Correct API Login ID is configured.
- Correct Transaction Key is configured.
- Sandbox and production credentials are not mixed.
- Magento version is compatible with the selected integration.
- Payment method is enabled.
- Checkout displays the expected payment option.
- Successful test transaction has been completed.
- Declined transaction behavior has been tested.
- Order and payment statuses are correct.
- Magento cache has been cleared after configuration changes.
- Production credentials are stored securely.
- Live mode has been enabled only after testing is complete.
Frequently Asked Questions About Authorize.Net and Magento
Can I use Authorize.Net with Magento?
Yes, Authorize.Net can be integrated with Magento/Adobe Commerce, but the implementation depends on the Magento version. The legacy core Authorize.Net integration was removed from Adobe Commerce 2.4.0, so newer installations may require a compatible third-party extension.
What credentials are required for Authorize.Net Magento integration?
The integration commonly requires an Authorize.Net API Login ID and Transaction Key. Depending on the integration method and version, additional credentials or keys may also be required.
Where can I get an Authorize.Net Transaction Key?
Authorize.Net provides the Transaction Key through the account's API credentials and keys settings. Sandbox and production accounts have separate environments and credentials.
Can I test Authorize.Net without charging a real credit card?
Yes. Authorize.Net provides a sandbox environment specifically for integration testing. Sandbox transactions do not process real payments through financial institutions.
Why is Authorize.Net not showing in Magento?
On newer Magento or Adobe Commerce installations, the legacy built-in Authorize.Net integration may no longer be available. Check your Commerce version and determine whether a compatible payment extension is required.
Should I use sandbox or production credentials during development?
Use sandbox credentials while developing and testing. Switch to production credentials only after the integration has been tested and you are ready to process real transactions.
What should I test before enabling live Authorize.Net payments?
Test checkout, successful payments, declined payments, order creation, payment status updates, invoices, customer emails, refunds where applicable, and the overall behavior of the payment integration.
How do I troubleshoot an Authorize.Net checkout error in Magento?
Start by checking the Magento payment configuration, API credentials, environment, browser console errors, Magento logs, extension compatibility, cache, and Authorize.Net transaction responses. If you are using a third-party extension, also check its documentation and compatibility with your Magento version.
Can ScriptBaker help with Magento payment gateway integration?
Yes. ScriptBaker provides custom software engineering and ecommerce development services, including Magento development and payment-related integrations. If your Magento store has an outdated payment integration, checkout errors, or needs a custom payment workflow, our development team can review the existing setup and help identify an appropriate implementation.
Conclusion
Configuring Authorize.Net in Magento requires the correct payment credentials, environment, Magento compatibility, and testing process. The older Magento configuration method can still be useful when maintaining legacy installations, but newer Adobe Commerce versions require careful attention to the current payment integration approach.
Always test the complete checkout workflow before processing live payments, keep API credentials secure, and verify that your payment extension is compatible with your Magento version.
Last updated: