It seems like this is designed for atomic purchases, could it be extended for subscriptions?

Hey, I'm one of the developers at Tempo. We're working on an extension type for subscriptions to propose being added to the spec as well! We're starting with the simple types, but subscriptions are a natural extension. The subscription intent will work similarly to a one-time charge—the server returns a 402 with intent="subscription", and the client signs a recurring authorization.

	▲	david_shi 4 hours ago \| parent [-]
		Cool, would be nice to get specifics on how payments are processed, failures, and cancellations re: the recurring model.

▲

jacobn 7 hours ago | parent | prev [-]

> MPP provides a specification for agents and services to coordinate payments programmatically, enabling microtransactions, *recurring payments*, and more.

▲

david_shi 7 hours ago | parent [-]

https://docs.stripe.com/payments/machine/mpp

Yeah I read that copy too, did you read the spec?

	▲	dabbz 6 hours ago \| parent [-]
		I believe the Shared Payment Token is interchangeable with a payment method id that you attach to a customer object, but that link has very sparse information about how things actually work end to end and what objects mean what.