Authorize.Net · Decline codes
What does Authorize.Net 153 “There was an error processing the payment data” mean?
Checked
Authorize.Net response reason code 153, "There was an error processing the payment data", usually appears with wallet payments sent as encrypted payment data. Authorize.Net's checklist: set marketType to e-commerce, use an auth-capture or auth-only transaction, send both opaque data values Base64 encoded, and leave out card number, expiry, track data and 3-D Secure data.
- Type
- Error (integration)
- Who declined
- Authorize.Net's payment data check
- Retry
- Only after the request is fixed; the shopper can try another method meanwhile.
- Shopper action
- Try again or pay by card.
- Merchant action
- Have your developer check the wallet integration.
What PlatformDTC does
PlatformDTC's Authorize.Net checkout sends Apple Pay and Google Pay as Authorize.Net opaque data and refuses any request that also carries a card number or expiry, which matches Authorize.Net's instructions for avoiding code 153.
Why it happens
The encrypted wallet data could not be decrypted or was sent with fields that must not accompany it.
What the shopper can do
Try once more, or pay by typing the card in.
What the store can do
Ask your developer to compare the request with Authorize.Net's checklist for code 153.
For developers
errors[0].errorCode "153". Requirements: marketType "0"; transactionType authCaptureTransaction or authOnlyTransaction; opaqueData.dataDescriptor and dataValue; no card number, expiry, track or 3DS data; data that decrypts for this merchant, Base64 encoded.
Frequently asked questions
- What causes Authorize.Net code 153 with Apple Pay?
- Payment data that cannot be decrypted for this merchant or is sent with fields that must not be included.
- Can the shopper fix Authorize.Net code 153?
- Not directly; paying by card is the workaround while the store fixes its integration.
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
- 154 — Apple Pay is not switched on for this Authorize.Net account.
- E00003 — The request sent to the API was malformed, so Authorize.Net could not read it.
- 289 — Your processor will not run a $0 card check for this card brand.
- 19 — Authorize.Net did not get an answer from the card processor (a connection problem).
- 20 — Authorize.Net lost contact with the card processor before getting a response.
- 35 — Your merchant account was set up incorrectly at the processor.
- 57 — The processor could not interpret data in the request, such as a bad CVV length or ZIP format.