Mastercard 4837 - No Cardholder Authorization
This is the Mastercard code for a customer denying an online or phone order: 4837. Looking for Visa 10.4, Amex F29 or Discover UA02?
Identify the network from your notice, not from punctuation or code shape. Formats vary, and newer Discover codes have four digits.
- 4837 is Mastercard's no-cardholder-authorization chargeback reason code
- The customer says they didn't authorize the charge and didn't take part in it
- Identity Check (3D Secure) has an authenticated-transaction route. On eligible payments it can shift liability to the issuer
- Without an eligible authenticated-transaction defense, assess every applicable remedy: AVS X or Y plus delivery to that address (not Maestro, Mastercard's debit scheme, or Mainland China domestic transactions), compelling evidence, an existing refund, or an invalid chargeback
- Use the filing condition and regional rule for this case
- Notice says 4863, "cardholder does not recognize"? Treat it as an older label and confirm the actual claim and case code. Older 4863 labels.
Got this code?
Your deadline: The date on your notice wins. Ask your processor if it isn't clear: the network's issuer filing window isn't your response deadline.
The claim: The customer told their bank they didn't make this purchase.
Records that answer it:
- Identity Check (3D Secure) records: liability may have shifted
- Earlier undisputed transactions from the same customer, for compelling evidence
- AVS X or Y with delivery to that address (not Maestro or Mainland China domestic)
Next: Decide whether it's worth fighting, then fill in the response outline for this claim and follow the Representment Workflow.
Records by what you sell
The same claim needs different records depending on what you sold. Find your column.
| What you sell | Shipped goods | Digital or online | In person or a service |
|---|---|---|---|
| Records that answer it |
|
|
|
| Where to find them |
|
|
|
Sources: Stripe's evidence by product type VENDOR; Stripe's dispute response form VENDOR; Shopify's evidence by reason VENDOR; Shopify's order risk analysis VENDOR; Square's dispute walkthrough VENDOR; Square's transaction search VENDOR. Source links accessed 24 October 2026; follow the labels shown in your processor dashboard.
Overview
You aren't arguing about whether the charge happened. You're arguing about who made it. Your evidence has to name a person, not a transaction. Identity Check can do that on its eligible route. The rest of this page is what you do without it.
When This Code Applies
-
Customer denies authorizing the transaction
-
Card was lost, stolen, or never received
-
Counterfeit card was used
-
Card-not-present fraud
Transactions Ineligible for This Chargeback
- The issuer filed outside the window for this condition and region
- Properly authenticated transaction with liability shift
- Transaction already charged back under a different reason code
- A network-defined card-account takeover reported as a takeover. A takeover of your shop login is a different case and doesn't take this exclusion
- A different card number (PAN) in supporting documents isn't enough on its own. It can legitimately differ from the clearing card number, so compare the actual first-presentment identifiers
- A related merchant-initiated payment tied to a qualifying authenticated original customer-initiated transaction (CIT), with evidence linking the later payment to it. A recurring flag and initial consent alone aren't enough
Time Frames
These are the customer's bank's (the issuer's) filing deadlines, not yours. A chargeback filed after its window can be invalid.
| Case | Issuer filing window |
|---|---|
| General 4837 issuer filing, outside Mainland China domestic | 120 calendar days from the sale's applicable network business date |
| Mainland China domestic issuer filing | Between 5 and 90 calendar days from the date the sale settled, counting that first day as day zero |
| Other regional and product cases | Their own clocks and start events. Confirm the one for your case with your processor |
Source: Mastercard Chargeback Guide, 13 May 2025, No Cardholder Authorization, Issuer Chargeback, pp. 419-420. Checked 3 November 2026.
Use the response date on your notice. The network's issuer filing window isn't your merchant response deadline. Ask your processor, which works with your acquirer (the bank behind your processor): "Which claim and Mastercard rule apply to this case, and what's my last date to send you evidence?" Don't rely on a filing-window summary without it.
Representment Options
1. Addendum Charges
You disclosed the extra charges up front and the customer took part. This route excludes Maestro. Your records have to show two things: the customer took part in the original sale, and they were responsible for this particular extra charge. Where the charge is for loss, theft or damage, include what those cases require.
Requirements:
- Original transaction was undisputed
- Addendum charges were disclosed at time of original transaction
- Customer signed or otherwise agreed to terms
2. Address Verification Service (AVS)
Requirements:
- AVS response was X or Y
- Goods shipped to AVS-confirmed address
- Not available for Maestro or for domestic Mainland China transactions
Documentation needed:
- Proof of AVS response X or Y
- Proof merchandise sent to AVS-confirmed address
- Shipping carrier confirmation
3. Authenticated Transaction
The transaction went through 3D Secure/Identity Check. Confirm the complete qualifying authentication and approved authorization records first. A trailing security-level digit of 1 or 2 doesn't by itself establish every authentication condition. Mainland China uses its specified comment field, not a universal message-field rule.
Message text: Your processor enters this in the message field (DE 72). You supply the authentication and authorization records behind it:
AUTH MMDDYY/NNNNNN SL 1when the approved authorization request's security-level indicator is 1. MMDDYY is the approval date; NNNNNN is the authorization approval code.AUTH MMDDYY/NNNNNN SL 2when the approved authorization request's security-level indicator is 2. MMDDYY is the approval date; NNNNNN is the authorization approval code. Use the correct country and message variant (Mastercard Chargeback Guide, 13 May 2025, Authenticated transaction, pp. 423-425).
4. Compelling Evidence (E-commerce/MO/TO)
The compelling-evidence routes in sections 4 to 7 apply only to non-Maestro transactions (Chargeback Guide, Compelling evidence, pp. 425-428).
Provide at least one of:
| Evidence Type | Description |
|---|---|
| Signed document | Signed document that substantiates receipt |
| Delivery confirmation | Written confirmation of electronic delivery registration |
| Correspondence | Email, SMS, or chat that shows the customer took part in the transaction |
| Pickup statement | Merchant statement documenting in-store pickup location |
| Partial shipment | The initial sale's details, proof that sale went undisputed, and a description of what shipped. Behind it, your processor needs one of two records: the qualifying authentication, or proof the security code (CVC2) was supplied and matched. Mainland China has its own authentication route |
Message text: Your processor includes COMP EVID in the message field. For Mainland China domestic cases the acquirer uses the China Switch comment field instead
5. Compelling Evidence (Registered Account)
You require an account before purchase. Show registration using an authentication method, plus one or more of these supporting records. Registration by itself isn't enough:
| Evidence Type | Supporting record |
|---|---|
| Undisputed purchases | Other transactions from same registered account |
| Device and IP match | Transaction from the registered device and IP address |
| Purchase details | Full order information |
| Delivery proof | Signed proof of delivery |
| Digital delivery | Email addresses for digital goods |
| Product registration | Disputed goods registered for warranty/updates |
| Usage proof | Evidence disputed goods were used |
| Identity Check | Fully enabled Identity Check used for PAN registration |
This defense doesn't apply to guest checkout purchases.
6. Compelling Evidence (Airlines)
Provide at least one of:
| Evidence Type | Description |
|---|---|
| Boarding documents | Flight ticket or boarding pass with passenger name |
| Manifest | Flight manifest/itinerary with passenger name |
| Connected charges | Upgrades, baggage, in-flight purchases |
| ID linkage | Passenger ID linked to the customer |
| Loyalty credits | Frequent flyer miles credited |
| Ticket delivery | Proof of ticket receipt (signed delivery, email) |
7. Compelling Evidence (Recurring/Installments)
Provide all of:
- Description of goods/services provided
- Start date with:
- Original transaction authorization date
- Authorization approval code
- The original customer-initiated transaction value, if there is one
- Proof the original payment was an authenticated customer-started payment, or that the security code (CVC2) was supplied and matched, with the response record behind that match. Your processor supplies the record; for Mainland China domestic cases it's the financial response
- Either proper recurring or installment identification in authorization and clearing, or the specified proof of recurring consent
8. Gaming Payment Transactions
The customer received a later, undisputed gaming payment after the funding transaction they're disputing. Explain how that payment relates to the funding transaction.
Documentation required (per gaming payment):
- Date of each Gaming Payment Transaction
- Switch Serial Number or ARN
- Transaction amount
9. Guaranteed Reservation ("No-Show")
For hotel no-show charges, establish that the charge complied with the applicable Guaranteed Reservation Service rules. That takes all of:
- Proper disclosure of the cancellation policy
- Customer didn't cancel inside the policy window
- The reservation went unused
10. Refund Previously Issued
You already refunded this payment. This route isn't available for ATM transactions. Document the matching refund in a timely second presentment. A refund on another transaction doesn't answer this one, and an unrefunded remainder can still be disputed.
Documentation:
- Proof of refund with date
- Refund ARN or transaction ID
- Amount refunded
11. Invalid Chargeback
Sometimes the chargeback itself is bad. Mainland China domestic cases are out for two of these defenses, account takeover and card-number mismatch. The others keep their own China eligibility, data and message rules. Check the exact test that fits:
| Reason | Description |
|---|---|
| Account takeover | The network's card-account takeover case. A takeover of your shop login is a different case |
| Counter exceeded | The account's fraud counter has passed 35, where that specific test applies |
| Prior fraud claims | The issuer approved after prior fraud claims, where that specific test applies |
| No fraud report | Not reported to the Fraud and Loss Database, allowing for the three-day reporting tolerance |
| Contactless | A contactless transaction meeting the specified unattended-terminal conditions |
| PIN verified | PIN transaction |
| Invalid filing | Chargeback doesn't meet requirements |
| Time frame | Past allowable filing window |
| Duplicate | Same transaction already charged back |
| Card number mismatch | A different card number (PAN) in supporting documents alone isn't enough. Compare the actual first-presentment identifiers |
| Documentation | Supporting docs not received, illegible, or incomplete |
| Message text | Invalid or missing message text |
Second Presentment Time Frames
Each row counts from the date the chargeback settled (or its applicable network business date).
| Region | Window |
|---|---|
| Standard second presentment | 45 calendar days from the date the chargeback settled (or its applicable network business date) |
| Costa Rica domestic second presentment | 10 calendar days from the date the chargeback settled (or its applicable network business date) |
| Kazakhstan domestic second presentment | 30 calendar days from the date the chargeback settled (or its applicable network business date) |
| Mainland China domestic second presentment | 30 calendar days from the date the chargeback settled (or its applicable network business date) |
| Nigeria domestic second presentment | 2 business days from the date the chargeback settled (or its applicable network business date) |
| Tanzania domestic second presentment | 20 calendar days from the date the chargeback settled (or its applicable network business date) |
Pre-Arbitration
When Issuer Can File Pre-Arbitration
After receiving second presentment, match the issuer's route and documents to the defense you actually submitted. These reasons aren't interchangeable:
- Chargeback was valid
- AVS evidence invalid or goods not shipped to confirmed address
- Transaction wasn't authenticated
- Compelling evidence insufficient
- Gaming payment evidence insufficient
- Refund wasn't issued
Issuer Must Provide
For AVS disputes:
-
Invalid AVS: denial that a positive AVS result was given, or denial that merchandise went to the AVS address
-
Confirmed AVS: confirmation the address was the customer's at authorization time, plus a new statement written after second presentment denying authorization, by the permitted statement or Form 0412 route
For Authenticated Transaction disputes:
- The matching cardholder information for that route, and a new post-presentment statement where that route requires one
For Compelling Evidence disputes:
- An explanation of why your evidence isn't compelling, OR
- A new customer statement (letter, email, Form 0412) dated after second presentment
Pre-Arbitration Time Frames
| Region | Window |
|---|---|
| Standard pre-arbitration | Issuer: 30 calendar days in the standard case, from the date the second presentment settled or its applicable network business date |
| Costa Rica domestic pre-arbitration | Issuer: 10 calendar days from the date the second presentment settled or its applicable network business date |
| Tanzania domestic pre-arbitration | Issuer: 10 calendar days from the date the second presentment settled or its applicable network business date |
Documentation Waiting Periods
When documentation is indicated to follow, the issuer waits before filing pre-arbitration. Filing can start earlier when the documentation arrives, as the route specifies:
- Costa Rica domestic: 3 calendar days
- Tanzania domestic: 4 calendar days
- ATM/Maestro: 10 calendar days for documentation
- All other: 8 calendar days for documentation
Arbitration
If pre-arbitration doesn't settle it:
- The issuer escalates. Standard case: within 15 calendar days of Mastercom's Rejected Date, or 10 for Costa Rica and Tanzania domestic. ATM/Maestro: 45 calendar days from the date the second presentment settled (or its applicable network business date) (Mastercard Chargeback Guide, 13 May 2025, Issuer Submission of an Arbitration Case, p. 479)
- Follow the issuer and acquirer translation duties. Brazil domestic documents can be in English or Portuguese
- Mastercard rules on the case. A separate limited appeal route can follow a ruling, with its own 45-day clock from the ruling date and limits on new facts. It isn't another initial filing window (Chargeback Guide, Appeals, pp. 679-681)
- You respond through your processor. Ask it for the filing and review fees, who pays them, and what it needs from you before the case escalates
Which defenses hold up
Use the documented route that fits your notice. The guide sets routes, not win rates.
| Defense Type | How it holds up |
|---|---|
| 3D Secure authenticated | Confirm the full qualifying authentication and authorization conditions for that route |
| AVS match + delivery proof | Use it where X or Y and delivery to that address meet the route's scope |
| Compelling evidence | The record has to establish participation or receipt under the route you use |
| Refund or invalid chargeback | Use those routes where their own conditions fit |
| No evidence | No documented route on these facts. Measure your own results by route |
Track your own win rate by reason code instead of relying on a general figure.
Retired 4863: Cardholder Does Not Recognize
4863 is a legacy label. It doesn't appear in the 13 May 2025 Mastercard Chargeback Guide. That edition uses 4837 for no-cardholder-authorization claims.
Route by the actual claim. Confirm it with your processor. A no-cardholder-authorization claim belongs on this page. A customer who recognizes the charge but disputes what they got may fit a 4853 - Cardholder Dispute condition.
Seeing 4863 on a current notification? Ask your processor for the actual case code, claim and response deadline. Don't dismiss the notice or assume the response from the label alone. If the issuer's claim is no cardholder authorization, use the 4837 evidence requirements.
| Code | Customer Statement | Implication |
|---|---|---|
| 4863 (older label) | "I don't recognize this" | A recognition question. Confirm what the customer actually claimed |
| 4837 | "I didn't do this" | Fraud claim |
A recognition question and an unauthorized-payment claim aren't the same thing. Confirm what the customer actually claimed before choosing a response.
The descriptor advice still matters
If your descriptor confused the customer, it can arrive under an older 4863 label or as a current claim. Fix your descriptor first, and confirm the actual claim before you respond.
What caused the confusion:
- Descriptor issues. The business name differs from the storefront name. The parent company name shows instead of the brand. Names abbreviated, truncated, or a generic processor name
- Legitimate confusion. They forgot about the purchase, or a family member made it. A subscription renewed, or a delivery charged late
- A precursor to fraud. Testing the water before a full fraud claim. Genuine fraud they're unsure about, or an account takeover
| Before | After |
|---|---|
PAYCO*12345 800-555-1234 | BRANDNAME.COM 800-555-1234 |
GLOBAL MERCHANT SVC | BRANDNAME*PRODUCT TYPE |
UNKNOWN MERCHANT | BRANDNAME CITY ST |
- Use a recognizable name - The brand name customers know
- Include a phone number - Easy to call before disputing
- Be consistent - Same name across all touchpoints
- Include location - City and state for brick-and-mortar
- Match advertising - Same name in marketing
Then make the charge easy to look up. Show the exact descriptor on receipts and order confirmations, link shipping notices to the original purchase, and give customers a self-service history. For subscriptions, send a reminder before billing ("You'll be charged..."), bill on the same day each cycle, and put "SUBSCRIPTION" or "MONTHLY" in the descriptor. More in Descriptors and Communication.
The old defenses still explain what to collect. A clear descriptor and delivery proof. Prior undisputed purchases. A subscription agreement and billing history. The customer acknowledging the purchase. Under 4837, check the compelling evidence requirements. You need evidence tying the person to the purchase.
Related Codes
- 4863 Cardholder Does Not Recognize (older label; confirm the actual claim)
- 4853 - Cardholder Dispute, when the customer recognizes the charge
- 4870 - Chip Liability Shift
- 4871 - Chip Lost/Stolen/NRI
Prevention Strategies
For E-commerce
- Turn on 3D Secure - On eligible payments it can shift liability to the issuer
- Run AVS and CVV - Store the results
- Require an account with authentication-based registration - Keep supporting records with it. Registration alone doesn't create the defense
- Send order confirmations - To verified email addresses
- Use delivery confirmation - Signature where you can
- Keep logs - Device fingerprints, IPs, session data
For Recurring/Subscriptions
- Get consent in writing - With the terms attached
- Remind before billing - Use the timing required for your subscription type and billing interval
- Make cancelling easy - Same channel as signup
- Flag it as recurring - In auth and in clearing
- Keep the original auth details - For compelling evidence
For High-Risk Transactions
- Score before you authorize - Pre-transaction screening
- Run velocity checks - Multiple orders, same parameters
- Watch first orders - New accounts get more scrutiny
- Flag address mismatches - Billing vs shipping
Next Steps
Prevent future 4837 chargebacks:
- Implement 3D Secure for liability shift
- Configure velocity rules to catch fraud patterns
- Set up dispute alerts to refund before chargeback
See Also
- Reference - The whole reference section
- Time Frames - Dispute and response deadlines
- Refund or fight - Accept or fight it, and why you don't send a refund
- What proof Visa, Mastercard and Amex accept - Evidence requirements
- 3D Secure Authentication - Identity Check
- Friendly Fraud - First-party abuse
- Third-Party Fraud - True fraud patterns
- Account Takeover - ATO defense
- Device Fingerprinting - Proving involvement
- AVS & CVV - Address verification
- Velocity Rules - Fraud detection
- Risk Scoring - Pre-transaction screening
- Chargeback Alerts - Ethoca for MC
- Mastercard ECP program limits - Program limits
- Fraud vs. Friendly - Classification