Authorize.Net · Decline codes
What does Authorize.Net 141 “This transaction has been declined (FraudScreen void failed)” mean?
Checked
Authorize.Net response reason code 141 means the transaction was declined by FraudScreen.Net and the system-generated void of that rejected transaction then failed. The shopper is not charged for an order, but an authorization hold can remain on the card for a while. Treat it like code 41 for fraud review, and check whether a hold needs to be released.
- Type
- Risk block (merchant setting)
- Who declined
- Your Authorize.Net fraud filter, then the processor
- Retry
- No. Check whether an authorization is still held on the card.
- Shopper action
- Expect a pending hold that should drop off; contact the store if it stays.
- Merchant action
- Look for a held authorization and ask the processor or issuer to release it if needed.
What PlatformDTC does
PlatformDTC classes Authorize.Net code 141 as a fraud stop, the same as code 41: the declined payment is never retried on a backup processor, so the shopper's card is not authorized a second time. 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 first declined the payment on your FraudScreen.Net score, then tried to void the authorization the processor had already granted. That void failed, which is why this code exists separately from 41.
What the store can do
Because the void failed, the shopper may see a pending amount. If they complain, contact your merchant service provider or the card issuer with the transaction details to have the authorization reversed.
For developers
errors[0].errorCode "141". Authorize.Net's description: "The system-generated void for the original FraudScreen-rejected transaction failed."
Frequently asked questions
- Was the shopper charged after Authorize.Net code 141?
- The sale was declined, but because the automatic void failed an authorization hold may still show on the card until it expires or is reversed.
- How is code 141 different from code 41?
- Both are FraudScreen.Net declines; 141 adds that Authorize.Net could not void the authorization it had already received.
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
- 41 — Your own FraudScreen.Net threshold blocked the payment because its fraud score was too high.
- 145 — Your AVS and card code filters rejected the sale, but the automatic void of the authorization failed.
- 44 — The processor declined because the card's security code (CVV) did not match the bank's records.
- 45 — Both the address check and the security code check hit the rejection rules you set.
- 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.