How the Fair Credit Billing Act Works
The Fair Credit Billing Act establishes a structured, time-bound process for resolving billing errors on open-end credit accounts. Both consumers and creditors have specific obligations and deadlines — and merchants are affected downstream through their acquiring banks. Understanding the mechanics is essential for building dispute-resilient payment operations.
Consumer Files a Written Dispute
The consumer must send a written notice to the creditor's billing inquiry address — not the payment address — within 60 days of the first statement on which the error appears. The notice must include the consumer's name, account number, a description of the error, and the amount in question. Verbal complaints alone do not trigger FCBA protections.
Creditor Acknowledges Within 30 Days
Upon receiving the dispute, the creditor has 30 days to send a written acknowledgment. This acknowledgment does not require resolution — only confirmation that the dispute was received and is under review. The clock on the full investigation starts here.
Investigation Period (Up to 90 Days)
The creditor investigates whether the charge qualifies as a billing error under the FCBA. During this window, the disputed amount cannot be collected, charged interest, or reported negatively to credit bureaus. The creditor contacts the merchant's acquiring bank, which in turn contacts the merchant for evidence.
Merchant Submits Evidence
The acquiring bank forwards a chargeback or retrieval request to the merchant. The merchant must provide documentation — signed receipts, delivery confirmation, customer communication logs, or authorization records — demonstrating the charge was valid and accurate.
Creditor Issues Resolution
The creditor either corrects the billing error or sends the consumer a written explanation of why the charge is valid. If the creditor rules in the merchant's favor, the consumer may still escalate through the card network's own dispute process. If the creditor rules for the consumer, the charge is reversed and the merchant absorbs the loss.
Why the Fair Credit Billing Act Matters
The FCBA is not a niche consumer law — it directly shapes the economics of card acceptance for every merchant in the United States. Its protections are woven into card network dispute rules, meaning non-compliance by creditors exposes them to liability, while merchants who ignore dispute hygiene face avoidable losses.
The scope of the problem is significant. According to Mastercard estimates, global chargeback volume exceeded 615 million transactions annually by the mid-2020s, costing merchants an estimated $117 billion when accounting for lost merchandise, fees, and operational overhead. The FCBA's 60-day dispute window is a key driver of this volume — it gives consumers a broad, federally protected right to challenge charges long after a transaction settles.
The CFPB reports that credit card complaints consistently rank among the top categories of consumer financial complaints filed each year, with billing disputes representing a substantial share. For ecommerce merchants specifically, card-not-present transactions carry higher dispute rates — often 3–5× those of card-present transactions — making FCBA-driven chargebacks a material revenue risk. Merchants operating without clear billing descriptors or robust order documentation are disproportionately affected, since ambiguous charges are more likely to be reported as billing errors under consumer protection statutes.
FCBA vs. Network Chargeback Rules
The FCBA sets the legal floor for consumer billing dispute rights. Card networks like Visa and Mastercard layer their own chargeback rules on top — often with shorter dispute windows, different reason codes, and their own evidence requirements. Merchants must satisfy both frameworks simultaneously.
Fair Credit Billing Act vs. Electronic Fund Transfer Act
The FCBA and the Electronic Fund Transfer Act (EFTA) are frequently confused because both govern payment disputes, but they apply to entirely different account types and carry different liability structures.
| Dimension | Fair Credit Billing Act (FCBA) | Electronic Fund Transfer Act (EFTA) |
|---|---|---|
| Account type | Open-end credit (credit cards, revolving credit) | Deposit accounts (debit cards, ACH, EFT) |
| Implementing regulation | Regulation Z | Regulation E |
| Dispute window | 60 days from statement date | 60 days from statement date |
| Acknowledgment deadline | 30 days | Not required |
| Resolution deadline | 90 days / two billing cycles | 10 business days (provisional credit) |
| Consumer liability cap | $50 for unauthorized charges | $50–unlimited depending on report timing |
| Interest during dispute | Suspended | N/A (no interest on deposits) |
| Merchant recourse | Evidence-based rebuttal | Evidence-based rebuttal |
The practical implication: a merchant accepting both credit and debit cards must maintain separate dispute workflows aligned to each regulatory regime.
Types of FCBA-Covered Billing Errors
The FCBA defines billing errors precisely. Not every consumer complaint qualifies — and understanding the taxonomy helps merchants identify which disputes are legally grounded versus which may constitute friendly fraud.
Unauthorized charges — Transactions the consumer did not authorize, including fraudulent card use. This is the most common FCBA claim category.
Goods or services not delivered — Charges for merchandise or services the consumer did not receive, or that were not delivered as agreed. Common in ecommerce where fulfillment disputes arise.
Computational or mathematical errors — Arithmetic mistakes in the billing statement, incorrect currency conversions, or duplicate posting of the same transaction.
Failure to post payments or credits — When a payment made by the consumer is not reflected on the statement, or an agreed-upon credit (refund, return) was not applied.
Charges for which a consumer requests documentation — Consumers can request written clarification or documentation for any charge. Creditors must respond, even if no error exists.
Charges to the wrong account — Transactions correctly executed but posted to an incorrect account number.
Best Practices
Every disputed charge is a recoverable situation if merchants maintain the right documentation and processes from the moment of sale.
For Merchants
Use precise billing descriptors. Your billing descriptor is the first line of defense — ambiguous descriptors are the top trigger for "I don't recognize this charge" disputes. Include your DBA name, a recognizable product category, and a customer service phone number.
Capture proof of delivery. For physical goods, require signature on delivery for high-value orders. For digital goods, log IP address, device fingerprint, and access timestamps at the moment of fulfillment.
Maintain transaction records for at least 18 months. Card network rules and the FCBA's dispute windows mean you may receive a dispute six months after a transaction. Records must be retrievable quickly.
Respond to retrieval requests immediately. When your acquirer forwards a retrieval request, treat it as urgent. Delays in responding convert retrievable disputes into uncontested chargebacks.
Communicate proactively with customers. A customer who can reach you easily is far less likely to escalate to a card dispute. Display customer service contact information prominently in confirmation emails and on your website.
For Developers
Log authorization data immutably. Store authorization codes, AVS/CVV response codes, 3DS authentication results, and device fingerprints in append-only records tied to the order ID.
Build dispute webhooks into your integration. Most acquiring banks and payment processors emit webhook events for chargeback notifications. Automate evidence packaging — pull order records, shipping data, and communication logs programmatically the moment a dispute event fires.
Implement idempotent payment flows. Duplicate charges are a common source of FCBA billing error claims and are entirely preventable with proper idempotency key handling.
Surface dispute reason codes in your dashboard. Map acquiring bank reason codes to FCBA error categories so your operations team can triage disputes by type and identify patterns.
Common Mistakes
Ignoring retrieval requests. A retrieval request is a warning, not a chargeback. Merchants who miss the response window automatically lose the subsequent chargeback — turning a winnable dispute into a certain loss.
Submitting incomplete evidence packages. Generic responses like "the customer made this purchase" without supporting documentation — signed authorization, delivery confirmation, IP logs — fail to rebut the specific billing error alleged. Evidence must directly address the consumer's claimed error type.
Conflating the FCBA with card network chargeback rules. Winning at the card network level does not mean the creditor's FCBA investigation is closed. Merchants sometimes stop following up after a chargeback reversal, not realizing the consumer can still pursue the FCBA process separately.
Missing the 60-day consumer window assumption. Merchants sometimes assume disputes filed after 60 days are automatically invalid. Card networks have their own — sometimes longer — dispute windows that operate independently of the FCBA timeline.
Failing to update billing descriptors after rebrands. Post-acquisition or rebrand scenarios where the billing descriptor no longer matches the brand consumers recognize are a leading source of "unauthorized charge" claims that are actually recognition failures, not fraud.
Fair Credit Billing Act and Tagada
The FCBA creates compliance obligations that ripple through every layer of a payment stack. As a payment orchestration platform, Tagada helps merchants manage dispute exposure systematically rather than reactively.
Dispute Automation with Tagada
Tagada's orchestration layer can be configured to route transactions through acquirers with the strongest dispute resolution support for your vertical, normalize chargeback webhook events across multiple processors into a single format, and trigger automated evidence-gathering workflows the moment a dispute notification arrives — reducing the manual overhead of FCBA-driven chargeback responses.
For merchants operating across multiple acquiring relationships, Tagada provides unified visibility into dispute rates by processor, card type, and product category — making it possible to identify whether a spike in FCBA-style billing error disputes is driven by a descriptor issue, a fulfillment problem, or a specific acquirer's reporting behavior. This operational clarity is essential for merchants who want to address root causes rather than dispute chargebacks one at a time.