Authorize.Net · Decline codes
What does Authorize.Net 154 “Processing Apple Payments is not enabled for this merchant account” mean?
Checked
Authorize.Net response reason code 154 means processing Apple Pay payments is not enabled for this merchant account. The shopper's Apple Pay worked on their device, but your Authorize.Net account cannot accept it yet. Get Apple Pay enabled on the Authorize.Net account, or hide the Apple Pay button until it is.
- Type
- Error (merchant setup)
- Who declined
- Your Authorize.Net account settings
- Retry
- No, until Apple Pay is enabled.
- Shopper action
- Pay by card or another method.
- Merchant action
- Enable Apple Pay on your Authorize.Net account.
What PlatformDTC does
PlatformDTC passes Apple Pay to a store's Authorize.Net account as opaque payment data, so the account itself must have Apple Pay enabled; until then the shopper sees Authorize.Net's code 154 message.
Why it happens
Apple Pay has to be enabled separately on the Authorize.Net account.
What the shopper can do
Use a card or another payment option the store shows.
What the store can do
Get Apple Pay enabled on your Authorize.Net account (contact Authorize.Net if you cannot find the setting), then retest a payment.
For developers
errors[0].errorCode "154".
Frequently asked questions
- Why does Apple Pay fail with Authorize.Net code 154?
- Apple Pay is not enabled on the merchant's Authorize.Net account.
- Is code 154 the shopper's problem?
- No. It is the store's account setting.
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
- 153 — The wallet payment data (such as Apple Pay) could not be processed as sent.
- 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.
- 63 — Often your business details (such as country) are wrong for a TSYS processor account.