Integrate the Stripe Machine Payments Protocol (MPP) so your platform can accept fiat and stablecoin payments directly from autonomous agents using Shared Payment Tokens

Verified steps

1. Review the Machine Payments Protocol specification published by Stripe and Tempo on March 18, 2026; MPP is an open standard for internet-native agent-to-merchant payment that supports Shared Payment Tokens (SPTs) for fiat card payments, BNPL (Affirm, Klarna), and stablecoin settlement on supported rails
2. Register your merchant endpoint to advertise MPP support; an agent can probe for MPP capability via a standard discovery header or well-known endpoint — check the current MPP specification for the exact advertisement mechanism
3. Accept inbound SPT payloads from agents: validate the token scope (amount cap, currency, merchant binding, expiry) before attempting to charge; reject tokens whose scope does not match the current cart total or merchant ID
4. Process the SPT through Stripe as the payment processor: the Stripe MPP integration routes SPTs through the appropriate payment rail (card network token, BNPL provider, or stablecoin bridge) transparently based on the SPT sub-type created by the buyer's wallet provider
5. Handle asynchronous confirmation: stablecoin legs of MPP payments may confirm asynchronously relative to card legs — implement a webhook or polling handler for MPP payment status events and do not fulfill orders until the payment status is confirmed settled
6. Implement MPP-specific idempotency: tie each MPP payment attempt to the SPT token ID and the cart hash; if the agent retries with the same SPT, return the cached outcome rather than re-attempting the charge