Charged twice for the same payment? What to do after a duplicate attempt

If your banking app shows you were charged twice for the same payment on a Pakistan booking, the likeliest explanation is not two charges. It is one completed payment plus one pending authorisation left behind by an attempt that failed, timed out or was abandoned. A pending line is a hold on your available balance, not money that has left your account, and it usually drops off without anyone doing anything. Stripe, which processes online card payments for iDrive where card payment is offered, documents in its guide to card holds that an online card authorisation is typically valid for about seven days before the funds are released. Two lines that have both posted as completed transactions are different: that is a genuine duplicate, and the fastest fix is a refund from the merchant, not a dispute with your bank.

So the order of work is simple. Identify which kind of “twice” you are looking at, collect four or five specific records, contact iDrive with them, and keep a chargeback in reserve for the case where the merchant route genuinely fails. The rest of this guide explains each step and the reasoning behind it, including why going to your bank first can make a simple refund slower.

Charged twice for the same payment: which kind of “twice” is it?

Banking apps and statements do not all label transactions the same way. Stripe’s own documentation warns that card statements from some issuers do not always distinguish between an authorisation and a captured, settled payment, which is exactly why this question comes up so often. Before contacting anyone, open the transaction details on each line and note its status.

The last row surprises people. Stripe explains that refunds issued shortly after the original charge can appear as a reversal: the original charge drops off the statement and no separate credit is shown. If you were expecting a “refund” line and instead the charge simply vanished, the money has not been lost.

Pending authorisation versus settled charge

A card payment happens in two stages. First the card issuer authorises the amount, which reserves it against your available balance. Then the merchant captures or settles it, and money actually moves. For most everyday online payments the two happen almost together, so you never notice the gap. When something interrupts the flow, the gap becomes visible.

How a duplicate pending transaction is created

A duplicate pending transaction typically appears in one of these ways:

• A failed verification step. The card was authorised, but a 3-D Secure check in your banking app timed out or was declined, so the payment never completed. The authorisation can still sit on your account for a while.
• A second attempt after an apparent failure. The first attempt was actually approved, but the confirmation page was slow to load or the connection dropped, so you tried again. Now there may be two approvals.
• A refreshed or resubmitted checkout. Pressing Back, refreshing, or opening the payment page in a second tab can send the same request again.
• A card-check authorisation. Some flows place a small or full hold to confirm the card is valid before the real charge.

In the first and last cases nothing was settled, so there is nothing to refund. The hold has to expire or be cancelled. In the middle two, one or both attempts may have gone through, and you need the records to tell which.

The pre-authorisation hold release, in plain terms

A pre-authorisation hold release is the moment the reservation on your card is removed. If the merchant never captures an authorised amount, the authorisation eventually expires and the funds return to your available balance. Stripe’s documentation describes this directly: if an authorisation expires before capture, the funds are released and the payment is cancelled. A merchant can also cancel an uncaptured authorisation early. Either way, no refund is issued, because no payment was ever taken.

How long a failed attempt takes to drop off your card

There is no single answer, because the timing is set by the card network and your own bank rather than by the merchant. What can be said with confidence:

• Online card authorisations are short-lived. Stripe’s published validity windows for customer-initiated, card-not-present payments are seven days for Visa, Mastercard, American Express and Discover. Once that window passes without capture, the authorisation is no longer valid.
• Your bank decides when your balance updates. The authorisation expiring on the payment side and the pending line vanishing from your app are related but not identical events. Banks refresh pending items on their own schedule, and debit and credit cards can behave differently.
• Your bank’s app is the last to know. Even after the payment side has released a hold, the pending line can linger until your bank next refreshes it, so the date the line disappears is not proof of when the hold actually ended.

A practical rule for planning: treat a pending line from a failed attempt as something to watch for about a week, not something to fight on day one. If it is still there after roughly seven to ten days, or if it changes from pending to posted, that is the point to contact support with your records. If the held amount is causing a real problem in the meantime, for example it has pushed you close to an overdraft before a flight, ask your own bank whether it can see the authorisation and release it sooner. Some banks will, some will not; it is their decision.

Refund timing is a separate clock

