ChargebackKit
MastercardProcessing ErrorUpdated June 2026

Mastercard Reason Code 4846: Correct Transaction Currency Code Not Provided

The transaction was submitted to clearing in a currency code that does not match what the cardholder agreed to pay — common in cross-border and dynamic currency conversion (DCC) transactions.

Respond within ~45 days
Winnable with strong evidence

Your strongest argument

The currency was clearly disclosed at checkout and the cardholder accepted it — the currency code in the clearing record matches what was agreed.

Evidence that wins a Mastercard 4846 dispute

  • Checkout or order confirmation showing the currency and amount the cardholder accepted before the transaction was completed
  • Authorization record confirming the currency code submitted matches what the cardholder agreed to pay
  • For dynamic currency conversion: proof the cardholder affirmatively chose the converted currency with explicit disclosure at the point of sale

Ordered strongest first — lead your rebuttal with the items at the top.

Source: Mastercard Chargeback Guide. The Mastercard rulebook defines this code and its dispute framework; the issuer decides every dispute and sets the exact deadline shown in your processor dashboard.

Not sure you have enough to win?

Run a free 60-second readiness check for Mastercard 4846. Answer a few yes/no questions and get a 0–100 score, a green/amber/red evidence checklist, and your exact response deadline — no signup.

Check my evidence readiness — freeLook up another code

How processors label this dispute

ProcessorWhat you'll see
Stripereason: general (processing error)

Where to pull this evidence

Prove each charge was a separate, legitimate transaction. Here's exactly where the relevant records live in each processor dashboard — gather them free before you build your pack.

Stripe

Dashboard → Payments → Disputes (or the email alert from Stripe).

  • AVS & CVC check results: Open the original payment → Payment details → "Checks" (CVC, ZIP, address).
  • Customer email, IP, and device: Payment → Customer section and the "Risk insights" / Radar panel.
  • Receipt / order confirmation: Payment → "Send receipt" or your order-management system; export the PDF.
  • Refund history & reference IDs: Payment → Timeline shows any refunds with their re_… reference IDs.

Shopify Payments

Shopify admin → Orders → the flagged order → "Chargeback" banner, or Settings → Payments → Manage disputes.

  • Order & fulfillment details: Orders → the order → Fulfillment + Timeline (shows when items shipped).
  • Tracking number & carrier: Orders → Fulfillment → tracking; confirm "Delivered" status with the carrier.
  • Customer info & IP: Order → Customer section; Order → Additional details / fraud analysis for IP and AVS/CVV.
  • Fraud analysis (AVS/CVV/risk): Order → "Fraud analysis" panel shows AVS, CVV, and Shopify’s risk indicators.

Square

Square Dashboard → Disputes (or Balance → Disputes), or the email from Square.

  • Transaction & receipt: Transactions → the payment → receipt; "Resend receipt" for a copy.
  • Card-present / chip details: Transaction detail shows entry method (chip, tap, keyed) — chip reads support card-present disputes.
  • Customer details: Customer Directory → the customer; or the transaction’s customer section.
  • Itemization & amount: Transaction → itemized breakdown to rebut "incorrect amount" claims.

PayPal

PayPal → Resolution Center → the open case (Dispute, Claim, or Chargeback).

  • Transaction details & ID: Activity → the transaction → details; note the Transaction ID.
  • Proof of delivery / tracking: Resolution Center → "Respond" → add tracking number + carrier (PayPal validates delivery).
  • Proof of shipment / service: Resolution Center evidence upload: invoice, shipment receipt, or service-completion proof.
  • Buyer communication: Resolution Center message thread + your own email records with the buyer.

Build a submission-ready Mastercard 4846 response

ChargebackKit assembles your evidence into a formatted, labeled rebuttal pack with the exhibits and response letter card networks expect — pre-mapped to Duplicate Charge disputes.

Build your evidence pack — $19
Verified against the official Mastercard Chargeback Guide3-day money-back guarantee if your pack isn’t structured correctly for your dispute

Or run the free readiness check first →

Frequently asked questions

What is Mastercard reason code 4846?↓
Mastercard 4846 ("Correct Transaction Currency Code Not Provided") is a processing-error code filed when a transaction is submitted to clearing in a currency that does not match what the cardholder agreed to pay — most often in cross-border or dynamic currency conversion (DCC) situations.
How do I rebut a Mastercard 4846?↓
Submit checkout or order records showing the currency and amount were clearly disclosed and accepted by the cardholder before the transaction. For DCC disputes, proof that the cardholder affirmatively chose the converted currency — with explicit disclosure at the point of sale — is the key defense.
How is 4846 different from 4831 (Transaction Amount Differs)?↓
4831 ("Transaction Amount Differs") disputes a single charge where the settled amount was wrong; 4846 ("Correct Transaction Currency Code Not Provided") disputes the currency in which the transaction was submitted. Both are processing-error codes, but 4846 is specific to cross-border and DCC transactions where the wrong currency was applied.

Where to go next

Build the pack for Duplicate Charge disputes, or dig into the matching guide, template, and processor evidence requirements.

Build the pack for this dispute

Updated June 2026. This code’s meaning and evidence requirements are sourced from the Mastercard Chargeback Guide and may change as Mastercard revises its rules; always check your processor dashboard for the exact deadline and label on your dispute. The issuer decides every dispute — there is no guaranteed outcome.