Authorize.Net · Decline codes
What does Authorize.Net 316 “Credit card expiration date is invalid (processor)” mean?
Checked
Authorize.Net response reason code 316 means the credit card expiration date is invalid, and Authorize.Net marks it as a processor-issued decline. The processor would not accept the expiry date it received, often because it does not match the card. The shopper should re-enter the date from the card; if the card has been reissued, the new card's date is the one that works.
- Type
- Hard decline for these details
- Who declined
- The card processor
- Retry
- Only with the correct expiry date.
- Shopper action
- Check the expiry date or use another card.
- Merchant action
- Ask for corrected details; do not resubmit unchanged.
What PlatformDTC does
PlatformDTC classes Authorize.Net code 316 as never-retry on the same details and does not send it to a backup processor. 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 processor compared the expiry date with what it knows about the card and rejected it. A replacement card with a new date is a common cause.
What the shopper can do
Use the expiry date printed on the card you are holding now. If your bank sent a replacement, use the new card.
What the store can do
Ask the customer for updated card details rather than retrying.
For developers
errors[0].errorCode "316" (processor-issued twin of 7).
Frequently asked questions
- Why would the processor reject a correct-looking expiry date (Authorize.Net 316)?
- The date may not match the card on file, for example after the bank reissued the card.
- Is Authorize.Net code 316 a bank decline?
- It is processor-issued; the fix is the same: correct the expiry date.
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
- 7 — The expiry date was sent in the wrong format or is not a valid date.
- 317 — The processor declined because the card has expired.
- 315 — The processor declined the card number as invalid.
- 8 — The card's expiry date has passed, so it can no longer be charged.
- 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).
- 318 — The processor rejected the request as a duplicate of an earlier transaction.
- 17 — Your Authorize.Net gateway is not set up to accept this card brand.