If a duplicate did settle and iDrive refunds it, a different timeline applies. Refunds can only go back to the original payment method, according to Stripe’s refunds documentation, and a customer typically sees the credit roughly five to ten business days after the refund is initiated, depending on the bank. For card refunds Stripe can sometimes provide a reference number such as an Acquirer Reference Number (ARN), which your bank can use to trace the credit. It can take up to seven business days for that reference to become available, and there is none for a reversal, because the original charge was never processed.

If the card you paid with has since expired or been replaced, the refund is handled by your card issuer, which in most cases credits the replacement card. Worth knowing if you swapped cards after a trip.

Records that get a payment taken twice for booking fixed quickly

A support agent resolving a duplicate needs to match what your bank shows against what the payment system recorded. Vague descriptions (“I think I paid twice last week”) slow this down. Precise records let the check be done in one pass. Gather these before you write:

1. Your booking reference. iDrive references begin with IDR- and appear in the subject line of your booking email. If you made two bookings by accident, list both references.
2. Every payment email you received. That means the payment confirmation from iDrive and any separate card receipt from the payment processor. Two receipts for one reference is strong evidence of a true duplicate. One receipt and two statement lines points towards a hold.
3. The statement or app lines themselves. For each line: date and time, amount, currency, the merchant name exactly as shown, and whether it says pending or posted. A screenshot of the transaction detail screen is better than a retyped summary.
4. The last four digits of the card. Never the full number. Nobody legitimate handling a refund needs your full card number, CVC or a one-time passcode. Our guide on whether it is safe to send card details over WhatsApp covers why.
5. Roughly when each attempt happened. “First try at 21:40 UK time, error screen; second try at 21:46, success page” tells the support team exactly which attempts to look up.
6. Anything the checkout showed you. An error message, a declined notice, or a success page with an amount. Screenshots again beat memory.

You can check the payment status on your booking at any time from your iDrive customer account. If the booking shows as paid once and your bank shows two posted charges, that mismatch is the heart of your message.

A note on currency lines

If you paid from a card issued outside Pakistan, the amount on your statement may be in pounds, dirhams or dollars even if the fare was quoted in rupees. If your bank charges a foreign transaction fee, it may show that fee as its own line, which can look like a second, smaller charge. Before reporting a double charge on card, read the line descriptions carefully. Our explainer on using a UK debit card in Pakistan goes through how those fees tend to appear.

Contact iDrive before you contact your bank

It is tempting to go straight to your bank and press “dispute”. For a duplicate payment that is usually the slower route, for a reason buried in how card disputes work.

Stripe’s explanation of how card disputes work states that once a cardholder opens a dispute, the merchant cannot issue a refund outside the dispute process while the dispute is open. In other words, the moment a chargeback begins, the quick fix, a straightforward refund of the duplicate, is taken off the table. The case then runs on the card network’s timetable. Stripe describes the full dispute lifecycle, from initiation to final decision, as something that can take two to three months, and says it cannot reliably be sped up.

A merchant refund of a clear duplicate, by contrast, is a single action on a charge that has already been identified. The clock that matters then is only the bank’s credit time described above.

How to raise it

1. Use the iDrive contact page or reply to your booking email, so the message is tied to your reference.
2. Put the booking reference and “possible duplicate payment” in the subject line.
3. List each statement line with date, amount, currency and pending or posted status, and attach the screenshots.
4. Say plainly what you want: a refund of the second charge, or confirmation that the pending line is an uncaptured hold that will lapse.
5. Keep the reply. If you later need to escalate, a dated message showing you raised it with the merchant first carries weight.

How refunds are handled, including what happens with cancellations and partial refunds, is set out in the iDrive refund policy. A duplicate charge is not a cancellation; it is a payment that should not exist, and your message should say so.

What not to do while you wait

• Do not attempt the payment again “to be sure” until the status of the first attempts is clear.
• Do not open a dispute and a refund request at the same time. Stripe notes that where a customer disputes a charge while a refund is pending, the refund can fail, and the case has to be resolved through the dispute instead.
• Do not cancel your card to make a pending line go away. It is not how holds are released, and if a refund is needed later it then has to be routed by your card issuer to a replacement card, which adds a step.

