Chargebacks: Rights, Evidence and Reversal Checks
Disputing a card payment or answering a chargeback? Preserve authority and delivery evidence, check the bank’s route and reconcile any reversal.
- Published
- Updated
A chargeback is a card-payment reversal pursued through the cardholder’s bank under the applicable card scheme rules. A request starts a dispute process. It does not establish that the money has been recovered finally. For lawyers advising either party, the work is to identify the right route, assemble evidence of the disputed issue and reconcile every resulting movement.
What a Chargeback Does
The cardholder’s bank is the issuer. It raises the dispute through the card scheme to the merchant’s acquiring bank or payment provider. The merchant responds through its acquiring arrangements. The process can produce a full or partial reversal, a rejected request or a further challenge.
Consumer Affairs Victoria’s chargeback guidance explains that chargebacks concern debit or credit card transactions. A merchant refund is different: the merchant initiates a credit back to the customer. Record that refund even when a chargeback request is already under way.
A mistaken transfer to the wrong account follows the bank’s transfer-recovery process. An unauthorised electronic transaction requires a separate assessment of permission and liability, including the ePayments Code where it applies. ASIC’s Moneysmart guidance distinguishes those problems and directs prompt notification to the bank. Card-scheme rights and the unauthorised-transaction assessment can overlap, so identify both routes where the facts require them.
Contractual payment arrangements govern chargebacks. Statutory consumer rights provide a separate basis for a remedy. The Australian Competition and Consumer Commission’s remedy guidance explains repair, replacement and refund rights where consumer guarantees apply. Identify the underlying contractual or statutory claim separately from the request to reverse the card payment.
Identify the Dispute and the Applicable Rules
Start a transaction record that identifies your client’s role as cardholder or merchant. Record the original amount and currency, posting and purchase dates, merchant descriptor and payment reference. Add the contracting parties, what was purchased, the agreed performance and the alleged failure. Preserve the explanation of who authorised payment and how.
A payment-authority dispute asks a different question from a failure to deliver. A recurring-payment complaint also needs the subscription terms and cancellation history. An unfamiliar statement descriptor alone does not establish that a payment was unauthorised.
Obtain the actual card conditions or merchant agreement, dispute notice and applicable scheme rules. Record the reason code, its requirements, the event that starts its time limit and the response channel. Keep the provider’s response deadline beside the internal task owner. A scheme processing window is not necessarily the time the merchant has to answer its provider.
For example, CommBank’s Credit Card Conditions of Use require contact within 30 days of the statement date for the card-scheme refund process. The document treats unauthorised transactions separately. This is an issuer-specific example, not a universal chargeback deadline.
The Visa Core Rules and Visa Product and Service Rules distinguish non-receipt under condition 13.1 from credit not processed under condition 13.6. The former limits the dispute amount to the undelivered portion and generally requires an attempt to resolve the issue with the merchant. The latter requires evidence that a credit is due. Apply the condition that fits the allegation and the relevant regional rules. A missing refund and an undelivered purchase need different evidence.
Prepare the Request or Merchant Response
Prepare a submission that connects each allegation to a record. Keep original files unchanged and use redacted copies for circulation outside the secure matter file. Shared examples need a matter reference, not a full card number or unnecessary personal information.
- Preserve the settled transaction record. Save the statement page and receipt, retaining the payment reference and any distinction between transaction and posting dates. Confirm that the alleged duplicate is a second settled payment rather than a pending authorisation.
- Collect the agreement and communications. Retain the order, applicable terms, refund request and responses. For recurring charges, preserve the authority given and evidence of cancellation or renewal notices.
- Match performance evidence to the allegation. Collect delivery records, collection acknowledgements or records of services supplied. Explain what each document proves and what remains disputed.
- Contact the correct provider promptly. The cardholder uses the issuer’s dispute channel. The merchant responds to the acquiring provider’s notice. For non-delivery, preserve attempts to resolve the issue with the merchant. Report suspected unauthorised use to the bank immediately so account security can be addressed.
- Lodge the amount and requested outcome with the evidence. State any partial refund already received and answer the specified reason code. Retain the submitted version, acknowledgement and case reference, then diary further requests.
NAB’s merchant chargeback guide describes evidence such as delivery acknowledgements and refund references. It also directs merchants to the information requested in their notice. If an acknowledgement is missing, confirm receipt through the provider’s recognised channel before the response deadline.
Authentication records can support an assessment of who participated in payment. They do not, by themselves, establish delivery, satisfaction of the contract or continuing consent to recurring charges. Pair them with evidence of the particular issue raised.
Document-to-Allegation Record
The following fictional record shows how to preserve contrary evidence alongside the client’s account.
| Allegation | Supporting record | Contrary evidence | Missing record or next check |
|---|---|---|---|
| Equipment never arrived | Order and promised delivery terms | Courier scan says delivered | Recipient acknowledgement and delivery location |
| Cardholder did not authorise payment | Cardholder’s account of events | Authentication log records a successful challenge | Link between authentication event and disputed transaction |
| Subscription continued after cancellation | Cancellation email and later debit | Merchant says cancellation reached another address | Contractual cancellation channel and receipt record |
| Refund was promised but absent | Merchant’s written refund confirmation | Processor says credit was submitted | Refund reference matched to the receiving statement |
A record can weaken the allegation without resolving it. A delivery scan, for example, still needs to be connected to the goods and agreed recipient. Keep that distinction in the submission instead of treating every document as conclusive.
Reconcile Provisional Credits and Final Reversals
Track the original payment and each adjustment separately, with its source and status. A provisional credit changes the account balance while the dispute remains open. Retain the provider’s description of that credit and any conditions for a later debit.
Consider this fictional cardholder ledger for a $1,200 equipment purchase. The provider messages and statement movements below are invented to show the arithmetic. Positive amounts reduce the cardholder’s net outlay. Negative amounts increase it. The example assumes no fees or interest.
Fictional Reversal Ledger
| Event | Movement | Net outlay | Source and status |
|---|---|---|---|
| Original purchase settles | -$1,200 | $1,200 | Statement A, page 2; original payment |
| Issuer grants provisional credit | +$1,200 | $0 | Statement B, page 1; dispute remains open |
| Merchant challenges the request | $0 | $0 | Provider message 1; evidence received, no account movement |
| Merchant separately refunds $300 | +$300 | -$300 | Statement C, page 1; settled partial refund |
| Issuer removes provisional credit after challenge | -$1,200 | $900 | Statement C, page 2; provider message 2 explains debit |
| Provider confirms a final $900 reversal after further response | +$900 | $0 | Statement D, page 1; written disposition confirms remaining amount |
At the partial-refund stage, the cardholder temporarily has $300 more than the original payment. That is duplicate recovery across two routes, not an additional entitlement. Notify the provider and reconcile it before describing the dispute as resolved.
The final calculation is $1,200 paid less the $300 merchant refund and $900 final reversal, leaving $0 net outlay. The provisional credit and its removal cancel each other. If a separate $20 fee remained, the net outlay would be $20, with the fee’s basis and refund status recorded separately.
A merchant needs the same discipline for its settlement account. Match each chargeback debit, refund and later credit to the provider’s advice. Visa’s merchant dispute guide explains how to respond where a refund or reversal has already been issued. Its guidance is subject to the applicable scheme rules and merchant agreement.
For a larger statement bundle, FinTrace saves hours of manual statement review by bringing transactions into one searchable ledger. Its findings cite the source PDF filename and page, so lawyers and forensic accountants have the payment evidence at hand alongside the provider correspondence.
Verify the Outcome and Preserve the Remaining Claim
Close the payment reconciliation only when the provider’s written disposition agrees with the settled account movements. Record the amount accepted or rejected, whether a response or challenge remains open and any further step with its deadline. If a credit is still labelled provisional, retain that status even when the current balance looks correct.
If the written decision says a refund is complete but the statement lacks the credit, obtain its payment reference and investigate the posting. If a later debit appears, connect it to the relevant notice and revise the net position. Keep unresolved fees separate from the purchase amount.
For a complaint about the bank’s handling, use its internal dispute resolution process and retain the final response. The Australian Financial Complaints Authority’s chargeback factsheet explains that AFCA examines the bank’s efforts to pursue the chargeback. It does not review the card scheme’s rules or arbitration decision. Eligible consumers and small businesses can take an unresolved complaint about a financial firm to AFCA, subject to its jurisdiction and time limits.
Assess any remaining merchant or cardholder claim separately. A scheme result determines the payment dispute within that process. The legal team still needs to consider the contract, applicable consumer law and any settlement. Record what money has already been recovered when assessing a demand or court claim.
Retain one evidence bundle containing the original payment records, submission and responses, the written disposition and the reconciled ledger. The file must show the client’s net financial position and the action still required on the underlying dispute.
FinTrace
Statements in. Evidence out.
FinTrace turns your bank statements into one searchable Excel ledger and a written findings report, with every finding cited to its source page.
FinTrace
See how FinTrace works