Every card-present parking transaction is actually two events: an authorization that reserves funds on the cardholder’s account, and a capture that instructs the issuer to move those funds to the acquirer. In most retail settings the two happen within seconds of each other. Parking is unusual — entry-pay lots, pay-on-foot stations, and gated exit-pay systems all use different timing patterns, and the gap between authorization and capture can stretch from milliseconds to several days.
Understanding those patterns is not academic. Mismatched timing is a leading cause of reconciliation breaks, expired authorizations, and cardholder complaints about “duplicate” charges.
The Two-Message Model
The dual-message model is defined in the card network specifications and mirrored in the ISO 8583 financial transaction standard referenced by the Federal Reserve’s payments research. An authorization (sometimes called an auth-only or pre-auth) sends a 0100 message to the issuer asking whether funds are available. If approved, the issuer places a hold on the cardholder’s available balance and returns an approval code. No money moves yet.
The capture — technically a completion in EMV terminology — sends a second message (typically batched with other captures at end of day) telling the acquirer to settle the authorized amount. Only at capture does the merchant actually get paid.
Parking Timing Patterns
Pay-on-entry (flat-rate lots)
Entry-pay terminals at airport economy lots and event parking typically run a single-message transaction: the driver pays a known amount, the authorization and capture happen together, and the terminal prints a receipt. There is no open authorization to worry about because the amount is final at the point of sale.
Pay-on-foot (pre-exit pay stations)
Garages where patrons pay before returning to their vehicle use the same single-message pattern. The fee is calculated from the ticket, the card is charged, and the validated ticket grants exit. Reconciliation is straightforward — the pay station reports match the processor batch.
Gated exit-pay (pay-at-exit)
Exit-pay lanes add complexity because the driver is captive at a gate. Some operators authorize a small amount at entry (often with a credit-card-in, credit-card-out model) and then adjust the final capture based on dwell time. Others run a single transaction at exit. The pre-auth-and-capture pattern carries risk: authorization holds can expire before capture, forcing a re-authorization or a forced-post. Re-authorizations that fail at the gate create customer service incidents.
Monthly and subscription parking
Recurring monthly parking uses card-on-file (CoF) tokens — not authorizations against a physical card. The merchant stores a network token, submits a credential-on-file transaction each month, and captures when approved. NACHA’s ACH Network rules cover the equivalent pattern for bank-account debits.
Authorization Hold Expiration
Card network rules dictate how long an authorization may remain open. For most card-present transactions in travel and parking the hold window runs 7 to 30 days depending on the scheme and MCC. When the hold expires without capture, the funds return to the cardholder’s available balance — but the merchant can still submit a force-post capture, which the issuer may decline or chargeback. This is why operators running pre-auth-at-entry systems must capture promptly; an expired hold that then force-posts is a classic chargeback trigger, as described in dispute reason code documentation from Visa and Mastercard.
Reconciliation Implications
Every auth without a matching capture shows up in reconciliation as an open item. Every capture without a matching auth indicates a forced transaction or a system that bypasses the authorization step. Healthy parking operations aim for near-zero unmatched items at end of day. The tolerance threshold many operators use is under 0.5% of daily volume. Anything above that usually points to a timing bug in the pay station software, a batch-close failure, or a gateway that is not forwarding responses correctly.
FAQ
How long does a parking pre-authorization stay on my card?
For most U.S.-issued cards the hold window is 7 to 30 days depending on the card network and merchant category code. Travel-related MCCs typically have longer windows than retail.
Why do I sometimes see two charges from a parking garage on my statement?
You are almost always seeing one pending authorization and one settled capture. The pending item drops off when the capture posts. If both items remain for more than a few business days, contact the operator for a voided authorization.
Can a parking operator capture more than they authorized?
Only within tolerances defined by the card networks — typically 15% above the original authorization for travel MCCs, and only when the original authorization was an estimate (such as an incremental authorization for an extended stay). Captures materially above the authorization are usually declined or chargedback.
What is a force-post transaction?
A force-post is a capture submitted without a matching live authorization — for example, when an authorization has expired. It carries higher decline and chargeback risk than a standard two-message flow, and most acquirers monitor force-post rates as a fraud-indicator metric.