When a chargeback is the right call

A chargeback exists for a reason, and there are situations where it is the correct tool. Consider it when:

• You have a posted duplicate, you have sent the records, and you have had no substantive response within a reasonable period.
• The merchant has refused to refund a charge that is clearly a duplicate.
• You do not recognise the charge at all, which is a fraud question for your bank, not a billing question.

Timing matters. According to Stripe, card networks typically allow cardholders to start a dispute within 120 days of the original payment, and for services bought in advance, such as a future trip, the window generally starts from the date of the service rather than the payment date. That is enough time to try the merchant route first without losing your rights, but not enough to leave it for a season.

If your card is issued in the UK

The Financial Ombudsman Service asks consumers to contact the financial business first and give it the chance to put things right. On timing, the Financial Ombudsman Service’s guidance on how to complain says a business has only 15 days to consider complaints about payment services (its examples are bank transfers and direct debits), against up to 8 weeks for most other complaints. If you are unhappy with the final response, you need to bring the complaint to the ombudsman within six months of the date on it. Note that this route is about your bank’s handling of a dispute; it sits after, not instead of, raising the duplicate with the merchant.

If your card or account is with a Pakistani bank

Raise the complaint with your bank first. If it is not resolved, the Banking Mohtasib Pakistan, the country’s banking ombudsman, takes complaints through an online complaint form and publishes its lodging procedure on the same site. Check its current eligibility rules and time limits there before filing, as they are set by the Mohtasib and can change.

Preventing a double charged on card next time

The duplicate-creating moments in the list above all happen just after pressing Pay. A few habits close them off.

1. One tab, one device. Open the secure checkout in a single browser tab and finish there. Do not start the same payment on your phone while the laptop is still thinking.
2. No refresh, no Back button. If the page seems stuck after you press Pay, leave it. A refresh or a Back-and-resubmit is exactly how a second request gets sent.
3. Keep your banking app to hand. Many cards now ask you to approve online payments in the bank’s app. Have it unlocked and ready, so the approval does not time out while you look for it. Overseas travellers on roaming data should do this on Wi-Fi if they can.
4. Wait for the confirmation, then check email. A success page with the amount, followed by a payment email, means it worked. Only if you see a clear error and no email arrives within a few minutes should you consider another attempt.
5. Before retrying, check the booking status. Reopen the payment link from your booking email or check your account. If the booking is already paid, the page says so rather than offering a second payment.
6. If you still have to retry, change nothing else. Same card, same amount, and note the time of each attempt. If both later post, your notes make the refund request straightforward.

Paying for someone else, such as parents landing in Islamabad while you are in Manchester, adds a layer: two people may each think the other has not paid. Agree in advance who pays and on which card. Our sister service Pakistan Taxi has a practical guide to booking and paying for someone else’s airport ride that covers how to split the booker and passenger details cleanly.

Why charging currency matters for duplicates

If the checkout offers a choice of currency, pick one and stick with it across attempts. Two attempts in different currencies produce two statement lines with different amounts, which are much harder for you, your bank and the support team to match up. If you are unsure which to choose, our comparison of paying in rupees or pounds explains the trade-off.

Questions people ask

Is a pending charge money I have lost?

No. A pending authorisation reserves part of your available balance but does not move money. If it is never captured, it expires and the funds are released. For online card payments Stripe lists a typical authorisation window of about seven days, though your bank controls when the line disappears from your app.

Both charges have posted. How do I get one back?

Contact iDrive with your booking reference, both statement lines and any payment emails, and ask for a refund of the duplicate. Refunds go back to the card you paid with and typically show as a credit within about five to ten business days, depending on your bank.

Should I raise a chargeback straight away?

Usually not. Once a dispute is open, the merchant cannot refund you outside the dispute process, and disputes commonly take two to three months to settle. Raise the duplicate with the merchant first and use a chargeback if that fails. Card networks typically allow around 120 days to start one.

The refunded charge vanished instead of showing a credit. Is that right?

Yes, that can be normal. A refund made shortly after the original charge may be processed as a reversal, so the original line simply drops off your statement and no separate credit appears.