Mastercard 4837 — No Cardholder Authorization

Mastercard 4837: the cardholder says they didn't authorize it

By · Updated

Checked by three automated reviewers (facts against the playbook, search, and our rules), then approved by the author on .

Mastercard 4837 means the cardholder says they didn't authorize the payment. Mastercard's answers include Identity Check, an address check answered X or Y with the goods sent there, and history from buyers who had to register and sign in; guest-checkout history doesn't count. If you suspect a fraudster placed it, accept, whatever the account history.

Start a free draft

The bank's test

The bank checks:

  1. Was the payment authenticated with 3D Secure? If so, fraud liability usually sits with the card issuer.
  2. Does anything link this cardholder to the seller: earlier undisputed payments, the same IP address or device, the same account or email?
  3. Did the purchase go somewhere the cardholder controls: their billing address, their email, their login?
  4. Did the cardholder use what was bought?

Evidence that answers it

“Where it goes” uses the names Stripe's and Square's APIs give each piece of evidence, which are the names Upheld uses in your packet. Nothing is sent without your approval; where Upheld can't send it for you, you submit it yourself. In Stripe's Dashboard, choose the matching type for each file or text field. In Square's, add it when Square asks you to “upload any additional evidence specific to your service type”.

Evidence for Mastercard 4837, by kind of business
EvidenceWhen it countsHow to show itWhere it goesFor
Messages with the customerShowing the cardholder took part in the purchase (Mastercard names letters, emails, texts and chat messages).The relevant messages only, dated, with the key lines highlighted or quoted in the response.Stripe: Customer communicationSquare: Cardholder communicationEvery seller
3D Secure authenticationIf the payment was authenticated with Mastercard Identity Check.State that the payment was authenticated with 3D Secure and the result. For fraud disputes this usually moves liability to the bank.Stripe: Uncategorized text. There's no field of its own: for a payment that shifts liability, Stripe adds the 3D Secure result itself, so mention it in your letter.Square: Authorization documentationEvery seller
Address and security-code checksWhen the address check answered X or Y and the goods went to that confirmed address.Report the check results as Stripe recorded them. Supporting evidence only, never the main argument.Stripe: Uncategorized text. There's no field of its own: mention the address and card code results in your letter.Square: Authorization documentationEvery seller
Proof of deliveryShowing delivery signed for by the cardholder, or to the address the address check confirmed.The carrier's delivery record showing date, address, and any signature or photo.Stripe: Shipping documentationSquare: Proof of delivery documentationOnline stores
Billing and shipping addresses matchThe order was sent to the cardholder's own billing address or a previously used address.Show both addresses side by side.Stripe: Billing address or Shipping addressSquare: Cardholder informationOnline stores
Access granted or digital product deliveredShowing the goods were delivered electronically, with the cardholder's written confirmation that they registered to receive electronic delivery. Only when buyers must register with a password or other authentication before buying (never a guest checkout): customer account history showing the registration, earlier payments from the same customer before or after the disputed one, customer IP address and device from a registered device and IP address, and access and usage log showing the goods or services were used. For a recurring charge: recurring billing agreed at signup showing the cardholder clicked to accept the recurring terms, and subscription billing history with the start date.The delivery or welcome email, or the platform record showing when access was granted and to which email.Stripe: Access activity log or Customer communicationSquare: Online or app access logCourses, memberships, digital products
Customer account historyThe buyer has an account with the seller — created on a known date, used repeatedly, tied to the cardholder's email.Account creation date, email, login count and dates, earlier orders. A screenshot or export from the seller's platform.Stripe: Uncategorized file or Uncategorized textSquare: Cardholder informationCourses, memberships, digital products
Earlier payments from the same customerThe same customer paid before without disputing, linking this purchase to a known buyer.List each earlier payment with date and amount, and which identifiers match the disputed one (email, IP, device, shipping address, account).Stripe: Uncategorized textSquare: Related transaction documentationCourses, memberships, digital products
Customer IP address and deviceThe purchase came from an IP address or device linked to the cardholder's other activity.Give the purchase IP and show the same IP or device on logins or earlier orders.Stripe: Customer purchase IPSquare: Cardholder informationCourses, memberships, digital products
Access and usage logThe customer actually used what they bought — logins, lessons viewed, files downloaded, features used.Dated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.Stripe: Access activity logSquare: Online or app access logCourses, memberships, digital products
Recurring billing agreed at signupThe customer agreed to be charged repeatedly, at a stated amount and interval.The signup page or email showing price, interval, renewal, and how to cancel, with the date the customer signed up.Stripe: Cancellation policy disclosure or Uncategorized fileSquare: Purchase acknowledgementCourses, memberships, digital products
Subscription billing historyWhen the subscription started, each renewal, and that earlier renewals weren't disputed.Start date, plan, each charge date and amount, status.Stripe: Cancellation rebuttal or Uncategorized textSquare: Related transaction documentationCourses, memberships, digital products
Signed contract or agreementThe customer agreed in writing to the scope, price, and terms, a work order or other document signed by the cardholder showing they received the service.The signed document with the signature and the relevant clauses marked.Stripe: Customer signature or Service documentationSquare: Purchase acknowledgementServices
Service deliveredThe service took place — a session was attended, work was delivered, an event happened.Dates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.Stripe: Service date or Service documentationSquare: Service received documentationServices

