Authorize.Net · Decline codes
What does Authorize.Net 28 “The merchant does not accept this type of credit card (processor)” mean?
Checked
Authorize.Net response reason code 28 means the merchant's processor platform is not configured to accept this card type. The gateway may allow the brand, but the processor behind it does not. Authorize.Net advises contacting the merchant service provider to request any needed merchant accounts and to have the card type enabled on the processor.
- Type
- Error (merchant setup)
- Who declined
- Your processor configuration
- Retry
- No, not until the processor enables the card type.
- Shopper action
- Pay with a different card brand.
- Merchant action
- Ask your merchant service provider to enable the brand on the processor.
What PlatformDTC does
PlatformDTC classes Authorize.Net code 28 as a decline another processor may approve, so a store with PayPal card payments as its backup can still take the card through PayPal's card fields. On a subscription renewal the card type will not be accepted later either, so the renewal is not retried and the customer is asked for a different card.
Why it happens
Card acceptance needs both the processor and the gateway set up for the brand. Code 28 means the processor is the missing piece.
What the shopper can do
Use another card brand the store accepts.
What the store can do
Ask your merchant service provider which brands your processor account supports and request the missing one.
For developers
errors[0].errorCode "28".
Frequently asked questions
- Who fixes Authorize.Net code 28?
- Your merchant service provider, by enabling the card type on your processor account.
- Can a shopper fix Authorize.Net code 28?
- Only by paying with a card brand you already accept.
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.
- 56 — The account only processes eChecks, so card payments are refused.
- 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.