If a cardholder disputes a transaction on their statement, their card issuer will raise a ‘retrieval request’. See an example of one of our retrieval letters below.
Retrievals usually happen when the customer doesn’t recognise the payment, and is questioning whether they definitely made the payment, or if the payment was fraudulent.
If I respond to the retrieval request, can a chargeback still be raised?
A retrieval request can be closely followed by a chargeback if the Card Issuing Company doesn’t receive sufficient information about the transaction in question. That’s why it’s important you send as much information as possible in your reply to the retrieval request.
Unfortunately, some retrieval requests can still lead to a chargeback even if you’ve supplied all the correct information regarding the transaction. Once the Card Issuing Company has raised a chargeback case, you’re at risk of being debited for the disputed amount.
See the chargebacks section below for further information.
From your customer’s perspective, a chargeback is a reversal of a payment transaction, in an attempt to get their money back.
Chargebacks exist in order to give cardholders a way to claim back money for transactions that they or their bank feel isn’t justified.
By definition, chargebacks can cost your business money – so it’s important to know what they are, how to respond to them, and how to prevent them from happening.
A chargeback can happen for many different reasons:
These are just the most common examples – for a full list of chargeback ‘reasons’, see our page on dealing with chargebacks.
Chargebacks may also happen because the customer’s bank disputes a transaction, for example:
For more information, visit our page on preventing chargebacks.
Chargebacks happen in several stages:
If a customer or their bank simply wants to question what a transaction was, they can send a retrieval. The bank already has limited details of the payment like the date and amount, so you will need to provide as much additional information as possible.
At this stage, you won’t be required to pay back any money. You’re encouraged to respond to a request for information as quickly as possible.
Sometimes this step is skipped, and the claim immediately jumps to step 2
If you want to dispute the chargeback, you’ll have 14 calendar days from the date on the letter to defend it by providing evidence, depending on the reason the chargeback was raised.
An example of this would be if the customer has disputed a duplicate payment, you would need to provide details showing that they were two separate transactions.
Alternatively, if you see the chargeback as a legitimate claim, you can choose not to dispute the chargeback.
Even chargebacks that you successfully defend will ultimately cost you money or time, due to the resource involved in order to defend them.
If your chargeback defence is successful at this stage and you’ve already been debited, we’ll return the funds by the same means they were taken. How long it takes us to return the funds will depend on how you get billed.
Unfortunately, if you lose the chargeback appeal, you will be out of pocket. In this case, you’ll be debited for the chargeback amount, plus any fees for handling the chargeback.
This debit will happen as per your previous instructions – for example, the amount could be debited to your merchant service statement, or taken by Direct Debit from your account.
We’ll get in contact either by post or fax, depending on your communications preferences (see example letter below). This will outline the evidence you’ll need to gather in order to defend the chargeback or retrieval.
In some cases, we might tell you that we’re ‘pending’ or putting the chargeback debit on hold for 14 days while we wait for a response from you.
You should send your response and any documentation relating to the transaction within 14 days of the date on the letter or fax (Sometimes this step is skipped, and the claim immediately jumps to step 2).
For more information, visit our page: How to prevent chargebacks – and what to do if you’ve had one