Authorize.Net · Decline codes
What does Authorize.Net 56 “Credit card transactions are not accepted by this merchant” mean?
Checked
Authorize.Net response reason code 56, "Credit card transactions are not accepted by this merchant", means the merchant processes eCheck.Net transactions only and does not accept credit cards. No card will work until card processing is added to the account. The store needs a card merchant account from its merchant service provider.
- Type
- Error (merchant setup)
- Who declined
- Your Authorize.Net account type
- Retry
- No, not on this account.
- Shopper action
- Pay with another method the store offers.
- Merchant action
- Set up card processing with your merchant service provider.
What PlatformDTC does
PlatformDTC shows the shopper Authorize.Net's message for code 56; it is an account setup code, not on PlatformDTC's reroute list, so no backup processor is tried.
Why it happens
Authorize.Net's note: "The merchant processes eCheck.Net transactions only and does not accept credit cards."
What the store can do
Contact your merchant service provider to add card processing, then enable it on the gateway.
For developers
errors[0].errorCode "56". Code 18 is the opposite case: ACH not accepted.
Frequently asked questions
- Why does Authorize.Net say I don't accept credit cards (code 56)?
- Your account is set up for eCheck.Net only.
- Can the shopper do anything about code 56?
- Only pay with a method the store supports.
Sources
- Authorize.Net Response Code Tool (response reason codes) — Authorize.Net
- Authorize.Net response codes (JSON list behind the Response Code Tool) — Authorize.Net
Related
- 17 — Your Authorize.Net gateway is not set up to accept this card brand.
- 28 — Your processor platform is not set up to accept this card brand.
- 39 — The currency sent is not the one your Authorize.Net account is set up for.
- 49 — The amount is above the maximum transaction amount allowed on your account.
- 5 — The amount field was missing or not a valid number.
- 13 — The API Login ID is wrong, sent to the wrong environment, or the account is inactive.
- 123 — A personal user login was used to connect software; it needs the API Login ID instead.
- 124 — Your processor does not support transactions flagged as recurring.