yes, it's bad; not just bad, it's borderline insane, given the resources they have to make something awesome. there are no fewer than 4 different APIs and endp

yes, it's bad; not just bad, it's borderline insane, given the resources they have to make something awesome. there are no fewer than 4 different APIs and endpoints to do the same thing, each with strange feature omissions / quirks and differing names for the same variables (sometimes just case). there is a separate sign-up for each service, with all-new verification; it's like they absorbed 10 different competing payment services, kept their original APIs and rapidly churned each of them into some additional shitty branded product. what's worse is that FPS was the best option as it could do what you wanted, how you wanted without being forced into a specific UI/pipeline. now FPS is being discontinued [1] and everyone is being shoved into the widget-only "Login and Pay with Amazon" if anyone knows of a way to retain the "leave-to-log-in -> select funds source -> come-back-with-token" process, please let me know. we're trying to keep our UI the same for all payment processors/methods, this widget requirement is not going to work for us. [1] https://payments.amazon.com/help/201626250 https://payments.amazon.com/help/201626250