Understand that card networks permit overcapture within a defined tolerance (e.g., a percentage above the authorized amount) for specific MCCs such as restaurants, taxis, and fuel; confirm the exact tolerance for your MCC with your acquirer.
When the final transaction amount exceeds the authorization (e.g., tip added at a restaurant), submit the capture with the final amount rather than re-authorizing.
Do not exceed the network-permitted overcapture tolerance; amounts beyond the tolerance will be declined at settlement or result in interchange downgrade.
For larger variances (beyond tolerance), perform a re-authorization for the new total before capturing.
Track overcapture events in your reconciliation system — the settled amount will exceed the authorized amount, which can confuse standard auth-to-settlement matching.
For tip adjustment flows, some acquirers offer a dedicated tip-adjustment API or a completion message type — prefer those over generic overcapture if available.
Known gotchas
Overcapture tolerances vary by card network, card type (credit vs. debit), and MCC — do not apply a uniform tolerance across all cards without validating network-specific rules.
Exceeding overcapture limits can trigger issuer disputes or chargeback reason codes related to incorrect transaction amounts, even if the cardholder consented to the additional charge.
Stripe's standard capture flow caps captures at the authorized amount in many configurations; verify whether your Stripe integration or plan supports overcapture before relying on it.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?