| It's hard to be certain from the outside, but my impression is: - Fractured product line; they have a bunch of products that are similar but different and they themselves are confused about which is which. Product management is in chaos. - Tech debt from the 90s that has never been paid off. - Acquisitions that were poorly integrated. - Some weird attempt to mash their platform together with ebay that never quite fully baked, then more debt incurred hastily ripping them apart again. - Some attempts at outsourcing development overseas? Can't be certain about this, just an impression. - A major attempt to rewrite their API, but instead of simplifying they got an architecture astronaut to design it. He wrote a lot of annoying blog entries about HATEOAS but AFAICT no longer works at the company. The modern API was published but it's broken and crippled in so many different ways that they would be better off putting a big "DO NOT USE" at the top of their documentation. - They've effectively abandoned the new API and apparently are relying on a sort of reverse-takeover from Braintree to save them. Maybe there is progress but it's been a while and I don't see any. |
All most merchants wanted was "let me accept credit cards with quick and easy setup, even if it's expensive." (Hence the success of Square, Stripe, etc.). All they needed to do was to offer a few APIs that acted like every other credit card gateway, and they'd be fine.
But instead, they went whole hog on telling consumers "you never need to give the retailer a card number." Now, I'm skeptical this was ever a huge selling point, but it means that any API they can ever offer will always be a nonstandard mess to work with because it means you're going to have to bounce users off your site to finish checkout.