Authorize.net

Setting up Authorize.net

1. 1

   Set up an Authorize.net account

2. 2

   Log into your Authorize.net account

3. 3

   If you're going live, make sure your Authorize.net account is not in Test Mode (see below)

4. 4

   Under your Authorize.net account settings, click Settings

5. 5

   Under Security Settings, choose API Login ID and Transaction Key

6. 6

   Obtain a Transaction Key by answering your security question

7. 7

   Copy your Authorize.net API Login ID. If one isn't shown, use your Authorize.net login username instead.

8. 8

   Go to the Foxy admin and go to Settings > Payments

9. 9

   Open or create a payment method set, then click Add payment method + and choose Authorize.net

10. 10

    Under Live setup, enter your API ID and Transaction Key. This setup only takes effect once Use live credentials is turned on for the payment method set.

11. 11

    Under Test setup, enter a separate test API ID and Transaction Key from your own Authorize.net sandbox account — there's no built-in default test account, so you'll need to set one up yourself (see Testing below)

12. 12

    If you want to verify a card is valid without charging it, set Card verification to something other than Off (leaving it Off means payment methods are never verified, which isn't recommended)

13. 13

    Turn on Authorize only (no capture) if you want to authorize payments without capturing them immediately

14. 14

    Click Create (or Save if editing an existing entry)

15. 15

    If you're doing international sales, configure your AVS settings as described below

Authorize.net test mode

If you're taking your account live, make sure Test Mode is turned off in your Authorize.net account. New accounts default to Test Mode on, which blocks payments even if Use live credentials is turned on for your Foxy payment method set. An account still in Test Mode shows an orange "Your account is in TEST MODE" banner in the Authorize.net admin.

See Authorize.net's instructions for turning off Test Mode.

Turning off your Authorize.net email receipt

Since Foxy usually sends your customers their email receipt, disable Authorize.net's own copy: in Authorize.net, go to Settings > Email Receipts and uncheck Enable Email Confirmation.

Configuring your AVS (Address Verification Service) responses

Review your AVS settings in Authorize.net under Settings > Address Verification Service.

Many non-US banks don't support AVS, and Authorize.net's defaults reject cards from banks that don't support it — worth understanding before you leave the defaults in place, especially if you get international orders. If you're not a high-risk merchant, many stores leave "B" as the only decline option, though declining B, E, R, and N is often reasonable. If you anticipate a lot of international orders, relax these settings further. See Authorize.net's FAQ for details on each code.

If you are a high-risk merchant, or seeing a lot of fraud, consider declining B, E, R, U, S, and N, and give serious thought to G.

Configuring your CSC (Card Security Code) settings

In Authorize.net, go to Settings, click Card Code Verification under Security Settings, and make sure every option except N is allowed. If you decline any option besides N, be aware that Foxy may sometimes send transactions without a CSC.

Also confirm the Card Code field under Settings > Payment Form > Form Fields in Authorize.net is not set to required, and save.

Configuring your phone fields

Check whether your Authorize.net account requires a customer phone number. If it does, go to Settings > Checkout in the Foxy admin, and under Checkout form settings, set Phone to Required.

Testing

Setting up a test account

Create your own Authorize.net sandbox account here, then enter its API Login ID and Transaction Key under Test setup on the Authorize.net entry in your payment method set. There's no shared default Foxy test account for this gateway — each store needs its own sandbox credentials.

You can also test with your live account: enter your real credentials under Live setup, turn on Use live credentials, then enable Test Mode in Authorize.net itself.

Test card numbers

On a test Authorize.net account, use test card number 4111111111111111, any future expiration date, and any 3-digit CSC.

Troubleshooting & interpreting response codes

Response Reason Codes and Response Reason Text is Authorize.net's authoritative reference for response codes.

Response Reason Code 103: Usually means the credentials in your Foxy payment method set don't match your Authorize.net account. Recheck the API ID and Transaction Key in both the correct section — Live setup or Test setup, matching whichever mode Use live credentials is set to.

Response Reason Code 87: "Transactions of this Market Type cannot be processed on our system" usually means the Market Type field in your Authorize.net Merchant Profile needs to be set to eCommerce. Contact Authorize.net support to change it.

Important notes and caveats

Review your AVS settings — the defaults can be overly restrictive for merchants doing international transactions.