Dual-Message Transaction

What Is a Dual-Message Transaction?

A dual-message transaction is a card payment that travels through the payment network in two separate electronic messages. The first message carries only the information needed for an authorization decision: card number, expiration date, transaction amount, and merchant details. The issuing bank evaluates the request, checks the cardholder's available balance, applies fraud rules, and responds with an approval or decline. If approved, the issuer places a hold on the authorized amount, reducing the cardholder's available credit or funds without actually moving money.

The second message, known as the capture or clearing message, arrives later with additional settlement details. This message triggers the actual transfer of funds from the issuer to the acquirer (the merchant's bank). The gap between authorization and capture can range from seconds to days, depending on the merchant's fulfillment process.

Most credit card transactions and signature-based debit transactions follow the dual-message model. In Europe, nearly all card payments are processed as dual-message transactions. The model is sometimes called "auth and capture" or "two-step processing," and Visa refers to the initial step as an "estimated authorization" while Mastercard uses the term "pre-authorization."

How It Works

A dual-message transaction flows through the four-party model (cardholder, merchant, acquirer, issuer) with the card network routing messages between banks.

Step 1: Authorization

The authorization phase handles approval and fund reservation:

1. The cardholder initiates a purchase (online checkout, tap at a terminal, or card-on-file charge)
2. The merchant's payment processor sends an authorization request to the card network
3. The card network routes the request to the issuing bank
4. The issuer checks available funds, applies fraud screening, and verifies the card status
5. If approved, the issuer places a hold on the authorized amount and returns an authorization code
6. The merchant receives the approval and can proceed with the order

At this point, no money has moved. The cardholder sees a "pending" charge on their statement, and their available balance decreases by the held amount. The merchant has a promise that the funds will be available when captured.

Step 2: Capture and Clearing

The capture phase initiates the actual fund transfer:

1. The merchant submits a capture request, typically in a batch at the end of the business day
2. The acquirer forwards the capture to the card network for clearing
3. The card network calculates interchange fees and routes the clearing message to the issuer
4. The issuer converts the hold into a posted transaction on the cardholder's account
5. The acquirer credits the merchant's account, minus applicable fees

The capture amount can differ from the authorized amount within limits set by card scheme rules. A restaurant may authorize $50 at checkout and capture $57 after the cardholder adds a tip. An e-commerce merchant shipping a partial order may capture less than the original authorization.

Authorization Hold Windows

Card networks set rules for how long an authorization hold remains valid before it expires. Standard card-not-present authorizations typically hold for 7 to 30 days depending on the network and merchant category. Some specific windows include:

• Standard Visa and JCB transactions: approximately 6 days
• Standard Mastercard transactions: up to 29 days
• Lodging and car rental (Visa): up to 29 days

If the merchant fails to capture within the hold window, the authorization expires and the hold is released back to the cardholder. The merchant would need to submit a new authorization to charge the card.

Message Format

Both messages travel over card network infrastructure using standardized formats. The authorization message typically uses ISO 8583 message type 0100 (authorization request) and 0110 (authorization response). The capture and clearing message uses message type 0220 (financial presentment) or 0230 (response):

// Dual-message flow (simplified)

// Message 1: Authorization Request (ISO 8583 MTI 0100)
{
  message_type: "0100",
  pan: "4111********1111",
  amount: 9999,           // $99.99 in minor units
  currency: "840",        // USD
  merchant_id: "MERCHANT_001",
  terminal_id: "TERM_042",
  pos_entry_mode: "051"   // e-commerce
}

// Issuer responds with approval
// Authorization code: "A12345"
// Hold placed: $99.99

// Message 2: Capture / Clearing (ISO 8583 MTI 0220)
{
  message_type: "0220",
  pan: "4111********1111",
  amount: 8999,           // $89.99 (partial shipment)
  auth_code: "A12345",
  settlement_date: "1025"
}

// Hold released, $89.99 posted to account

Dual-Message vs. Single-Message

The alternative to dual-message processing is a single-message transaction, where authorization, clearing, and settlement data travel in one combined message. The payment is approved and the fund transfer is initiated simultaneously.

Single-message transactions are generally preferred for card-present scenarios where the cardholder is physically present and the good or service is delivered immediately. PIN entry provides strong authentication, making the combined message safe. Dual-message dominates in scenarios where there is a delay between purchase and fulfillment.

Use Cases

E-Commerce and Online Retail

Online merchants are the primary users of dual-message transactions. A customer places an order and the merchant authorizes the card immediately to confirm funds are available. The capture happens only when the order ships, which could be hours or days later. If an item is out of stock, the merchant can void the authorization without ever charging the customer.

Hotels and Car Rentals

Hotels authorize a card at check-in for the estimated stay cost, then capture the final amount at checkout after adding room service charges, minibar fees, or extending the stay. Car rental companies follow a similar pattern, authorizing an estimated rental fee upfront and capturing the actual cost (plus fuel or damage charges) upon return.

Restaurants and Tipping

When a cardholder pays at a restaurant, the terminal authorizes the bill total. The cardholder then writes a tip on the receipt. The restaurant captures the original amount plus the tip in a single capture message, which is permitted because card networks allow capture amounts to exceed authorization amounts by a percentage (typically 15 to 25 percent for restaurants).

Subscription and Recurring Billing

Recurring billing systems often use dual-message flows to authorize a stored card before processing the charge. If the authorization fails (expired card, insufficient funds), the system can retry or notify the customer before a capture attempt, reducing failed payments and improving authorization rates.

Why It Matters for Crypto and Stablecoins

The dual-message model exists because traditional card payments are pull-based: the merchant requests funds from the cardholder's bank. This requires a verification step (authorization) before the money actually moves (capture). The two-step flow introduces delay, complexity, and cost, but provides merchants and cardholders with useful flexibility.

Cryptocurrency and stablecoin payments work fundamentally differently. They are push-based: the payer initiates and completes the transfer in a single atomic operation. When a user sends Bitcoin or a stablecoin like USDB, authorization and settlement happen together. Once the transaction is confirmed on-chain or on a Layer 2 like Spark, it is final. There is no hold, no pending state, and no capture step.

This single-message finality eliminates several pain points of the dual-message model:

• No authorization holds tying up customer funds for days
• No expired authorizations requiring re-authorization
• No chargeback risk from the gap between auth and capture
• No batch processing delays: merchants receive funds at confirmation, not days later

However, the dual-message model's flexibility has advantages that crypto payments currently lack. The ability to place a hold without charging, adjust amounts after purchase, and void before settlement are features that merchants rely on heavily. Solutions like hodl invoices on Lightning and programmable escrow on smart contract platforms attempt to replicate some of this conditionality in a crypto-native way. For a deeper comparison of settlement models, see the research on payment finality across systems.

Risks and Considerations

Authorization Decay

An authorization is a snapshot of the cardholder's account at the moment of approval. Between authorization and capture, the cardholder's financial situation can change. They may spend down their available balance, their card may be reported stolen, or the issuer may lower their credit limit. Merchants who delay capture face a higher risk of declined captures, a problem known as authorization decay.

Over-Authorization

Merchants sometimes authorize more than the expected purchase amount to cover potential add-ons (tips, fuel overages, incidentals). This reduces the cardholder's available balance by more than necessary, which can cause legitimate purchases on other cards or accounts to be declined. Card networks have rules limiting over-authorization, and excessive holds can result in scheme fines.

Fraud Exposure Window

The gap between authorization and capture creates a window where fraudulent transactions might go undetected. A stolen card could be authorized successfully if the theft has not yet been reported. By the time the merchant captures, the issuer may have flagged the card, leading to a chargeback against the merchant. Strong authentication methods like 3D Secure help mitigate this exposure.

Processing Costs

Dual-message transactions can carry higher processing fees than single-message PIN debit transactions because they involve two separate network messages and a longer settlement cycle. The interchange fee structure also tends to be higher for card-not-present dual-message transactions due to elevated fraud risk. Merchants processing high volumes may prefer routing eligible transactions through single-message PIN debit networks to reduce costs.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.