Chargeback vs Void: Why an Authorization Reversal Is Different

A void releases an authorization before the payment is captured. A chargeback challenges a captured card payment through the bank dispute process. The difference is the transaction stage: a temporary authorization is not the same event as a completed charge.

For Shopify merchants, this distinction prevents a common reporting mistake. A customer may see a pending card entry and call it a charge, while the store’s payment history shows that no funds were captured. Review the actual transaction sequence before labeling the event a refund, void, or chargeback. Shopify explains authorization and capture in its payment authorization documentation.

Read the transaction as a sequence of events

Authorization asks whether the payment can proceed and can place a hold on available funds. Capture is the stage at which the merchant completes the charge against that authorization. A void cancels an uncaptured authorization; it is not a bank ruling about a disputed purchase.

The customer’s statement and the merchant’s transaction record can present this sequence differently. A pending entry may remain visible while the issuer updates its records. Its appearance does not, by itself, prove that the merchant received the amount twice or retained money after canceling an order.

Avoid estimating the issuer’s release time from a generic rule. The relevant card, issuer, and payment method can affect what the customer sees. Your immediate task is to establish the action shown in the processor’s transaction history and describe it accurately.

A useful timeline records authorization, any capture, any void, and any later dispute as distinct dated events. If capture is absent, do not invent it merely because the order was created.

Compare the right pair of records

Shopify’s capture guidance provides the native context for identifying captured and uncaptured payments. Use it to interpret the record, not to infer the state from an order title or a customer’s chosen word.

The distinction becomes especially important when an order has more than one payment attempt. A void associated with the first attempt does not necessarily describe the second. Match references, amounts, and timestamps before concluding that a later claim concerns an already canceled authorization.

A hypothetical order with two card entries

Consider a fictional footwear store. A customer tries to buy shoes for €95. The first authorization is voided after an interrupted purchase. A second attempt produces a valid order and captured payment for €95.

The customer sees two similar entries and reports a duplicate charge. The store should not answer “both were voided” because it found one void. It should identify each transaction: attempt one has an authorization followed by a void; attempt two has a captured payment tied to the completed purchase.

Now suppose a bank dispute arrives concerning the second transaction. The void on the first transaction does not close that dispute. It is context explaining the earlier attempt. The merchant still has to understand the specific allegation against the captured payment.

This example is hypothetical, but the diagnostic method is reusable: distinguish payment attempts, establish their stages, and only then compare them with the case reference.

Use a transaction-stage worksheet

For each relevant payment attempt, record the processor reference, authorized amount, captured amount, void status, currency, and transaction times. Add the associated order reference if one exists. Keep a final column for uncertainty: missing capture confirmation, unclear association, or conflicting display.

Read the worksheet from left to right as an event history. If a void is present before any capture, describe an authorization release. If a capture exists, identify any subsequent payment action separately. If a bank case exists, link it to the exact challenged transaction.

Do not use a screenshot of a canceled order as a substitute for this review. Canceling an operational order and changing the payment state are related decisions, but the record of one does not supply all the details of the other.

The Shopify chargeback overview explains the bank-led reversal process. Its terminology belongs to the disputed payment, not every abandoned authorization visible near the purchase.

Describe the result in precise language

A good internal conclusion sounds like: “Attempt one was authorized and voided; no capture found for that reference. Attempt two was captured and is the transaction identified in the dispute.” This language is specific enough for another employee to verify.

Avoid saying “the bank refunded the authorization” unless the records actually establish that event. Avoid promising that a pending entry will disappear on a particular day without issuer-specific confirmation.

Your goal is a correct explanation of the transaction stage. Once that is established, the team can choose the appropriate customer-service or dispute action without confusing a released hold with a challenged captured payment.

Explore Lower Chargeback to keep disputed orders visible alongside their operational references.

Explore Lower Chargeback

Related reading in this collection:

• What Is a Chargeback? A Shopify Merchant’s Starting Guide
• Why a Shopify Order Can Be Paid, Fulfilled, and Disputed at the Same Time
• Fraudulent vs Unrecognized Chargebacks: Why the Labels Differ