A chargeback notification gives a merchant a fixed window, commonly between seven and thirty days depending on the scheme and the acquirer's own cut-off, to submit a response. Inside that window the firm either supplies evidence that the transaction was legitimate and authorised, or accepts the reversal. There is no third option and no extension for a busy week.
That response is representment: literally re-presenting the transaction to the issuer with supporting documents. It is not a conversation with the cardholder and it is not a court. An issuer analyst, or increasingly an automated rule, reads what was submitted and decides.
The sequence, and where the clock starts
A cardholder disputes a transaction with their issuing bank. The issuer assigns a reason code and pushes the chargeback through the scheme to the acquirer, which debits the merchant and passes on the notification. The merchant may represent with evidence. If the issuer accepts it, the funds return. If not, the issuer can raise a second chargeback or pre-arbitration, and beyond that the case goes to scheme arbitration, where the losing side pays a fee that usually exceeds the disputed amount.
Most trading firms should stop at representment. Arbitration on a mid-size deposit is economically irrational once the fee is counted, and the time cost of preparing it lands on the same small compliance team that has other work. The exception is a case that sets a pattern with a specific issuer, or a disputed amount large enough that the fee stops mattering.
The chargeback fee charged by the acquirer applies whether the firm wins or loses, and the dispute still counts toward the ratio the schemes monitor. Winning restores the money, not the count. That is the argument for preventing disputes rather than fighting them well.
Reason code decides everything
The evidence that wins depends entirely on why the dispute was raised. Broadly the codes fall into four families, and the response differs sharply between them.
| Reason family | What the issuer is asking | Evidence that answers it |
|---|---|---|
| Fraud, card not present | Did the real cardholder authorise this? | 3DS authentication result, AVS and CVV outcome, device and IP history, prior undisputed transactions from the same card |
| Service not provided | Did the client receive what they paid for? | Timestamped credit of funds to the trading account, platform login records, trade history after the deposit |
| Cancelled or not as described | What did the client agree to? | Accepted terms with version and timestamp, the refund policy shown at checkout, support correspondence |
| Processing error, duplicate | Was the charge correct? | Settlement records, the authorisation trail, evidence that any duplicate was already refunded |
A fraud dispute answered with trade history alone tends to lose, because it does not address identity. A service dispute answered with authentication data alone tends to lose for the mirror reason. Read the code before writing anything.
Compelling evidence for a trading deposit
The schemes use the term compelling evidence for material that establishes the cardholder participated in the transaction or received the benefit. For a broker or prop firm, the strongest bundle is boring and specific.
- The authentication record: 3D Secure outcome, liability shift status, AVS and CVV results.
- Identity: the KYC verification completed by the account holder, with the name matched to the card, and the date it was completed.
- Delivery: the exact timestamp the deposit was credited to the trading account, and the balance before and after.
- Use: logins from the same device and IP as the deposit, and the trading activity that followed it.
- Agreement: the terms and refund policy version the client accepted, with a timestamp.
- History: earlier transactions from the same card that were never disputed.
Notice what all of these have in common. Every item is captured at the time of the deposit or before it, by systems already running. None of it can be created after the notification arrives. A firm that logs device fingerprints and terms versions at checkout has a case ready in minutes, and a firm that does not has an argument.
Never fabricate, backfill or edit evidence to strengthen a response. Submitting false documents to a card scheme is fraud against the acquirer, and it puts the merchant account itself at risk, which is a far larger loss than the disputed deposit.
Writing the response
The rebuttal letter should be short and direct: what the customer bought, when, what identity and authentication checks passed, and what the customer then did with the funds. State the reason code and answer it in the first paragraph. Reference each attachment by name. Redact card numbers to the last four digits and remove personal data not needed for the case, which matters under data protection rules as well as scheme requirements.
Keep it to one page with clearly labelled exhibits. The analyst reading it has a queue and a few minutes. A long narrative about the client's behaviour, or an argument about how unfair the dispute is, reduces the chance anyone reaches the evidence.
When to accept the loss
Fight where the evidence is complete and the amount justifies the effort. Accept where authentication failed, where the deposit was never credited, where the client has a legitimate complaint, or where the file is thin. A firm that contests everything reflexively wastes hours and can end up with a lower success rate than one that picks its cases.
Track outcomes by reason code and by issuer, because the pattern tells you where the leak is. A run of friendly fraud disputes from one region usually points at a payment method or an onboarding gap rather than at bad luck, and fixing that upstream does more for the ratio than any improvement in representment. The same records feed the approval rate work, and the two problems are usually the same problem seen from different ends.
"Every dispute we won was won at deposit time. By the time the notification lands you are not building a case, you are printing one."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- Representment is a single fixed-window response with documents, not a negotiation, and the window is set by the scheme and the acquirer.
- The reason code determines which evidence wins. Fraud codes need authentication and identity, service codes need delivery and usage records.
- Every strong exhibit is captured at deposit time, so the case is built by the checkout systems long before a notification arrives.
- Winning restores the funds but not the dispute count or the acquirer fee, so prevention beats a high representment success rate.
Frequently Asked Questions
How long does a merchant have to respond to a chargeback?
The window is set by the card scheme and narrowed by the acquirer, commonly between seven and thirty days from notification. Missing it means the reversal stands regardless of the evidence.
What counts as compelling evidence for a trading deposit?
Authentication results, KYC identity matched to the cardholder, the timestamp the funds were credited, subsequent logins and trading activity, and the accepted terms with their version.
Is it worth escalating to arbitration?
Rarely. The scheme fee often exceeds a typical deposit, so arbitration only makes sense for large amounts or for a pattern with one issuer that needs to be settled.
About the Author
Roman Onta is an Executive Director at SINGUARD. He builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals side by side with his brother Alex Onta, and he helped on the design of eTrader, the division Alex built and leads. His ground is worldwide payment processing, AML compliance and the corporate structures brokers are built on, work the two of them carry together, shaped by executive roles in the UAE and international corporates. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.