Thanks Sebastien Iâll let your know if we use it. And Svenâs right: beautiful! Max On 13.03.2014, at 03:12, Sebastian Sastre <sebastian@flowingconcept.com> wrote:
On Mar 12, 2014, at 7:15 PM, Max Leske <maxleske@gmail.com> wrote:
To answer my own question (RTFMâ¦):
"This is a credit card processing library. I needed this for airflowing an application from flowing.â
Where âairflowingâ and âflowingâ link to http://airflowing.com/ and http://flowingconcept.com/ respectively.
On 12.03.2014, at 23:12, Max Leske <maxleske@gmail.com> wrote:
Thanks Sebastian, very cool!
Do you use it in production, or know of anyone who does? We might want to use it too.
Forgot to mention that before doing it, I did took a look at ActiveMerchant which seems to be what Shopify uses: http://activemerchant.org/
But yeah, thatâs right. We use it in airflowing
Also in flowingâs invoice system for the consulting services we also do :D
All over https and never saving credit cards info (only the gatewayâs token of the authorised cards, the sensible data only touches RAM and gets a nice nil on the instVar after the gateway's result)
We could authorise and capture on debit cards too but the gateway weâre using has debit only for brazilian cards and doesnât provide the international debit feature (which seems to be kind of a big deal for vendors and banks)
Let me know if you want to extend its API to your gateway, just push the merge requests.
Here... this is how our invoice system looks: <flowingInvoice.png>