3 ms·
If you've ever sat down and looked at Paypal's APIs properly, for instance with a view towards a proper risk analysis and/or from-scratch integration, then this
by contingencies 12y ago
If you've ever sat down and looked at Paypal's APIs properly, for instance with a view towards a proper risk analysis and/or from-scratch integration, then this should not surprise you. I did this for the first time perhaps ten years ago, and here's what I found.
Firstly, the degree of marketing bullshit that you have to push through just to get to the truth of the APIs is staggering.
Secondly, they perform backflips to avoid telling the truth about their integration options, which is to say that they're all fundamentally insecure for real time digital goods and services unless you implement IPN plus polling plus duplicate detection / additional round-trip validation calls, ie. you can't trust an IPN notification. The degree of complexity (order state tracking, IPN state tracking and duplicate detection, retry support, running your own IPN-receiving server) and latency requested here of client businesses is immense.
Thirdly, their idea of international support is pathetic. It seems that they've basically duplicated their entire business process to other countries, translated it, and then assumed that everyone in that country requires only one human language in all of their interactions: documentation, support, emails, etc.
Finally, as is widely known throughout the industry they have a shocking reputation for the arbitrary suspension and seizure of accounts and assets, with little to no recourse for those affected.
I am not surprised that Stripe has taken off. Unfortunately, that's still lipstick on a pig: fundamentally, the settlement, risk, transparency and government interaction model of credit card networks means they are unsuitable for an increasingly large volume of business around the world.
- bkirkbri 12y agoAgreed. Over the past 9 years I've had to implement double, triple and end-of-the-month checking on PayPal to be sure that we have some reconciled idea of reality with respect to payments. What's worse, their system essentially rewrites history over time. This means that rather than keeping a ledger of payment events, they change the dates and amounts depending of payment status / reversal /etc. Querying later in the week and the data is different. For the same charge. I ended up keeping an event log of everything we ever get from them (IPN, API polling, reports) and synthesizing that into a current snapshot at query time. The code is riddled with comments saying, essentially, "this charge, then return, then recharge and failure means that the payment is OK".
- jephir 12y agoI would switch to Stripe if they offered micro-payment pricing like PayPal's 5c + 5%.
- yuhong 12y agohttps://news.ycombinator.com/item?id=7871180 https://news.ycombinator.com/item?id=7871180 Notice the questions I asked.