Intents
Payment patterns for MPP
Intents define what kind of payment a server requests. Each intent specifies the shared request fields, Credential requirements, and settlement semantics that payment methods implement.
Overview
When a server responds with 402 Payment Required, the WWW-Authenticate header includes an intent parameter. The intent tells the client whether the request is a one-time payment, recurring authorization, or another payment pattern.
HTTP/1.1 402 Payment Required
WWW-Authenticate: Payment method="tempo", intent="charge", ...Payment methods implement intents on top of a payment rail. For example, Tempo supports charge, session, and subscription, while Stripe currently supports charge.
Available intents
Collect a fixed one-time payment before returning the resource
Meter high-frequency usage with reusable payment state
Collect recurring fixed payments across billing periods
Choose an intent
| Intent | Best for | Example methods |
|---|---|---|
charge | One request, one payment, known price | Tempo charge, Stripe charge, Lightning charge |
session | High-frequency metered usage with costs calculated over time | Tempo session, Lightning session |
subscription | Fixed recurring access by billing period | Tempo subscription |