Start a free draft

What doesn't help

  • A security-code match on its own; it shows the buyer had the card details, not that they were the cardholder.
  • Earlier purchases from a guest checkout. Mastercard counts account history only for buyers who had to register with an authentication method.
  • Proof of delivery to an address, email, or account with no link to the cardholder.
  • Arguing that the product was good. In a fraud dispute the question is who made the purchase, not its quality.

Mastercard's rules for 4837

  • Mastercard lists this code as 4837/37: 37 is the short form some processors and statements show. Source: Mastercard, Chargeback Guide – Merchant Edition (13 May 2025).
  • Mastercard doesn't allow 4837 for an online or phone order the issuer approved although the security code (CVC 2) didn't match, a payment verified by PIN or on the cardholder's device, a payment approved after the issuer had already charged back two or more fraud disputes on the same card, or once the issuer has filed more than 35 fraud chargebacks on it. Source: Mastercard, Chargeback Guide – Merchant Edition (13 May 2025), No Cardholder Authorization (4837); read 2026-10-27.
  • Mastercard's responses for an online order: the address check (AVS) answered X or Y and the goods went to that address; the payment was authenticated (Identity Check); or compelling evidence, at least one of: a receipt or work order the cardholder signed; the cardholder's written confirmation of registering for electronic delivery; messages between the seller and the cardholder showing they took part; a pickup at the seller's address. Where the cardholder had to register an account with a sign-in to buy: other undisputed purchases, the same registered device and IP address, signed proof of delivery, the email used for digital delivery, product registration, or use of what was bought (not for guest checkout). For a recurring payment: a description, the start date, and the original approval.
  • 3D Secure (Mastercard Identity Check): if the payment was authenticated, liability generally shifts to the issuer. Stripe adds the authentication result automatically.
  • Visa's Compelling Evidence 3.0 doesn't apply to Mastercard. The same linking evidence (earlier payments, IP address, device, account) still helps as ordinary evidence.
  • Other Mastercard codes in the same Stripe category: 4849 (questionable merchant activity), 4870 and 4871 (chip liability shift).

Common mistakes with Mastercard 4837

  • Using account history from a guest checkout. Mastercard accepts it only where buyers must register with a password or other authentication.
  • Sending an address-check result without showing the goods went to the address it confirmed.
  • For a recurring charge, leaving out the start date, the first approval, or the record of the cardholder accepting the recurring terms.
  • Sending delivery proof with no signature and nothing linking the recipient to the cardholder.

Should you fight it?

Fight it when the payment was authenticated with Identity Check, or the address check answered X or Y and the goods went to that address, or buyers must register and sign in and earlier undisputed purchases, the registered device and IP address, or use of what was bought tie the cardholder to it, or messages or a signed receipt or work order show they took part. Accept it when any of these is true:

  • No authentication and nothing at all linking this cardholder to any earlier activity.
  • Goods shipped to an address unrelated to the cardholder, with no other link.
  • Digital access granted but never used, and nothing else ties the cardholder to the purchase.
  • The seller suspects the order really was fraud. Accepting also avoids paying to fight a case that should be lost.

