Careful what you wish for. I used to use Amazon DevPay for S3stat and Twiddla subscriptions. It's "user-centric" like you describe, where users sign up for to

Careful what you wish for. I used to use Amazon DevPay for S3stat and Twiddla subscriptions. It's "user-centric" like you describe, where users sign up for to pay for the service through Amazon, and can later tell Amazon to stop paying for it. My thing would get webhooks when those things happened so I could update my end. But it was only user-centric, so if the user asked me to cancel their subscription, I couldn't do anything except give them a link to Amazon's page to cancel. I could have a Cancel button on my site to stop my end of things, but I had to give them a link and tell them not to forget to go over to this other site and perform the necessary steps to stop sending me money. As you can imagine, it was not optimal. I ended up on the phone with Amazon too many times begging them to please stop charging my customer money and sending it to me because neither of us want that to happen, and listening to Amazon explaining patiently that that is not something they can do. No sir, write back to your customer and tell them to re-activate their Amazon subscription then visit this page and click this series of links. Stripe couldn't arrive fast enough. The day it did, my business was gone. ... and 5 years later I still had hundreds of customers who had signed up using Amazon DevPay, which doesn't have a way of transferring payment details (again, because "user-centric"), so every one of them ended up with the same professionally-embarrassing email exchange asking them to go to a 3rd party website and perform some complicated tasks that we weren't able to perform on their behalf. And sorry.