Connect your Authorize.net account with ReCharge and accept credit card payments. To sign up for a merchant account, visit Authorize.net. The Authorize.net integration has a different set-up configuration than Stripe and Braintree, so you will need to reach out to the ReCharge support team to enable it on your ReCharge account.
Before you begin
- You will need to obtain your API Login ID and Transaction Key and send it to ReCharge Support. Use the instructions below on how to get these keys to give our team.
- Once set up, transactions will show up in the transaction details report on Authorize.net, rather than the customer information manager.
- The integration can only connect to a live/production Authorize.net gateway account. Sandbox/test accounts will not work with ReCharge.
Step 1 - Access Authorize.net
Log in to your Merchant Interface at Authorize.net and click account at the top.
Step 2 - Locate and view API keys and credentials
Click on API Credentials & Keys in the Security Settings section. You can view and copy your API Login ID on this page as well as view or generate the transaction key you'll also need. When you visit this page to get the transaction key, it will generate a new key each time, so be sure to send us a new key and avoiding opening that page in the future.
Note: Ensure that your currency is correct. Otherwise, you may risk incorrect charges for your customers.
Step 3 - Send credentials to ReCharge support
Once you've copied your Login ID and Transaction Key create a support ticket and send the credentials to ReCharge so we may activate Authorize.net for your checkout.
Troubleshooting Authorize.net
Why is Authorize.net holding my payments?
Authorize.net may hold payments for a number of reasons, including fraud detection. It is recommended to check your Authorize.net account in the event that payment is quarantined and requires action. To prevent or reduce the number of false-positive fraud detections, we recommend the following:
- Disabling the Velocity Filter.
- Disabling the IP filter as the IPs sent are from ReCharge rather than Authorize.net and we rotate through a list of IPs that may change in the future. If you must keep this on, reach out to the ReCharge support team and we will be happy to provide the list of IPs so you can whitelist the IPs in your Authorize.net account.
Common error codes
| Error Code | Error Message | Details |
| E00007 | User authentication failed due to invalid authentication values. | Authorize.net does not allow you to view existing transaction keys. In clicking the Transaction Key page, it will automatically disable the current transaction key. If this happens, send the new credentials to our Support team to update. |
| The reference transaction did not succeed. Only successful reference transactions are permitted. | This can mean that the transaction has not cleared in Authorize.net or is caught in their fraud filter. You will need to reach out to Authorize.net for further assistance. | |
| Your Authorize.net account is set to require the CVV code. | The CVV code cannot be vaulted for recurring orders, so the first checkout order may process correctly but you may see an error on subsequent charges. To fix this error, you will need to turn off the CVV requirement in Authorize.net. Reach out to ReCharge Support once updated and we can retry your error charges. | |
| 27 | The transaction has been declined because of an AVS mismatch | This can happen when the billing address in Authorize.net is different than what is in ReCharge. It is recommended that the customer update their billing address in ReCharge. If the issue persists, the store owner should update the billing address manually in Authorize.net or temporarily turn off the AVS validator. |
| 54 | The referenced transaction does not meet the criteria for issuing a credit. | Authorize.net delays the transfer of funds for 24 hours. If you receive this error message, try refunding the charge directly in Authorize.net. You may also need to confirm if the payment has been flagged in Authorize.net for review. |