2 ms·
Exactly. Not tied to a payment gateway's integration code or a 3rd party service provider like Recurly or Spreedly. No transaction fees or external dependenci
by brockf 16y ago
Exactly. Not tied to a payment gateway's integration code or a 3rd party service provider like Recurly or Spreedly. No transaction fees or external dependencies.
- johns 16y agoWhen it comes to marketing to software developers, I think this is a disingenuous use of the term. It's not open source and the provider list is controlled by you. And how does this solve being effectively tied to a specific provider? If I start with Authorize.net, isn't this using CIM to store all my customer payment profiles? Can I switch at will and take all my profiles with me to Payflow Pro? I like the host-your-own-Spreedly idea to save on transaction fees. I think that should be your primary selling point.
- brockf 16y agoTrue. It's not free and open-source. And, until Braintree's Credit Card Data Portability movement takes a foothold, it's impossible for OpenGateway to transfer CIM data to another payment gateway (though we'll be the first on that train when it comes). However, the "open" part of this solution is, to me, that: 1) You choose which gateway you want to use based on its price, service, etc. - not because there's some free PHP class available for it or the API makes slightly more sense than the others. 2) You can run your own billing engine and open up the API, so to speak. 3) You aren't gaining billing engine power by giving up more transaction % fees or relying on a 3rd party service provider's closed system.