Authorize.Net · Decline codes
What does Authorize.Net 37 “The credit card number is invalid” mean?
Checked
Authorize.Net response reason code 37 carries the same message as code 6: "The credit card number is invalid." The number submitted is not one the card network or processor accepts, most often because of a typo or a missing digit. The shopper should enter the number again or use a different card; repeating the same number will not change the result.
- Type
- Hard decline for these details
- Who declined
- Authorize.Net or the processor
- Retry
- Only with a corrected card number.
- Shopper action
- Re-enter the card number or try another card.
- Merchant action
- Check the form is not truncating or reformatting card numbers.
What PlatformDTC does
PlatformDTC classes Authorize.Net code 37 as never-retry on the same details and never reroutes it, since another processor would reject the same number for the same reason. On a subscription renewal the code is not retried: the subscription is held past due and the customer gets an email with a link to add a new card.
Why it happens
The card number either fails basic format checks or does not belong to a card the network recognises.
What the shopper can do
Check every digit of the card number. If it is right and still fails, the card may not be valid for online payments; ask the bank.
What the store can do
Watch for spikes: many code 37 errors in a short time from one source can mean someone is guessing numbers on your checkout.
For developers
errors[0].errorCode "37". Treat like 6 and 315 in retry logic: never resubmit the same PAN.
Frequently asked questions
- Why do Authorize.Net codes 6 and 37 have the same message?
- Authorize.Net lists both with "The credit card number is invalid"; either way the number was not accepted.
- Can a code 37 card work later?
- Not with the same number; the shopper needs to correct it or use another card.
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
- 6 — The card number failed validation: a typo, a missing digit, or not a real card number.
- 315 — The processor declined the card number as invalid.
- 7 — The expiry date was sent in the wrong format or is not a valid date.
- 316 — The processor rejected the card's expiry date as invalid.
- 8 — The card's expiry date has passed, so it can no longer be charged.
- 317 — The processor declined because the card has expired.
- 78 — The security code (CVV) sent was in the wrong format, for example the wrong number of digits.