An individual IETF draft from Tempo Labs and Stripe that defines a Payment HTTP authentication scheme, so a server can ask for payment in a 402 challenge and acknowledge it with a Payment-Receipt header. It underlies Stripe’s Machine Payments Protocol.
Payment HTTP Authentication Scheme
An individual IETF draft from Tempo Labs and Stripe that defines a Payment HTTP authentication scheme, so a server can ask for payment in a 402 challenge and acknowledge it with a Payment-Receipt header. It underlies Stripe’s Machine Payments Protocol.
Where it stands
As of 2026-10-14, the Agentic Standards Map records:
Individual draft-httpauth-payment-01 (2026-09-09), Standards Track intended, no Working Group (WG), expires 2027-03-13; authors from Tempo Labs and Stripe. The datatracker record of 2026-10-13 gives revision 01 (time 2026-09-09 16:08 UTC) and no later revision.
Why it matters to agents
On receipts, -01 reads “Servers SHOULD include a Payment-Receipt header on successful responses”; the receipt table has four fields (status, method, timestamp, reference) and no signature field.
Sources
- https://datatracker.ietf.org/doc/draft-httpauth-payment/
- https://www.ietf.org/archive/id/draft-httpauth-payment-01.txt
- https://docs.stripe.com/payments/machine/mpp
Status and relevance quoted, shortened, from the Agentic Standards Map by Francesco Marinoni Moretto, CC BY 4.0, https://frmoretto.github.io/agentic-standards-map/. The full entry, with every dated source, is in map.json under ietf-httpauth-payment.
Industry: payments
Related standards
Standards this one builds on, supersedes, profiles or is commonly deployed beside.
