Create a Stripe Issuing cardholder and issue virtual or physical cards linked to your corporate travel program; configure spending controls at the card or cardholder level
Define MCC-based spending restrictions on the card object by specifying allowed or blocked merchant category lists; travel-relevant MCCs include ranges in the 3000s for airlines, 4000s for ground transport, and 7000s for lodging
Listen to the issuing_authorization.created webhook event; each authorization payload includes a merchant_data object with the category field containing the MCC for the transaction
Implement the real-time authorization webhook handler to approve or decline based on your travel policy rules; return a 200 response within the Stripe-required latency window to avoid timeouts that default to decline
Query the Authorizations API after the fact to retrieve historical transaction data filtered by merchant category for reconciliation reporting
Map MCCs to your internal expense categories for automated coding; note that the same merchant may post under a different MCC than its primary business type depending on how it is registered with the card network
Known gotchas
Real-time authorization webhook responses must be returned within a strict latency window; synchronous policy logic that calls external systems during this window risks timeout-based declines on legitimate travel purchases
MCC assignment is controlled by the merchant and card network, not by the issuer; a hotel that processes a restaurant charge may use a lodging MCC or a restaurant MCC inconsistently across transactions
Stripe Issuing is not available in all countries; verify regional availability before designing a global travel card program on this platform
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp