Hacker News new | past | comments | ask | show | jobs | submit login

You want a local, independent gateway and acquirer anyway (same jurisdiction, language, support…) which both Spreedly.com and Recurly.com support with http://www.WireCard.com/

In bad circumstances you don't want to lose all your payment infrastructure e.g. if paymill or stripe go out of business/have issues. That's why dealing with 2 parties may look odd but in the end it is worth the effort.

If you have problems paying the 50-100$ monthly fee, then your business is the problem. Not your payment partner.

(WireCard is a profitable, public credit-card processing bank, the chances that they go out of business is much lower than VC driven payment startups. See http://www.wirecard.com/investor-relations/ for details. They do CC-payments for Deutsche Telekom and Lufthansa. >11 Billion Euro/year)

If you have problems paying the 50-100$ monthly fee, then your business is the problem.

Why should a scrappy startup pay an extra 50-100$ when it doesn't have to?

Why should a scrappy startup deal with the horrible paperwork of payment gateways on top of the horrible integration, when it doesn't have to?

You make no sense.

Seconded. I run an ecommerce site that has more than 100k in sales per year but only 10 to 20% go through credit cards. I sure will not file endless paperwork and do long integration just to move away from paypal. But I signed up for paymill in a second because it will provide what I really need (a nicer payment process) and spare me a lot of hassle. The processing fees on 20k is 580 for Paymill so it would even be cheaper. If the shop grows tenfold then sure lets integrate with the XML over fax machine API of a real bank.

If Stripe were to go out of business, it wouldn't really impact your use of Spreedly. They just charge the gateway, not store information there, so it's not a big deal.

I agree with the last statement, however, the chance of Stripe/Paymill going out of business pretty much equals that of Wirecard going haywire.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact