|
|
|
|
|
|
by saurik
1181 days ago
|
|
|
> Amazon used to NEVER cancel projects that customers were using. They just straight up Did. Not. Do. It. FWIW, Amazon killed Amazon Flexible Payments in 2015. They ostensibly replaced it with Amazon Pay, but they didn't offer any kind of migration path for existing users/accounts (which felt very much like a Google thing to do) and, frankly, the services were fundamentally different: the former was more like a better version of PayPal, while the latter is more like a worse version of Stripe. I had a lot of contact with the team as this happened as I was their biggest user on mobile devices for years, and they begged me to move to their new product, but they were really screwing me by shutting down the old service in the way they did--deleting the account history and customer connections rather than just figuring out a new way to use them--and the new service not only comparatively sucked but was way more expensive (trying to command the Stripe premium, forcing me to rely solely on PayPal, which is much cheaper for small payments if you ask for their micropayments pricing). But like, Amazon Flexible Payments was amazing. They seriously had a pricing model that automatically scaled into separate buckets all the way down to tiny tiny tiny fractions of a single cent (on which they changed like 25% with no fixed component) when using your balance, while supporting all of the standard use cases for large ($12+) payments that Stripe is good at, having the API prowess of AWS attached to the flexibility of PayPal but using your Amazon.com account's payment information. But like, it had seemed as if they internally lost all the engineers working on that project and could no longer fix even basic things like their email template. It definitely soured the otherwise excellent long-term support experience I've had with Amazon services. |
|
|