Authorize.Net · Decline codes
What does Authorize.Net 145 “This transaction has been declined (filter void failed)” mean?
Checked
Authorize.Net response reason code 145 means the transaction was rejected by both your card code and AVS filters, and the system-generated void of that rejected transaction failed. No sale went through, but the shopper may see an authorization hold until it expires or is reversed. Fix the details as you would for code 45, and help the shopper if the hold worries them.
- Type
- Hard decline for these details (merchant filter)
- Who declined
- Your Authorize.Net filters, then the processor
- Retry
- Only after the shopper corrects the details. Check for a lingering authorization.
- Shopper action
- Correct the address and security code; a pending hold may show briefly.
- Merchant action
- Check for a held authorization and request a reversal if the shopper asks.
What PlatformDTC does
PlatformDTC treats Authorize.Net code 145 like 45: never retried on the same details and never moved to a backup processor, so the card is not authorized again while the earlier hold is still pending. On a subscription renewal the code is not retried: the subscription is held past due and the customer gets an email with a link to add a new card.
Why it happens
Authorize.Net received an authorization from the processor, your filters rejected it, and the automatic void that should have released the money did not complete.
What the store can do
If the shopper reports a pending charge, contact your merchant service provider or ask the shopper's bank to release the authorization, quoting the transaction details.
For developers
errors[0].errorCode "145". Authorize.Net's description: "The system-generated void for the original card code-rejected and AVS-rejected transaction failed."
Frequently asked questions
- Why does the shopper see a pending charge after Authorize.Net code 145?
- The automatic void failed, so the authorization the bank granted can stay on the card until it expires or is reversed.
- Do I need to refund a code 145 transaction?
- No sale was captured, so there is nothing to refund; at most an authorization needs releasing.
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
- 45 — Both the address check and the security code check hit the rejection rules you set.
- 141 — FraudScreen.Net rejected the payment, but the automatic void of the authorization did not go through.
- 127 — An AVS mismatch declined the sale and the automatic void failed, so a hold may stay on the card.
- 65 — Your card code (CVV) filter rejected the payment based on the security code result.
- 165 — A security code mismatch hit your settings and the automatic void of the authorization failed.
- 27 — The billing address entered does not match the address the card's bank has on file.
- 128 — The shopper's bank does not currently allow transactions on this account.
- 250 — The payment came from an IP address you blocked in Authorize.Net's fraud tools.