If you accept, don't refund as well: once it's a chargeback the money has already gone back to the customer, so a refund would pay them twice.

A dispute counts against your account whether you win or lose. To see the chance of winning at which fighting pays on your amount, try the fight-or-accept calculator; to compare what you keep with each tool, the fee calculator.

How to prevent the next one

  • Use Mastercard Identity Check (3D Secure) for risky or high-value online payments (Stripe Radar rules can require it).
  • Have buyers register an account with a password or one-time code before buying, so Mastercard's account-history evidence is open to you, and log the device and IP address.
  • For physical goods, ship to the address the address check confirmed, and require a signature on valuable orders.
  • For subscriptions, have buyers click to accept the recurring terms, and keep that record with the start date.
  • Use a statement descriptor customers will recognize.

Deadlines and fees

Deadlines and fees by platform
PlatformDeadlineFees
Stripe (US)Checked 2026-10-21Respond by the due date on the dispute in your Stripe Dashboard. It's usually 7 to 21 days, depending on the card network.$15 when the dispute arrives, which isn't returned. $15 more when you respond, returned only if you win in full.Stripe's Smart Disputes waives the $15 response fee and takes 30% of the disputed amount when you win.
SquareChecked 2026-10-21Seven days from Square's first email about the dispute.No fees for dispute management on chargebacks: Square covers the fee for disputes you challenge together.
Shopify Payments (US)Checked 2026-10-21Respond by the evidence due date in your Shopify admin. It's usually 7 to 21 days.$15 per chargeback, returned if you win.

A worked example (made up)

Your course site requires buyers to register an account with a password before buying. On February 2 a customer, signed in to the account they used for two earlier purchases, neither disputed, buys a $39 online course from the same registered device and IP address. They complete six lessons over the next two weeks. On March 1 the cardholder files a 4837 dispute saying they didn't authorize the payment.

The response would attach:

  1. Exhibit A: your checkout's rule that buyers register an account with a password before buying, this account's registration, and the two earlier purchases from it, neither disputed.
  2. Exhibit B: the device and IP address of the purchase, matching the ones registered to the account.
  3. Exhibit C: the access log: the course set up for that account, and six lessons completed between February 2 and February 16.

A sample response letter (made up)

For the example above. It's laid out the way Upheld drafts a response: one part for each thing the bank checks, strongest evidence first, each pointing to its exhibit. Yours should state only what your own records show.

We contest this dispute, Mastercard reason code 4837, for $39.00 charged on February 2 for an online course. The purchase was made signed in to the cardholder's registered account, from their registered device, and the course was used.

The cardholder bought from us before, signed in to their registered account. Buyers must register an account with a password before buying from us, and this purchase was made signed in to the account that made two earlier purchases, neither of which was disputed (Exhibit A). The device and IP address match the ones registered to the account (Exhibit B).

The course was used from the account after the purchase. The course was set up for that account and six lessons were completed between February 2 and February 16 (Exhibit C).

The registered account, the device and the use of the course all tie this purchase to the cardholder. We ask that the dispute be decided in our favor.

Questions people ask

What is a 4837 chargeback?

Mastercard's code for no cardholder authorization: the cardholder says they didn't make or allow the payment.

The security code matched. Is that enough?

No. A CVC 2 match shows the buyer had the card details, not that they were the cardholder. An address check answered X or Y counts only when the goods went to that confirmed address.

What ties a cardholder to a digital purchase?

The same account or email as earlier undisputed purchases, the same device, and dated use of what was bought after the payment, where buyers must register an account and sign in to buy (a password or other authentication); history from a guest checkout doesn't count.

Is reason code 37 the same as Mastercard 4837?

Yes. Mastercard's Chargeback Guide lists it as 4837/37: 37 is the short form some processors and statements show.

Draft yours free

Answer a few questions and get a draft, an evidence checklist and an honest read on whether to fight. Free account, no card.

Not sure what your notice says? Decode it first.

Start a free draft