Protocol

MPP Compatibility

How Scribe Finance interoperates with the Machine Payments Protocol from Stripe and Tempo.

MPP (Machine Payments Protocol) is an open standard for machine-to-machine payments over HTTP, published by Stripe and Tempo in March 2026 and tracked at the IETF. It builds on the x402-style request-pay-retry pattern, layering in Stripe’s billing infrastructure and Tempo’s L1 as a settlement layer.

Scribe Finance is designed to be legible to MPP clients: an MPP-speaking agent can transact with Scribe Finance endpoints, with settlement carried on Robinhood Chain rather than Stripe or Tempo rails.

How MPP relates to x402

MPP and x402 share the same skeleton: a 402 Payment Required response prices the resource, the client pays, and a retry carries the proof. MPP’s contribution is rigor, an IETF draft that specifies:

  • A standard schema for payment negotiation
  • Named settlement profiles (Stripe and Tempo today, with room for more)
  • Structured error codes and retry semantics

An MPP-compliant agent should parse a Scribe Finance HTTP payment response without difficulty. The two diverge only at settlement: MPP defines Stripe and Tempo profiles, while Scribe Finance settles on Robinhood Chain.

What this means for agent developers

An agent that already implements the MPP client spec (through a framework, for instance) needs no code changes to consume Scribe Finance-powered endpoints. It parses the 402, selects a scheme it understands, pays, and retries; which chain settles the payment is invisible at that layer.

The single detail an MPP agent will observe differently is the payment object’s network field:

{
  "network": "robinhood-mainnet",
  "token": "0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168"
}

An endpoint settling through Stripe would present Stripe’s settlement details in that position. Any agent with a Robinhood Chain wallet and a route to the Scribe Finance Facilitator can complete the payment.

What this means for service providers

If Stripe already handles your MPP payments, Scribe Finance drops in as a second settlement option with your API structure untouched. The payment gate adds a Robinhood Chain native entry to your 402 response alongside the Stripe one; each agent picks the option its wallet supports.

Scribe Finance’s IETF roadmap

We intend to contribute a Robinhood Chain native MPP settlement profile to the IETF draft, alongside the Stripe/Tempo submission. That work lands in Phase 3 (Q1 2027), once the MPP specification is mature enough to accept an alternative settlement profile.

Current status

During the beta, MPP compatibility is maintained informally: the SDK emits and accepts responses that align structurally with MPP, and formal certification against the IETF draft follows after beta. If you build an agent framework and want to validate Scribe Finance’s MPP compatibility against your stack, reach out through the beta program.