3 ms·
I wasn't implying that you were, I was just trying to be clear. Why is simple. It's the economics. If you're a startup that does lots of micro-transactions you
by smokinn 17y ago
I wasn't implying that you were, I was just trying to be clear.
Why is simple. It's the economics. If you're a startup that does lots of micro-transactions you're paying a good chunk of overhead in gateway processing fees. If you feel it's worth the continual development effort (because don't kid yourself, writing a secure internal gateway takes a long time and essentially never ends) then you do it.
In Blippy's case they probably had to write their own because I don't know of any 3rd party gateway that has an API to return a list of user purchases when you give them a credit card number. I'm actually surprised the banks even support that kind of request.
- run4yourlives 17y agoIf you feel it's worth the continual development effort then you do it. I would think that when you start thinking your first application requires a second application (that you have to build yourself) just to efficiently exist, you should be taking a good solid look at the viability of your idea. In Blippy's case they probably had to write their own Case in point I suppose. PCI compliance isn't something a startup should be looking to saddle themselves with, in my mind. Once you're established and can analyze whether you want to internalize an outsourced function, it's on the table with everything else I suppose.
- smokinn 17y agoPCI compliance isn't something a startup should be looking to saddle themselves with, in my mind. Once you're established and can analyze whether you want to internalize an outsourced function, it's on the table with everything else I suppose. Exactly. That's the point I was trying to get across. Guess I wasn't very clear. =)