Force capture

What is force capture?

Force capture is the process of capturing funds from a cardholder's card after a purchase has been authorized, even when the

authorization

is not directly linked to a specific transaction or order. It's used when a merchant needs to charge a cardholder after authorization, or when the authorization was obtained through a different system than the one used for capture.

What separates it from a standard

payment capture

is the missing link between the two events. In the normal flow, the capture message carries the identifier the

issuer

returned at approval, so the issuer, the

acquirer

and the merchant all reference the same record. A force capture arrives without that identifier. The amount still settles, but the issuer has no approval on file matched to it, and every downstream consequence of force capture follows from that gap.

Key facts

Also known as: force post, forced sale, or forced payment, depending on the processor
Applies to: card transactions where an approval exists but was never captured through the standard authorization message
Common triggers: an authorization obtained by phone or another method outside the standard system, an order fulfilled long after it was authorized, or an order modified after approval so that the amount changed
Entry method: the amount, card details and approval code are submitted manually rather than referenced from a stored
authorized transaction
Processor permission: merchants often need explicit approval from their
payment processor
before using force capture, as some processors impose limits on the amount that can be captured and may restrict certain transaction types
Dispute exposure: Visa reason code 11.3 (No Authorization) and Mastercard 4808 (Authorization-Related Chargeback) both cover cases where no valid authorization is on record for the settled amount

How it works

An approval is obtained outside the standard flow. The merchant gets a voice authorization from the issuer, an approval through a separate terminal or system, or an authorization that has since expired or been lost by the system that would normally capture against it.
The approval code is recorded manually. Because no authorization record sits in the gateway waiting to be captured, the code exists only as something the merchant wrote down.
The capture is keyed in as a forced entry. The merchant or the processor enters the card details, the amount and the approval code into a force capture entry, rather than selecting an authorization to capture.
The item joins the clearing file. The transaction moves into the next
batch processing
cycle and on to
settlement
like any other capture, with no online authorization matched to it.
The issuer posts the charge. The cardholder's account is debited. Since the issuer holds no approval tied to that amount, the charge can reach the statement without the corresponding record the issuer would normally expect to find.

Why it matters

It recovers revenue that would otherwise go uncollected. When an approval exists but the capture path broke, because the authorization expired, the system that held it went down, or the order was edited after approval, force capture is the mechanism that still moves the money.
It covers sales that never touch the checkout. Phone orders, offline terminals and approvals granted by a call to the issuer produce no online authorization record for a gateway to capture against, so the funds move only through a forced entry.
It handles upward order changes. If items are added or quantities change after approval, force capture collects the difference where an
authorization adjustment
on the original approval isn't available.
It removes the defence a matched authorization provides. An approval linked to a capture is scheme-level evidence that the issuer said yes to that amount. Without the link, the issuer's own records show no approval for what settled, and the merchant defends the transaction with order paperwork instead of network data.

Common issues

Authorization-related chargebacks. A force capture is the exact fact pattern Visa 11.3 and Mastercard 4808 describe, so a
chargeback
filed under either code starts from a position the merchant cannot rebut with authorization data.
Fines and account restrictions. Misuse of force capture can result in fines or penalties from payment processors, and repeat use can lead to the capability being withdrawn from the
merchant account
.
Cardholder disputes. Lack of clarity around force capture can lead to
disputes
and complaints, especially when the charge posts long after the order date and the cardholder no longer recognizes it. Charges of this shape are a frequent source of
friendly fraud
claims.
Duplicate and stale captures. Force-capturing an amount already collected through the normal flow produces a double charge that then needs a
refund
or a
payment reversal
, and a manually keyed amount has no authorization to validate it against.
Pricing treatment. Acquirers can price a capture with no matching authorization differently from a standard capture, since the risk sits with a different party. The exact treatment is set by the acquirer agreement and scheme rules.