Authorize.Net · Decline codes
What does Authorize.Net 57 “An error occurred during processing. Please try again” mean?
Checked
Authorize.Net response reason code 57 is caused when a transaction reaches the processor with data it does not recognise or cannot interpret. Authorize.Net's examples: the wrong number of characters in the card code, or non-alphanumeric characters in the ZIP code. Despite the "please try again" message, retrying unchanged data fails again; the fields need cleaning up.
- Type
- Processing error (data)
- Who declined
- The card processor
- Retry
- After the data is corrected.
- Shopper action
- Check the security code and postcode, then try again.
- Merchant action
- Check your form sends clean data in each field.
What PlatformDTC does
PlatformDTC lists Authorize.Net code 57 among the processing-error codes that defer a renewal rather than dun it, so a data quirk at the processor does not send the customer a "payment failed" email.
Why it happens
Authorize.Net's safeguards catch most bad data, but each processor parses fields differently, so some invalid values slip through and the processor rejects them.
What the shopper can do
Re-enter the security code and the postcode carefully, without extra characters.
What the store can do
Ask your developer to trim spaces and strip unusual characters from the card code and postal code before sending.
For developers
errors[0].errorCode "57". Validate cardCode length (3 or 4 digits) and zip characters client-side.
Frequently asked questions
- Why does Authorize.Net code 57 say try again if it is a data problem?
- It shares the generic processing-error text; Authorize.Net's explanation points to data the processor could not interpret.
- What data causes Authorize.Net code 57?
- Authorize.Net gives a wrong-length card code or non-alphanumeric characters in the ZIP code as examples.
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
- 19 — Authorize.Net did not get an answer from the card processor (a connection problem).
- 63 — Often your business details (such as country) are wrong for a TSYS processor account.
- 78 — The security code (CVV) sent was in the wrong format, for example the wrong number of digits.
- 120 — The original transaction timed out and the automatic void of it also failed.
- 16 — The transaction ID you referenced (for a refund or void) is not on this Authorize.Net account.
- 50 — You can only refund a settled transaction; this one has not settled yet.
- 54 — The refund can't be issued: unsettled, wrong type or currency, bad ID, or settled over 180 days ago.
- 55 — This refund plus earlier refunds would be more than the original payment.