Preauthorisations and deferred captures: how to hold an amount and charge it later without surprises

In standard e-commerce, charging a customer is usually an instantaneous event: the cardholder enters their payment details, completes strong customer authentication, and the gateway processes the transaction in a single step that both authorises and settles the payment. However, many business models do not know the exact final amount at the moment of checkout, or services are fulfilled days after the order is placed. This is where preauthorisations and deferred captures come into play.

This mechanism verifies fund availability and places a temporary hold on a specific amount on the customer's card, postponing the actual capture until the goods are dispatched, the service is rendered, or the exact total consumption is computed.

The difference between authorising and capturing

To understand this workflow within the wider online payments ecosystem, it is helpful to break down the standard lifecycle of a card transaction into two distinct stages:

• Authorisation: The card-issuing bank confirms that the card is active, free of security blocks, and backed by sufficient credit or balance. At this stage, the bank sets aside the funds by holding that amount against the customer's credit line or account. The customer cannot spend those funds elsewhere. However, no money has actually moved from the customer's account to the merchant's account.
• Capture or settlement: This is the instruction by which the merchant directs the banking network to settle the transaction permanently. Once captured, the held funds are formally transferred through card schemes into the merchant's acquiring account.

When an online business operates with deferred capture (frequently termed *auth and capture* or manual capture), the system initially initiates only the authorisation call. The capture instruction is triggered later, either through an automated API call from the payment gateway or automatically when a warehouse marks an order as shipped.

Standard business use cases for preauthorisation

A two-phase capture workflow is not required for every business, but it solves essential operational issues across several industries:

• Merchants with frequent stockouts or slow fulfilment: If a business settles funds immediately and discovers hours later that an item is unavailable, it must process a refund. Refunds generate processing fees and take several business days to appear on the customer's bank statement. Using a preauthorisation instead allows the merchant to void the hold (or release unneeded funds) without triggering accounting complexity.
• Reservations, security deposits, and temporary holds: Hotels, car rental agencies, and ride-hailing apps routinely place a hold as a security deposit or ride estimate. Upon vehicle return or checkout, they capture the final amount reflecting exact mileage or ancillary charges, immediately releasing the remaining balance.
• Variable weight baskets: Online grocers and food retailers weigh fresh produce before packing. They typically authorise 110% or 120% of the estimated basket value and capture the exact amount once weighing is completed in the warehouse.

Expiry windows and operational risks

Holding customer funds is not an indefinite state. Card schemes (such as Visa and Mastercard) and issuing banks enforce strict time limits on how long an authorisation can remain open. As a general rule, standard e-commerce authorisations expire within 5 to 7 calendar days, though specialised sectors (such as vehicle rental or lodging) can maintain holds for up to 30 days under specific scheme rules.

If the merchant fails to capture the preauthorisation before it expires, two problems emerge:

• The hold on the customer's account lapses, releasing the funds back to the cardholder.
• If the merchant attempts a late capture on an expired authorisation, the transaction may be declined by the issuer or processed as an out-of-bounds capture. This significantly increases interchange and acquiring processing fees while exposing the business to chargebacks for unauthorised debit.

Consequently, if order preparation and delivery regularly take longer than one week, a traditional preauthorisation is technically unsuitable. A stored-credential model using card tokens for subsequent customer-consented charges is far more reliable.

European regulations and strong customer authentication

Under the European PSD2 framework and strong customer authentication (SCA) rules, preauthorisations require careful technical handling. If the final captured amount exceeds the amount initially authenticated via 3D Secure, the card issuer may decline the incremental capture or demand a fresh authentication challenge. For predictable variations, current card scheme specifications allow merchants to submit an estimated total during initial verification to absorb minor discrepancies without introducing consumer friction.

Best practices for implementing deferred capture

To ensure deferred capture provides operational flexibility without harming buyer trust, merchants should follow several baseline principles:

• Transparency at checkout: Buyers should clearly understand whether they are being charged immediately or if a temporary hold is being placed. Mobile banking apps frequently display holds as pending debits, which can prompt customer support inquiries if not disclosed upfront.
• Immediate release of uncaptured amounts: If an order is cancelled or the final amount is lower than the initial hold, do not leave the surplus to expire naturally. The payment gateway should dispatch an explicit void or partial capture instruction immediately.
• Event-driven automation: Captures should be wired directly into logistical milestones (such as parcel packaging or courier handover) to prevent authorisations from lapsing due to human administrative oversights.

In conclusion, preauthorisations and deferred captures are effective tools for synchronising logistical operations with payment flows in digital commerce. When managed strictly within card scheme timelines and communicated transparently to buyers, they eliminate unnecessary refund overhead and ensure that businesses only collect funds for products they are actually ready to deliver.