Authorize.Net · Decline codes
What does Authorize.Net 127 “The transaction resulted in an AVS mismatch (void failed)” mean?
Checked
Authorize.Net response reason code 127 means an AVS mismatch declined the transaction and the system-generated void then failed. Authorize.Net explains that on the FDC Omaha platform the original authorization may stay on the card for up to 30 days. The merchant can contact the issuing bank with the merchant account number and the authorization code to request a manual reversal.
- Type
- Hard decline for these details
- Who declined
- AVS result on the FDC Omaha platform, then the processor
- Retry
- Only with the correct address. Check for a lingering authorization first.
- Shopper action
- Correct the billing address; ask the bank about any pending hold.
- Merchant action
- Request a manual authorization reversal from the issuer if needed.
What PlatformDTC does
PlatformDTC classes Authorize.Net code 127 as never-retry on the same details and never offers a backup processor for it, which avoids a second authorization on a card that may already carry a hold. 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
On FDC Omaha, Authorize.Net voids transactions that fail AVS or CVV. If FDC Omaha does not reply to that void request, you get code 127 instead of 27.
What the store can do
Authorize.Net's guidance: if necessary, contact the card issuing bank, provide your merchant account number and the authorization code for the declined transaction, and request a manual reversal.
For developers
errors[0].errorCode "127". Authorize.Net: "The system-generated void for the original AVS-rejected transaction failed."
Frequently asked questions
- How long can the hold from Authorize.Net code 127 last?
- Authorize.Net says the original authorization may remain on the card for up to 30 days unless it is manually reversed.
- How do I release a code 127 hold?
- Contact the card issuing bank with your merchant account number and the authorization code and request a manual reversal.
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
- 27 — The billing address entered does not match the address the card's bank has on file.
- 145 — Your AVS and card code filters rejected the sale, but the automatic void of the authorization failed.
- 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.
- 251 — A Fraud Detection Suite filter declined the payment, including the blocked-IP filter.
- 252 — The payment was accepted but is held for your review by a fraud filter set to hold.
- 253 — The card was authorized, but a fraud filter is holding the payment for your review.
- 254 — You or your team declined the payment after reviewing a held transaction.