MPP
The Machine Payments Protocol — HTTP 402 with payment-method-agnostic credentials.
In development
This rail is being implemented against the core v2 contract. Option names below may change; this page will be updated with a tested example when it ships.
MPP uses the HTTP authentication flow: the server responds 402 with a WWW-Authenticate: Payment challenge, and the client retries with a payment credential in the Authorization header. MPP is payment-method agnostic — stablecoins and cards through a provider.
import { mpp } from "@tollstile/mpp";
createTollstile({
rails: [
mpp({
provider: stripeProvider({ secretKey: process.env.STRIPE_SECRET_KEY }),
}),
],
});Intents
| Intent | Status | Use |
|---|---|---|
charge | Planned v0.1 | One payment per call |
session | Planned v0.2 | One authorization covering many calls |
Cards stay with the provider
When an agent pays with a card through MPP, card data is handled by the provider. Tollstile never receives or stores card numbers, which keeps your application out of card-data scope.
Details subject to the specification
Option names and capability values will be finalized against the current MPP specification before release.