Payments · protocol · Individual IETF draft (Tempo Labs and Stripe)
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.
datatracker.ietf.org/doc/draft-...The standard
Individual IETF draft (Tempo Labs and Stripe)Governing body
0tagged with it
Providers that carry Payment HTTP Authentication Scheme 0
No provider in the catalog carries this standard as a tag yet. That is a statement about the catalog's tagging, not about adoption: a provider that implements Payment HTTP Authentication Scheme and says so in its APIs.json profile appears here on the next build. Add or correct a listing.
Read from the API Evangelist standards directory, facts verified 2026-10-14. Provider links come from the catalog's own identity tags and are rebuilt nightly. If this page is wrong about a standard or a provider, say so.