Live data from Hacker News

PayPal Acquires Braintree for $800M

techcrunch.com

11–20 of 187 posts

Re: PayPal Acquires Braintree for $800M

#16

This has put me off of Braintree and on to Stripe, but not for the reasons you might suspect. You see, I still want to take PayPal payments from my customers who prefer it. But it doesn't seem like a good business to have all my eggs in one basket, and using a competing payment system gives me the ability to switch PayPal off if they try any shenanigans.

That's why I only code against Spreedly [1] instead of directly against any payment processor. One API instead of 53, switch processors just by changing a variable, and you can securely store customers' payment info without locking yourself into any processor's vaulting solution either.

1: https://spreedly.com/

Re: PayPal Acquires Braintree for $800M

#18
post #15

We were just about to add payments to our site, and Braintree was high on the list to checkout. Any other suggestions in addition to Stripe? -edit- This seems like a good list: http://gatewayindex.spreedly.com

If you do at least $3-5k/month in transactions, a real merchant account from a bank/ISO/MSP. I pay $0.05 + 0.04% markup over interchange. Even after the monthly and gateway (Authorize.net) fees, that's around 2%, compared to Stripe's 2.9% or PayPal's 2.2% (I qualify for their merchant rate discount). Amex cards are the only ones I pay more for by not doing a flat rate.

[By coding against Spreedly, it's possible to do things like send all Visa and MasterCard charges to Authorize.net, and all Amex charges to PayPal for the flat rate, without ever seeing the cardholder data myself. I don't though.]

Re: PayPal Acquires Braintree for $800M

#20

This has put me off of Braintree and on to Stripe, but not for the reasons you might suspect. You see, I still want to take PayPal payments from my customers who prefer it. But it doesn't seem like a good business to have all my eggs in one basket, and using a competing payment system gives me the ability to switch PayPal off if they try any shenanigans.

That's why I only code against Spreedly [1] instead of directly against any payment processor. One API instead of 53, switch processors just by changing a variable, and you can securely store customers' payment info without locking yourself into any processor's vaulting solution either. 1: https://spreedly.com/

But instead you are reliant on Spreedly. Looks interesting though.
Post reply on HN