Authorize.Net · Decline codes
What does Authorize.Net 295 “Partially approved on the prepaid card” mean?
Checked
Authorize.Net response reason code 295 means the amount was only partially approved on the prepaid card used, and an additional payment is required to fulfil the balance of the transaction. The card had some value but not enough. The store either collects the remainder with a second payment, if its integration supports split tender, or voids the partial authorization.
- Type
- Partial approval
- Who declined
- The prepaid card's issuer
- Retry
- Not for the full amount on that card; collect the remainder another way.
- Shopper action
- Pay the balance with another card.
- Merchant action
- Support split tender or void the partial approval.
What PlatformDTC does
Code 295 is not on PlatformDTC's reroute list, and PlatformDTC's checkout completes an Authorize.Net order only on a full approval (response code 1), so a partial approval is not taken as a paid order.
Why it happens
Prepaid and gift cards carry a fixed balance. When partial authorization is enabled, the issuer approves what is left and Authorize.Net reports the shortfall with code 295.
What the shopper can do
Use a second card for the remaining amount, or one card that covers the full total.
What the store can do
If your checkout does not handle split payments, void the partial authorization so the prepaid balance is released, and ask for a single card.
For developers
Partial authorizations return splitTenderId and splitTenderPayments in the transaction response; later requests reference the splitTenderId. Codes 296–298 are the related split tender errors.
Frequently asked questions
- Is the prepaid card charged after Authorize.Net code 295?
- The approved portion is authorized; it is released if the transaction is voided.
- How does a shopper finish paying after code 295?
- With a second payment for the balance, if the store supports split tender, or with one card that covers the total.
Sources
- Authorize.Net Response Code Tool (response reason codes) — Authorize.Net
- Authorize.Net response codes (JSON list behind the Response Code Tool) — Authorize.Net
- Authorize.Net API reference: createTransactionResponse fields — Authorize.Net
Related
- 2 — The card issuer, or the processor on its behalf, refused the payment without a specific reason.
- 49 — The amount is above the maximum transaction amount allowed on your account.
- 36 — The bank approved the card at checkout, but the payment failed when it was settled.
- 6 — The card number failed validation: a typo, a missing digit, or not a real card number.
- 37 — The card number was rejected as invalid (same text as code 6).
- 315 — The processor declined the card number as invalid.
- 7 — The expiry date was sent in the wrong format or is not a valid date.
- 316 — The processor rejected the card's expiry date as invalid.