Payment HTTP Authentication Scheme (draft-httpauth-payment, Tempo Labs and Stripe)
IETFspecificationcontext entry
Verified 2026-10-14. Status as of 2026-10-14. All entries.
Seams: S4
Status
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.
Relevance
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.
Committed next
None declared in the sources read.
Sources
- https://datatracker.ietf.org/doc/draft-httpauth-payment/ official decision or commitment, read 2026-10-03 · archived
- https://www.ietf.org/archive/id/draft-httpauth-payment-01.txt participant or third party, read 2026-10-03 · archived
- https://docs.stripe.com/payments/machine/mpp maintainer or chair statement, read 2026-10-14 · archived
Neighbours in the map
Solid lines: overlaps declared by one of the two entries. Dashed lines, coloured by seam: entries named by the same seam (S1 to S4) in the seams note. Every node is a link.
Evidence and coverage
- Read
- On 2026-10-13: the datatracker record.
- Not read
- Full -01 text, payment method and intent specifications on mpp.dev, software development kit (SDK) licensing, IETF list discussion, Tempo pages. mpp.dev was not read again on 2026-10-14: its robots.txt carries the signal ai-input=no.
- Not found
- Not found, 2026-10-03, in -01: agent protocol, card network, AP2, x402, Verifiable Intent; in the eight lists: the draft name. The Stripe page on the Machine Payments Protocol (MPP), read 2026-10-14, describes MPP as "co-authored by Stripe and Tempo" and does not mention this draft; a statement by a primary source that links the draft to MPP: not found there.