How Dual Message System (DMS) Works
The Dual Message System is the dominant payment processing architecture for card-not-present commerce. Understanding it at a mechanical level is essential for any merchant, payment engineer, or orchestration architect who wants to control cash flow, minimize fraud exposure, and avoid costly interchange downgrades. The process unfolds across two clearly defined network messages, each with its own timing requirements and compliance rules.
Cardholder Initiates Payment
The customer enters card details at checkout. The merchant's payment gateway packages a structured authorization request — including the card PAN, expiry, CVV, billing address, and requested amount — and routes it through the card network to the issuing bank.
Issuing Bank Places Authorization Hold
The issuing bank validates the card credentials, checks the cardholder's available credit or funds, and runs fraud scoring. If approved, it places a hold for the requested amount and returns an authorization approval code to the merchant. No funds have moved yet — only a reservation exists.
Merchant Fulfills the Order
Between authorization and capture, the merchant ships goods, confirms inventory, performs fraud review, or completes service delivery. This window is the defining feature of DMS: the merchant retains the ability to cancel (void) or adjust before any money changes hands.
Merchant Submits Capture Request
Once fulfillment is confirmed, the merchant submits a capture message — the second of the two DMS messages — specifying the final amount. This amount can be equal to, less than, or (within network limits) slightly greater than the original authorization.
Clearing and Settlement
The capture message enters the clearing batch, typically processed once or twice daily. The card network routes the clearing file to the issuing bank, which releases the hold and initiates the actual transfer of funds. Settlement typically completes within one to two business days, depositing net proceeds into the merchant's acquiring bank account.
Authorization Window Compliance
Visa's standard retail authorization hold window is 7 days. Mastercard follows similar rules. Lodging and vehicle rental merchant category codes (MCCs) are granted up to 30 days. Capturing outside these windows triggers a downgrade from qualified to non-qualified interchange tiers — significantly increasing your processing cost per transaction.
Why Dual Message System (DMS) Matters
DMS is not just a technical implementation detail — it has direct, measurable impact on merchant economics, fraud rates, and customer experience. The architecture has become the default for ecommerce precisely because it aligns fund movement with value delivery rather than with purchase intent.
According to Visa's annual data, card-not-present transactions represent over 50% of total Visa payment volume globally, and the overwhelming majority of these transactions flow through a DMS architecture. The ability to cancel before capture means that merchants using DMS with post-authorization fraud screening can intercept fraudulent orders before they become chargebacks — one industry study found that pre-capture order review programs reduce chargeback rates by up to 40% compared to immediate-capture workflows.
Capture flexibility also has a direct impact on revenue recovery. For subscription businesses and platforms where the final charge depends on usage — think SaaS metered billing, marketplace service fees, or hospitality incidentals — DMS enables capturing the precise correct amount rather than issuing post-settlement refunds. Refunds carry their own interchange costs and create negative cash-flow timing gaps, making pre-capture adjustment significantly cheaper operationally.
Interchange Optimization
Many card networks offer preferred interchange rates specifically for transactions that follow DMS best practices: capture within 24 hours of authorization, amount match within tolerance, and matching transaction identifiers between auth and capture messages. Non-compliance can add 50–100+ basis points to your effective rate.
Dual Message System (DMS) vs. Single Message System (SMS)
DMS and the single-message-system serve different use cases, and mixing them up — or choosing the wrong one for a given channel — creates real compliance and cost problems. The table below captures the key operational dimensions.
| Dimension | Dual Message System (DMS) | Single Message System (SMS) |
|---|---|---|
| Number of network messages | 2 (authorization + capture) | 1 (combined auth + capture) |
| Settlement timing | Deferred — merchant triggers capture | Immediate — settles in real time |
| Amount adjustment | Supported (within network tolerances) | Not supported — amount is final |
| Typical use case | Ecommerce, lodging, car rental, B2B | PIN debit, fuel pumps, low-value in-person |
| Void window | Available between auth and capture | Not available after message sent |
| Fraud cancellation window | Yes — cancel before capture | No — funds move immediately |
| Chargeback recovery | Easier — cancel before settlement | Requires post-settlement refund |
| Interchange complexity | Higher — requires matching auth/capture | Lower — single clearing record |
For card-present point-of-sale transactions where the final amount is known immediately — such as grocery or fuel purchases using PIN debit — SMS is often preferred for its simplicity and speed. DMS becomes essential the moment there is any gap between price confirmation and fulfillment.
Types of Dual Message System (DMS)
Not all DMS implementations are identical. The base architecture branches into several operational variants that serve specific industry needs.
Standard Authorization and Capture is the most common form. The merchant authorizes at checkout and submits a single capture for the full amount at shipment. This is the default mode for most ecommerce platforms.
Incremental Authorization extends the DMS model for industries where the final amount grows after the initial hold. Hotels authorize an estimated total at check-in and submit incremental authorizations as the guest adds room service, spa charges, or parking fees. Each incremental auth adds to the total hold without replacing the original.
Pre-authorization with Partial Capture allows merchants to authorize a larger amount as a deposit or guarantee, then capture only the amount actually used. Car rental companies routinely authorize $500 as a damage hold and capture only the base rental fee plus fuel when the vehicle is returned undamaged.
Split Shipment Capture enables merchants to capture multiple smaller amounts against a single authorization when an order ships in multiple packages. Each capture reduces the remaining authorized amount until the full order is fulfilled or the hold expires.
Best Practices
For Merchants
Capture as close to fulfillment as operationally possible — within 24 hours of shipment or service delivery is the industry standard. Delayed captures expose you to authorization expiry and the corresponding interchange downgrade. Build an explicit void workflow so that cancelled orders immediately release the authorization hold rather than leaving cardholders with frozen funds for days.
Monitor your capture-to-authorization ratio by MCC and processor. A high ratio of captures significantly below authorization amounts may signal over-authorization practices that inflate cardholder friction. Conversely, frequent captures at or above tolerance thresholds signals a need to recalibrate how you set initial authorization amounts.
Implement post-authorization fraud review during the DMS window rather than relying solely on pre-authorization screening. Velocity checks, device fingerprinting correlation, and manual review queues placed between auth and capture allow your fraud team to cancel high-risk orders before they settle — eliminating the chargeback entirely.
For Developers
Treat the authorization ID (transaction ID or retrieval reference number) as a first-class entity in your data model. Every capture, void, and incremental authorization must reference the original auth ID to maintain a complete audit trail and ensure the card network routes messages correctly.
Implement idempotency on capture requests at the API level. Network timeouts during capture submission can cause duplicate capture attempts, resulting in double-charges. Use idempotency keys and check for existing capture state before retrying. Design your capture job to handle partial failures gracefully — a split-shipment workflow must track which capture succeeded and which needs retry independently.
Expose authorization expiry timestamps in your internal tooling dashboards. Operations teams need visibility into aging authorizations so they can prioritize capture or void actions before the window closes. Automated alerts at 80% of the expiry window prevent accidental expirations during peak fulfillment delays.
Common Mistakes
Capturing after the authorization window expires is the most common and costly DMS error. Expired authorizations can still process on some networks but at non-qualified interchange rates. Others will simply decline the capture, requiring you to reauthorize — which may fail if the cardholder's available balance has changed.
Capturing significantly more than the authorized amount without requesting an incremental authorization violates card network rules. Even small overages outside the permitted tolerance (typically 15–20% depending on network and MCC) can trigger issuer declines or merchant category violations.
Never voiding uncaptured authorizations creates a poor cardholder experience and inflates your outstanding hold liability. Cardholders who see holds for cancelled orders will call their bank, generating issuer inquiries. Systematically voiding cancelled orders immediately is both a CX best practice and a compliance expectation.
Mismatched transaction identifiers between authorization and capture cause clearing failures where the network cannot match the capture to the original auth record. This forces the transaction into exception queues and delays settlement. Always propagate the original authorization response fields — particularly the network transaction ID — into the capture request.
Running a single daily capture batch without exception handling means a capture failure for one transaction silently blocks revenue. Production capture pipelines must process results individually, flag failures, retry with backoff logic, and alert on persistent failures before authorization windows expire.
Dual Message System (DMS) and Tagada
Tagada's payment orchestration layer manages DMS workflows across multiple acquirers and gateways from a single integration point. Rather than building separate authorization-capture logic for each processor, merchants connect once and Tagada normalizes the DMS message flow — including capture timing rules, incremental authorization handling, and void propagation — to each downstream processor's specific API requirements.
Orchestration Advantage
When routing a transaction across acquirers for cost optimization or failover, Tagada ensures the capture message is always routed to the same acquirer that processed the original authorization — a critical requirement that single-acquirer integrations get for free but multi-acquirer setups must explicitly manage. Tagada handles this transparently, eliminating a class of settlement failures that commonly appear when merchants try to build multi-acquirer DMS routing themselves.