Authorize.Net · Decline codes
What does Authorize.Net 289 “This processor does not accept zero dollar authorization for this card type” mean?
Checked
Authorize.Net response reason code 289, "This processor does not accept zero dollar authorization for this card type", means a $0 authorization, a check of the card without charging it, is not supported by your processor for this card brand. Saving the card needs another approach, such as validating it with a real first charge.
- Type
- Error (merchant setup)
- Who declined
- Your processor
- Retry
- Not as a $0 authorization.
- Shopper action
- Nothing; the store has to adjust.
- Merchant action
- Use a different validation method for this card type.
What PlatformDTC does
PlatformDTC saves a subscriber's Authorize.Net card from the approved first charge itself, creating the customer profile from that transaction, rather than from a separate $0 authorization.
Why it happens
Some processors do not support zero-amount verification for every card brand.
What the store can do
Validate the card with the actual first payment, or ask your merchant service provider about $0 authorization support.
For developers
errors[0].errorCode "289". Affects $0 authOnly requests and customer profile validation in live mode.
Frequently asked questions
- What is a zero dollar authorization (Authorize.Net 289)?
- A $0 check that a card is valid without charging it.
- How do I save cards if my processor returns code 289?
- Create the profile from a real approved charge instead of a $0 check.
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
- E00027 — The API reports the transaction failed; the real reason is in the transaction's errorCode.
- 124 — Your processor does not support transactions flagged as recurring.
- 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.
- 120 — The original transaction timed out and the automatic void of it also failed.