payment intent
A payment intent is the kind of obligation a payment challenge is asking for: a one-off charge, metered usage, or a recurring subscription. MPP names the three and puts the choice in the challenge itself, so a client learns which commitment it is being asked to make before it pays.
The three are defined by the protocol that names them. A charge intent defines one-time payments, for a client paying once for a resource. A session intent defines metered pay-as-you-go payments, for usage that is frequent. A subscription intent defines recurring fixed payments, for access that renews. A pay-per-call endpoint is asking for a charge.
Naming it in the challenge is what makes the difference readable from outside. The payment challenge MPP defines carries intent as a required parameter beside the payment method, the challenge identifier and the protection realm — so the commitment and the price arrive in the same response. The Internet-Draft behind the protocol takes it further and defines the intent as a registered value, with each intent specified in a document of its own.
→ probe402 records what each tracked endpoint asked for at each check — open an endpoint from the endpoint list.
Sources
- The Machine Payments Protocol specification siteMachine Payments Protocol
- Protocol: challengesMachine Payments Protocol
- The 'Payment' HTTP Authentication Scheme (Internet-Draft, individual submission)IETF Datatracker
Related pay-per-call API · payment challenge · MPP · micropayment