Authorize.Net · Decline codes
What does Authorize.Net 315 “The credit card number is invalid (processor)” mean?
Checked
Authorize.Net response reason code 315 means the credit card number is invalid, and Authorize.Net describes it as a processor-issued decline: the processor, rather than Authorize.Net's own checks, rejected the number. The shopper should confirm the digits or use another card. A correctly typed number that still returns 315 points to a card the processor will not accept.
- Type
- Hard decline for these details
- Who declined
- The card processor
- Retry
- Only with a corrected card number.
- Shopper action
- Re-type the number or use another card.
- Merchant action
- Ask for another card if the number is correct.
What PlatformDTC does
PlatformDTC classes Authorize.Net code 315 as never-retry: checkout shows the decline and does not move the shopper to a backup processor with a number that was just rejected. 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
Unlike code 6, which Authorize.Net's own validation raises, 315 comes back from the processor after the request reached it.
What the shopper can do
Double-check the number. If it is correct, try a different card or ask your bank whether this card works online.
What the store can do
Nothing to configure; offer another payment method.
For developers
errors[0].errorCode "315" (processor-issued). Codes 316, 317 and 318 are the processor-issued versions of 7, 8 and 11.
Frequently asked questions
- What does processor-issued mean for Authorize.Net code 315?
- The processor itself returned the invalid card number decline, not Authorize.Net's front-end checks.
- Should I retry Authorize.Net code 315?
- Only if the shopper corrects the card number.
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.
- 37 — The card number was rejected as invalid (same text as code 6).
- 316 — The processor rejected the card's expiry date as invalid.
- 7 — The expiry date was sent in the wrong format or is not a valid date.
- 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.
- 11 — An identical transaction was sent within the duplicate window (two minutes by default).