Skip to main content

Visa 12.6 - Duplicate Processing/Paid by Other Means

TL;DR
  • The cardholder was charged twice for one sale, or paid by card and by another method
  • Dispute window is 120 days from the duplicate charge, and each extra charge can be disputed on its own
  • You win only if the two charges were genuinely separate sales. Separate receipts, different items, timestamps days apart
  • If it really is a duplicate, refund it before it becomes a chargeback. You keep the fee and your ratio

Used when a cardholder was charged multiple times for a single transaction, or when a charge appeared on both card and another payment method.

When This Code Applies​

Duplicate Processing​

  • Same transaction submitted twice
  • Multiple authorizations cleared separately
  • Batch submitted multiple times
  • Technical error caused duplicate
  • Charged to card AND paid cash
  • Charged to card AND different card
  • Charged to card AND via check
  • Charged to card AND bank transfer

Time Frames​

ScenarioDispute Window
Standard120 days from duplicate transaction date
Each duplicateCan dispute each extra charge

Conditions for Valid Dispute​

Cardholder Must Show​

  1. Same goods/services charged multiple times
  2. Only one transaction should have occurred
  3. Additional charge(s) were unauthorized
  4. Not separate valid transactions

Evidence of Duplicate​

  • Same amount
  • Same/similar date
  • Same merchant
  • Single purchase occasion

Representment Options​

1. Not a Duplicate​

When to use:

  • Two separate, valid transactions
  • Different items/services purchased
  • Different dates (days apart)
  • Cardholder made both purchases

Evidence required:

  • Separate receipts for each transaction
  • Different items on each receipt
  • Proof cardholder participated in both
  • Transaction timestamps showing separation

2. One Charge Already Refunded​

When to use:

  • Duplicate was identified and refunded
  • Credit already processed for extra charge

Evidence required:

  • Refund transaction details
  • Refund ARN
  • Date refund processed

3. Split Transaction​

When to use:

  • Large purchase split into multiple smaller charges
  • Disclosed to cardholder at time of purchase
  • Common for high-value items

Evidence required:

  • Receipt showing split
  • Cardholder acknowledgment
  • Total matches purchase amount

4. Different Services/Products​

When to use:

  • Multiple charges for different things
  • Cardholder confused but both valid

Evidence required:

  • Itemized receipts for each charge
  • Service dates (if different)
  • Order numbers (if different)

Required Documentation​

Evidence TypeStrength
Separate receipts + different itemsStrong
Refund already processedStrong
Split transaction documentationMedium-Strong
Same receipt, different totalsWeak

Representment Time Frames​

StageWindow
Response30 days
Pre-arbitration30 days
Arbitration45 days

Prevention Strategies​

Technical Prevention​

  1. Transaction IDs - Unique identifier per transaction
  2. Duplicate detection - Real-time at POS/gateway
  3. Batch review - Check before settlement
  4. Timeout handling - Proper retry logic
  5. Error recovery - Don't resubmit blindly

Process Prevention​

  1. Single swipe/entry - One entry per transaction
  2. Receipt verification - Customer sees charge
  3. Confirmation screen - Digital transactions
  4. Staff training - Avoid accidental duplicates
  5. End-of-day review - Catch before settlement

Monitoring​

  1. Duplicate alerts - Flag same card, same amount
  2. Same-day review - Multiple transactions review
  3. Batch analysis - Look for patterns
  4. Exception reporting - Investigate anomalies

Technical Causes of Duplicates​

CausePrevention
Timeout retryWait for response, don't auto-retry
Double-clickDisable button after first click
Batch resubmissionMark processed batches
Network hiccupImplement idempotency
Terminal errorStaff training on error handling

Win Rate Expectations​

ScenarioExpected Win Rate
Separate valid transactions65-80%
Refund already issued80-95%
Split transaction documented55-70%
Cannot prove separateUnder 25%

Common Mistakes​

  1. No duplicate detection - Duplicates not caught
  2. Same receipt - Can't show different transactions
  3. No unique IDs - Hard to prove separation
  4. Slow refunds - Customer files before credit
  5. Poor batch process - Resubmitting settled items

Distinguishing Duplicates from Legitimate​

Likely Duplicate​

  • Same exact amount
  • Same day (within hours)
  • Single purchase scenario
  • Customer bought once

Likely Separate Transactions​

  • Different amounts
  • Different days
  • Different items
  • Customer returned/bought again
  • 12.5 - Incorrect Amount
  • 13.1 - Not Received

Next Steps​

Got this chargeback?

  1. Compare transaction records → Are these truly different transactions?
  2. Check if refund already issued → Already credited one?
  3. Pull separate receipts/orders → Show different purchases
  4. Respond within 30 days → Representment Workflow

Prevent future 12.6 chargebacks:

  1. Implement duplicate detection at POS/gateway
  2. Add unique transaction IDs to all charges
  3. Review batches before settlement
  4. Check operations checklist

See Also​

Last updated on