Visa · Processing Errors
Reason code 12.5: Incorrect Amount
The cardholder was billed an amount different from what they agreed to, or the transaction amount was altered after the sale was completed. Typical patterns include inflated totals, decimal errors, and post-sale additions the customer never approved. The dispute may target just the difference or, as filed by some issuers, the full transaction.
Issuer filing window
120 days from the transaction processing date
Merchant response window
typically 20-30 days to respond, depending on the acquirer
Why 12.5 chargebacks happen
- A decimal-place error at keying turned $49.90 into $499.00.
- Post-sale charges like handling fees, gratuities, or order add-ons were folded into the capture without the customer's agreement.
- The checkout displayed a discounted price but the gateway charged the pre-discount amount because a coupon failed silently.
- A currency rounding or conversion step changed the total between display and settlement.
- A receipt was altered after signature, which cardholders can prove with their copy.
How to fight a 12.5 chargeback
- Submit the order confirmation, invoice, or signed receipt showing the cardholder agreed to the exact amount that settled.
- Document the composition of the total, itemizing product, shipping, and tax so the issuer can reconcile the figure the customer remembers against the figure billed.
- Where terms authorized variable or additional amounts, such as disclosed shipping calculated at fulfillment, provide the accepted terms and the calculation.
- If the amount truly was wrong, refund the difference promptly and present the correction, which usually limits or resolves the dispute.
- Compare against the authorization amount too, since a capture exceeding authorization can convert the problem into an 11.3.
How to prevent 12.5 chargebacks
- Charge the exact total displayed at final checkout confirmation, computed once and passed immutably to the gateway.
- Never modify a transaction amount after customer approval; process differences as separate authorized transactions or refunds.
- Add automated alerts for captures that deviate from their order totals.
- Test coupon, bundle, and shipping-calculation paths on every funnel change, because silent pricing failures create systematic amount mismatches.
- Show the full itemized total, including all fees, before the payment button rather than revealing charges afterward.
Frequently asked questions
- The customer agreed to the price, so why a 12.5 chargeback?
- Usually because the settled amount differs from what they remember agreeing to, often due to post-checkout additions like shipping, fees, or an upsell folded into the same charge. Your defense is documentation that the exact settled figure was displayed and accepted. If any component was added after approval, expect to refund the difference.
- Is a 12.5 dispute for the full charge or just the difference?
- Conceptually the dispute corrects the discrepancy, and a proper resolution can be limited to the difference between the agreed and billed amounts. Issuers nonetheless sometimes file for the entire transaction. Present evidence supporting the valid portion of the charge and the correction of any genuine overage, and push your acquirer to limit the adjustment accordingly.
- Do post-purchase upsells cause incorrect amount chargebacks?
- They do when the upsell modifies the original transaction amount instead of creating a new one. The cardholder confirmed $39 and their statement shows $107, which is exactly the fact pattern 12.5 exists for. Run each upsell as a separate authorization with its own confirmation screen and receipt, which is also cleaner for authorization compliance.
Related Visa codes