The good ol' folks at Stripe's collaborators Tempo Labs tried to make an RFC-style description page for MPP: https://paymentauth.org/ (full doc on IETF draft page: https://datatracker.ietf.org/doc/draft-ryan-httpauth-payment...)

I almost was going to point it out as evidence there was thought put into it. Nope, it's flimsy and AI generated.

Also, it contains provisions for scamming customers:

> 403 indicates the payment succeeded but access is denied by policy

No, it doesn't explain how to refund payments for customers you deny access to.

I recently redesigned my blog to look like a modern RFC and I'm loving the way they've decided to render tables in their plain text, definitely gonna steal that.

On topic though, Stripe is trying to make themselves the Visa/Mastercard of crypto. They're in position to do so and it seems like Coinbase is their other half. I don't trust or like it though.

This one is even worse IMO

> Servers MAY return 402 when:

> * Offering optional paid features or premium content

This implies that a successful GET request to a resource that user already does have access to, might still return 402 instead of 200. This makes 402 basically unworkable.

[dead]