Skip to main content

Why Issuers Decline and Dispute

TL;DR
  • Issuers (your customers' banks) see far less in an ordinary authorization than you hold. 3DS can send them much more, if your integration provides it
  • A decline can turn on the cardholder's history and on what data reached them, not on your fraud signals
  • US consumer rules (Reg E for debit, Reg Z for credit) set the bank's investigation clock with its customer. Your evidence can answer the claim, alongside the bank's own records
  • Issuers want to approve legitimate transactions but need help identifying them
  • Understanding issuer constraints helps you get more payments approved and win more disputes
Scope

This page covers why issuers decline transactions, and what they need from you on a dispute. For the issuer's dispute process step by step, see Issuer Side of Chargebacks. For the technical deep dive on authorization logic, see Authorization Decisioning.

Your order passed every check you run, and the customer's bank declined it anyway. In an ordinary authorization, that bank may see little of what you hold. On a dispute it has its customer's word, its own records and whatever evidence you send, so the records you collect matter.


What Issuers See​

When you send an authorization request, you might hold 50+ data points: device fingerprint, session behavior, address history, account age, velocity patterns. An ordinary authorization message carries little of that. 3DS is a separate exchange that can carry much more.

What an ordinary authorization can carry, depending on your integration:

Data PointWhat They See
Transaction amount$127.50
Merchant name"ACME STORE"
MCC5411 (Grocery)
Billing address123 Main St, if you send it for AVS and it's supported
Security codeThe code you supplied, if supported. The issuer checks it and returns the result (Stripe's verification checks)
Cardholder nameJohn Smith, depending on the integration

What 3DS can add: EMV 3DS can give the issuer's authentication system device and browser data, shipping details and the customer's account history with you (EMVCo's white paper; Visa's Better Data guide, copyright 2024, pp. 1 and 3-4). Not every integration sends every field, so ask your provider what yours sends.

What you shouldn't assume the issuer sees:

  • Your fraud score
  • Session behavior (time on site, pages viewed)
  • Product category or cart contents

So the issuer can be deciding with little context about your specific transaction.


Why Issuers Decline Legitimate Transactions​

Issuers decline for reasons that have nothing to do with your fraud controls:

Decline ReasonWhat's HappeningYour Fix
Unusual spending patternCardholder doesn't normally shop your MCCUse the actual decline reason. Ask the customer to contact their bank, or offer another payment method
Geographic anomalyTransaction from unusual location for this cardholderAsk the customer to contact their bank. Better authentication and data can help some cases
Velocity flagCardholder has hit their own daily limitsOffer another payment method, or ask the customer to contact their bank
Your merchant historyA possible input on your MID. Its weight varies by issuerMeasure declines by issuer and reason, and fix your ratios
Merchant-category restrictionIssuer blocks certain merchant categories. That's your MCC. A BIN identifies the card rangeA hard restriction won't move at checkout. Offer a permitted alternative, or ask the customer to contact their bank

A decline can be about the cardholder's history, not your transaction.

The False Decline Problem​

Separate fraud-flagged declines from other reasons, then review which declined orders were legitimate. A count share isn't a dollar share. Price blocked good orders using their actual values and margins.

False declines can cost repeat business too. Javelin's 27 August 2015 research announcement says 39% of declined cardholders reported abandoning their card after a false decline. The report included a survey of 3,200 US adults; the public release doesn't give the declined subgroup's size. That's a historical survey result, not a forecast for your customers. REPORTED, accessed 2026-10-22.


Why Issuers Side with Cardholders on Disputes​

When a cardholder disputes a charge, Reg E (debit) and Reg Z (credit) create specific obligations:

Reg E (Debit Cards)​

RequirementWhat It Means for Merchants
After a qualifying error notice from a consumer, the bank normally decides within 10 business days of receiving it. That's 20 business days for a transfer within 30 days after the account's first depositThat's the bank's clock with its customer. It doesn't tell you when your case clock starts. Work to the date on your notice
The bank can extend to 45 calendar days from the same notice if it gives provisional credit. There are exceptions, such as written confirmation it asked for and didn't get. It's 90 days for POS debit, transfers not initiated in a state, and that new-account transfer (CFPB Regulation E, section 1005.11)The customer may already have the credit while the bank investigates
Consumer liability for an unauthorized transfer depends on whether the card was lost or stolen, when the customer reports it, and when each transfer happenedA customer who reports promptly risks little by disputing. The tiers

Reg Z (Credit Cards)​

RequirementWhat It Means for Merchants
Liability for unauthorized use capped at $50. Visa and Mastercard zero liability can make eligible claims $0, on their conditionsLittle downside to disputing an unauthorized-use claim
A "billing error" includes goods or services not accepted or not delivered as agreed, on a written notice received within 60 days of the first relevant statement (section 1026.13)A quality complaint about goods they accepted isn't a billing error. The separate claims-and-defenses route has its own conditions (section 1026.12(c))
Issuer must investigateIt can use its own records as well as yours. Send what answers the claim
Customer can withhold the disputed amount while the billing-error procedure runsThe money argument happens after they're protected, not before
The Evidence Problem

The issuer didn't see the delivery or watch the customer use the product. It does have its own records, authentication and transaction history, and its own duty to investigate. Both rules also let it correct an error without investigating, on stated conditions (Regulation E, Regulation Z).

So you aren't the only source of proof, but you may hold the records that answer the claim. Send those.


What Issuers Need From You​

For Authorization (Improve Approval Rates)​

ActionWhy It Helps
Use 3D SecureThe issuer authenticates the cardholder itself. Measure the effect on approvals by issuer
Send clean trafficYour fraud history can be an input to issuer models. Measure your declines by issuer and reason
Send better dataWhere your 3DS integration supports it (Visa's Better Data guide)
Don't retry aggressivelyRepeated retries can look like fraud to an issuer. Follow the actual decline reason

For Disputes (Win More Representments)​

Send the records that answer the claim:

Dispute TypeEvidence to SendWhat It Shows
"I didn't authorize this"3DS authentication result, IP/device match to prior ordersThe buyer's own devices and history on this purchase
"Never received"Signed delivery confirmation, GPS delivery photoDelivery to the address on the order
"Not as described"Product photos, description at checkout, correspondenceWhat was promised vs. delivered
"Canceled but still charged"Cancellation policy shown at checkout, cancellation confirmationThe policy the customer agreed to, and when any cancellation landed
"Already refunded"Refund transaction ID, date, amountA succeeded refund already covering this sale
The Compelling Evidence Standard

Use Visa CE 3.0 to check whether qualifying history supports a Visa 10.4 response. Device or IP history alone isn't enough. Ask your processor: "Does case [ID] qualify for Visa CE 3.0? Which requirements does it meet, and which records do you still need from me?"


What Issuers May Track About You​

Your merchant history can be one input to an issuer's decisions. How much it weighs varies by issuer, so measure your own declines by issuer and reason (fraud metrics):

MetricWhat it can feed
Chargeback ratioIssuer decisions, and possible program enrollment
TC40/SAFE fraud reportsIssuer models, even without a chargeback
MCC riskAn issuer may look harder at some categories. Check your own decline data
Historical patternsTrack how long a change takes to show up in your own approvals
TC40/SAFE Reports

Even if you prevent a chargeback through an alert or refund, issuers may still file a TC40 (Visa) or SAFE (Mastercard) fraud report. These can feed issuer models even when you never see a dispute.


Working With Issuer Constraints​

Improve Auth Rates​

  1. Reduce chargebacks: Your chargeback ratio can feed issuer decisions and program tests
  2. Use 3DS strategically: Issuers run their own authentication. Compare approvals by issuer
  3. Send better data: Where your 3DS integration supports it. Measure the result
  4. Fix soft declines properly: Don't retry hard declines. Retry a soft decline only where its response allows it, at sensible intervals

Win More Disputes​

  1. Collect evidence before you need it: IP, device, delivery confirmation, screenshots
  2. Use CE 3.0 through its checklist: Qualifying earlier purchase history, checked against the requirements, not a device match alone
  3. Work to the date on your notice: Reg E's clock is the bank's clock with its customer. Yours is on the case notice
  4. Be specific: Generic evidence doesn't help; show exactly what happened
  5. Share purchase details: Order Insight and Consumer Clarity put your logo and item details in banking, call-center and dispute-recognition channels. That helps recognition. Don't count on it raising approvals

Build Long-Term Reputation​

  1. Keep ratios within your written limits: Confirm the metric with your processor and check network program conditions. No single ratio promises that issuers will ignore you
  2. Respond to alerts: A matching Ethoca or Verifi alert from a participating issuer can stop a covered dispute becoming a chargeback, if you complete the response in time (Ethoca Alerts). It doesn't guarantee coverage or erase a TC40 on a fraud claim
  3. Don't fight everything: Accept a valid chargeback you're liable for when no permitted remedy applies. First check the actual condition, eligible authentication, prior credits and whether the claim is invalid (Mastercard's guide, 13 May 2025, 4837, pp. 423-425). True fraud alone doesn't decide it

Next Steps​

Improving auth rates?

  1. Optimize authorization: Reduce declines
  2. Implement 3DS: Issuer authentication
  3. Check decline codes: Understand why you're being declined

Winning more disputes?

  1. Review Compelling Evidence: CE 3.0 requirements
  2. Build evidence collection: What to gather upfront
  3. Understand reason codes: What evidence each code needs

Understanding issuer regulations?

  1. Review Reg E: Debit card rules
  2. Review Reg Z: Credit card rules
  3. Check network programs: VAMP, ECM thresholds

Something wrong on this page? Email matt at paymentsandrisk.com and say what needs fixing.