Visa Reason Code 11.1: Card Recovery Bulletin

What Visa Reason Code 11.1 Means

Visa reason code 11.1 falls under the Authorization category and is titled Card Recovery Bulletin. It is filed when a transaction was completed using a card that appeared on Visa's Card Recovery Bulletin — a list of accounts flagged for fraud, compromise, or other issues that should trigger an automatic decline at the point of authorization.

In practice, 11.1 chargebacks arise when a merchant processed a transaction without obtaining a proper electronic authorization, or when a transaction was forced through despite a decline signal. The Card Recovery Bulletin function is now embedded in real-time electronic authorization systems. Any merchant who requests proper authorization and receives an approval code is protected. The dispute arises when that process was bypassed.

Cross-Network Equivalent Codes

Common Trigger Scenarios

• Forced authorization bypassing the decline. A customer's card was declined electronically, but the clerk processed the transaction anyway using a force code or manual override. The card was on the CRB and the decline was correct — forcing it through creates full chargeback liability.
• Voice authorization on a CRB card. Voice authorizations call Visa's authorization center but may not always check the full CRB in the same way as electronic systems. Accepting a voice auth without ensuring the card number is clear can still trigger 11.1.
• Offline or store-and-forward transactions. When POS systems operate offline and batch-submit transactions later, CRB checks do not occur in real time. If a fraudulent card is used during an offline period, it slips through without the block that would normally stop it.
• Imprinter transactions (legacy card-present). Manual imprinter transactions — now extremely rare — could not check the CRB electronically. Any merchant still using these for fallback is fully exposed to 11.1 chargebacks.
• System error producing false approval. Technical errors sometimes generate false authorization approvals that do not reflect a genuine issuer response. Settlements based on these false approvals are vulnerable to 11.1 disputes when the card was actually flagged.

Key Deadlines & Timeframes

Evidence You Will Need

Your entire defense rests on demonstrating that proper electronic authorization was obtained. Pull authorization records before anything else.

• Authorization approval code from your processor confirming that an electronic authorization was obtained and approved for this specific transaction
• Authorization request and response data showing the exact message sent to and received from the issuer's authorization system, confirming the approval was genuine
• Transaction receipt bearing the authorization approval code, transaction amount, and date matching what was settled
• POS system transaction log confirming the authorization was obtained electronically and online (not forced, not offline, not manually entered)
• Settlement batch records showing the authorized amount matches the settled amount

How Merchants Lose This Dispute

• Cannot produce a valid authorization code. If the transaction was forced, offline, or based on a voice authorization that was not properly logged, you may not have the authorization record needed to win. Without an approval code, the dispute is essentially indefensible.
• Submitting a voice authorization instead of an electronic one. Voice authorizations, while technically valid in some circumstances, are generally insufficient to rebut an 11.1 dispute because they do not prove the CRB was checked. Electronic records are required.
• Misidentifying the authorization record. Submitting authorization data from a different transaction, or confusing batch numbers, will fail on review. Ensure the approval code you submit matches this specific transaction date, amount, and card number precisely.
• Processing transactions after a decline without re-authorizing. If the card was declined and then the merchant asked the customer to run it again as a smaller amount or different transaction type, the approval obtained on the second attempt does not cover the first declined attempt if it somehow settled.

Response Framework Overview

1. Lead with the authorization approval code. State the approval code, authorization date and time, and the authorizing system. This is your primary and often sufficient evidence.
2. Confirm online electronic processing. Explicitly state that the authorization was obtained electronically and in real time — not forced, not offline, not via voice authorization.
3. Attach the transaction receipt. Include the receipt showing the same approval code that appears in your authorization records.
4. Provide processor authorization logs. If available, include the raw authorization request/response log from your processor or acquirer confirming the genuine approval.
5. Note the amount match. Confirm the authorized amount equals the settled amount, eliminating any incremental authorization concerns.

Prevention Tips

• Never force authorizations or override declines. A declined transaction is a signal from the issuer. Overriding it — whether through a force code or manual process — transfers full liability to you. Train all staff that declines are final and cannot be overridden.
• Minimize offline transaction windows. If your POS operates offline during outages, the offline window should be as short as possible and offline batches should be reviewed before submission for any suspicious patterns.
• Ensure authorization codes are stored in your records. Every settled transaction should have an associated authorization code in your records. If your POS does not log authorization codes, fix that gap before the next chargeback arrives.
• Test your authorization infrastructure regularly. Silent authorization failures — where the system approves transactions without actually reaching the issuer — are rare but devastating. Periodic reconciliation between authorization requests and genuine issuer responses catches these issues early.

Frequently Asked Questions

What is the Card Recovery Bulletin?

The Card Recovery Bulletin (CRB) was a Visa-published list of card numbers that should be denied authorization — flagged accounts due to fraud, loss, or compromise. In modern systems, this function is handled electronically through real-time authorization checks. An 11.1 chargeback means the card should have been declined at authorization but was instead accepted.

How can I avoid 11.1 chargebacks?

Always request electronic authorization for every transaction. Never process transactions based on voice authorizations alone unless absolutely necessary. Ensure your POS system is connected and authorizing in real-time. If your system returns a decline, do not override it — the decline exists for a reason.

Can I win an 11.1 chargeback?

Yes, if you have a valid authorization code for the transaction. If your records show the transaction received an electronic authorization approval — not a voice authorization, not a forced authorization — you can successfully represent the dispute. The key is pulling the authorization record that shows a proper approval code.

What is a forced authorization and why is it dangerous?

A forced authorization (also called a force post or offline authorization) bypasses the normal electronic authorization process. Merchants sometimes use these when systems are down or to override a decline. Forced authorizations never check the Card Recovery Bulletin or real-time fraud lists, which is why they create 11.1 liability. They should be avoided except in documented emergencies.

Related Codes & Resources