Machine Payments Protocol
Value Proposition & Features
- Multiple payment rails: The SDK can expose ordered EVM charge offers, Tempo Payments charges, Stripe-backed stablecoin charges, and Stripe Shared Payment Tokens. [1] [2] [3] [5]
- Non-mutating validation:
validateCredentialchecks credentials without settling, reserving funds, or broadcasting a payment. [6] - Stablecoin and fee sponsorship support: Tempo methods can use stablecoins, optional MACH swaps, and configurable fee-payer policies. [7]
- Replay and challenge binding: Challenges can receive an HMAC-SHA256-derived identifier from server-side parameters and a secret key. [8]
Product Roadmap / Announcements
History and Origin Story
mppx TypeScript SDK and show integrations co-developed around Tempo and Stripe payment infrastructure, but they do not provide a reliable founding date, founder list, or detailed origin story.
[1]
[2]
[7]
Market Sizing
Category, Market Size, and Category Growth
Competitive Landscape
Who it's for, who it's not for
Viable Alternatives
- x402: A viable alternative or adjacent protocol for EVM-based HTTP payment challenges; MPP’s EVM method can be configured with an x402 facilitator. [3]
- Stripe Shared Payment Tokens: A viable rail for Stripe-centric implementations, though within MPP it is presented as an integrated payment method rather than a complete protocol alternative. [5]
- Direct Tempo payments: A lower-level alternative for applications willing to integrate Tempo settlement without MPP’s challenge and credential lifecycle abstractions. [7]
Competitor Table
| Competitor | Description |
| x402 | EVM-oriented HTTP payment infrastructure that MPP can use through a configured facilitator. [3] |
| Stripe | Mainstream payment infrastructure whose Shared Payment Tokens and PaymentIntents are integrated into MPP. [1] [5] |
| Tempo | Stablecoin payment infrastructure used by MPP for on-chain charges, subscriptions, swaps, and fee sponsorship. [10] [7] |
| Custom EVM settlement | Bespoke payment implementation for teams that need direct control over credential checks, chain-state validation, replay protection, and settlement. [6] [3] |
Sources
[1] 2026, Nov 02. mpp.dev . stripe.create | MPP - Machine Payments Protocol . Generated: 2026, Nov 06. Perplexity API response.
[2] 2026, Nov 02. mpp.dev . stripe . Generated: 2026, Nov 06. Perplexity API response.
[3] 2026, Nov 02. mpp.dev . evm server method . Generated: 2026, Nov 06. Perplexity API response.
[4] 2026, Oct 26. mpp.dev . Challenge.fromResponseList . Updated: 2026, Oct 31. Generated: 2026, Nov 06. Perplexity API response.
[5] 2026, Oct 26. mpp.dev . stripe.spt | MPP . Updated: 2026, Oct 24. Generated: 2026, Nov 06. Perplexity API response.
[6] 2026, Nov 02. mpp.dev . mppx.validateCredential | MPP - Machine Payments Protocol . Generated: 2026, Nov 06. Perplexity API response.
[7] 2026, Nov 02. mpp.dev . Method.tempo.charge . Updated: 2026, Nov 04. Generated: 2026, Nov 06. Perplexity API response.
[8] 2026, Oct 26. mpp.dev . Challenge.from . Updated: 2026, Oct 31. Generated: 2026, Nov 06. Perplexity API response.
[9] 2026, Oct 26. mpp.dev . Challenge.meta . Updated: 2026, Oct 31. Generated: 2026, Nov 06. Perplexity API response.
[10] 2026, Nov 02. mpp.dev . Method.tempo.renewSubscription | MPP - Machine Payments Protocol . Generated: 2026, Nov 06. Perplexity API response.