Features
Part of Card payment guide: authorization, capture, clearing, settlement, and disputes
Resolving a duplicate card authorization and posted charge case
Duplicate card authorization case showing how to separate pending holds from posted charges, trace merchant records, preserve deadlines, and close the file.
What to take away
- Equal amounts do not prove that two purchases settled.
- Pending and posted entries must be compared as separate records.
- The merchant order, authorization attempts, captures, and processor batch answer different questions.
- Security reporting and billing-error reporting should follow the account type and facts.
- Close the case only after the account record and available balance both reconcile.
This fictional case shows how a customer and merchant can resolve an apparent duplicate without guessing. Names, dates, amounts, and references are invented. The method is educational and should be adapted to the issuer's instructions and the applicable agreement.
The alert
On Friday, Jordan buys a desk lamp from Harbor House for $86.35 using a debit card. The terminal pauses after the first tap. A cashier asks Jordan to tap again, and the second attempt produces an approved receipt.
Jordan's bank app soon shows two pending entries:
| Entry | Status | Amount | Displayed time |
|---|---|---|---|
| A | Pending | $86.35 | 6:41 p.m. |
| B | Pending | $86.35 | 6:42 p.m. |
The customer leaves with one lamp and one receipt. The available balance has fallen by $172.70, although the ledger balance has not yet recorded either purchase as final.
The first classification
Jordan does not add the entries to a fraud report yet. Both happened at the merchant where one purchase was made, and both remain pending. The working hypotheses are:
- The first terminal attempt produced an authorization that the point-of-sale screen did not recognize.
- The second attempt produced another authorization and the completed sale.
- The merchant submitted both as completed purchases.
- One entry belongs to an unrelated purchase with a similar descriptor.
The evidence needed to distinguish them is status plus references, not the repeated amount.
The customer record
Jordan saves screenshots and creates two rows:
Entry A
- Amount
- $86.35
- Status
- Pending
- Date
- Friday
- Descriptor
- HARBOR HOUSE 117
- Card
- Debit ending 4402
- App reference
- P-701
Entry B
- Amount
- $86.35
- Status
- Pending
- Date
- Friday
- Descriptor
- HARBOR HOUSE 117
- Card
- Debit ending 4402
- App reference
- P-724
Jordan also saves the receipt, which shows one sale, one approval code, one terminal, and one time.
The merchant record
The store manager searches the point-of-sale system and processor portal. The records show:
- one completed order for $86.35;
- authorization attempt X at 6:41 p.m.;
- authorization attempt Y at 6:42 p.m.;
- one captured sale tied to attempt Y;
- one batch item for $86.35;
- no second capture and no second order.
The first attempt received issuer approval, but the terminal timed out before the point-of-sale system displayed it. The cashier's retry produced a second approval. Only the second was captured.
This is a duplicate authorization scenario, not yet a duplicate posted-charge scenario.
Why the distinction matters
The Federal Reserve's debit-card issuer survey glossary distinguishes authorization from clearance and settlement, and defines a chargeback as a transaction returned by an issuer through the network to an acquirer. Those concepts explain why two approvals do not automatically mean two settled purchases.
The survey does not determine Jordan's rights or the duration of this hold. Jordan must ask the issuer how its account handles an approved but uncaptured debit transaction.
The issuer conversation
Jordan calls the verified number on the card and gives the two app references. The representative confirms:
- both entries are authorization holds;
- neither is currently a posted ledger debit;
- the bank has received one completed transaction for $86.35;
- the unused hold is expected to expire under the issuer's policy;
- a case number is available if the hold remains after the stated date.
Jordan records the representative's name or identifier, call time, case number, and exact wording. An expected expiry is not recorded as a guaranteed merchant refund.
The Monday state change
On Monday, the account shows:
| Entry | New status | Effect |
|---|---|---|
| A | No longer displayed | Unused hold released |
| B | Posted | One $86.35 ledger debit |
Available balance and ledger balance now reflect one purchase. Jordan saves the updated transaction history and closes the working issue.
No refund was required because the merchant never captured the first attempt. No chargeback was filed because there was no second posted purchase.
The alternate branch: both entries post
Suppose the Monday record instead shows two posted debits. The facts have changed. Jordan now has one receipt and two completed account entries.
The next actions would be:
- Save the statement or transaction history showing both posted items.
- Ask the merchant to check whether two captures entered its batch.
- Request a written merchant correction if it confirms a duplicate.
- Notify the issuer under its formal error procedure without allowing a merchant promise to consume the reporting period.
- Submit the receipt, two posted records, and merchant response.
- Track any temporary credit separately from the final decision.
The statement should be factual: Jordan authorized one purchase, received one item, holds one receipt, and sees two posted entries.
The security branch: the merchant is unfamiliar
If Jordan had not visited Harbor House, the case would not begin as a terminal retry. Jordan would contact the issuer promptly, secure the card, review other activity, and follow the unauthorized-transaction process.
The CFPB's unauthorized bank-account transaction guidance says to tell the bank or credit union right away and describes investigation and consumer-protection considerations for electronic fund transfers. The exact timing and liability depend on the facts, notice, and account.
Calling an unknown merchant first would not replace securing a potentially compromised debit card.
What the merchant should change
The store treats the incident as an operating defect even though only one sale posted.
It updates its procedure:
- Cashiers do not retry an uncertain terminal response immediately.
- Staff check the terminal and point-of-sale transaction log first.
- A supervisor searches for an approval reference before resubmission.
- Failed-display and approved-host states are escalated to the processor.
- Customers receive a plain explanation and a case contact.
- Duplicate attempts are reviewed during daily reconciliation.
The merchant also tests the network connection and terminal integration. Training alone will not repair a timeout defect.
What the customer should retain
Jordan's final file contains:
- the original receipt;
- screenshots of both pending entries;
- the merchant's one-order and one-capture confirmation;
- the issuer case number and hold-policy statement;
- the later record showing one posted debit;
- a short closure note.
The closure note says: "One completed purchase posted. The unused authorization stopped reducing available funds on Monday. No second debit or refund occurred."
That wording preserves the accounting sequence without claiming the merchant returned money.
Decision table for apparent duplicates
| Account display | Merchant record | Likely next step |
|---|---|---|
| Two pending | One capture | Ask issuer about unused hold release |
| One pending, one posted | One capture | Monitor hold under issuer policy |
| Two posted | Two captures, one order | Request merchant correction and preserve issuer notice rights |
| Two posted | One capture | Give both systems' references to issuer and merchant |
| Unknown merchant | Any status | Secure account and report promptly |
| Purchase plus equal credit | Refund shown | Confirm whether credit is temporary or final |
Lessons from the case
First, visible entries are not all in the same state. Second, merchant and issuer identifiers need translation. Third, a single order can generate more than one authorization attempt. Fourth, a temporary availability problem still deserves documentation, even when it resolves without a refund.
Most important, the remedy follows the confirmed state. The case moved from observation to evidence to classification, then to the narrowest correction needed.
Common questions
Did the merchant charge Jordan twice on Friday?
No final conclusion was possible on Friday. The app showed two pending authorization holds, not two posted debits.
Why did the cashier's first attempt matter if the terminal appeared to fail?
The issuer had approved it even though the point-of-sale system did not display a usable result. That left an unused authorization.
Should Jordan have demanded an immediate refund?
No refund record existed because the first approval was not captured. Jordan needed the issuer's hold-release information.
When would a formal error report become appropriate?
It would be appropriate if the facts fit the account's error process, such as two posted debits for one authorized purchase or an unauthorized transaction. Follow the issuer's instructions promptly.
