4 ms·
You don't use auth and capture -- you create a customer (with the card/token) in stripe and then create a charge against the customer. Having a customer allows
by zmitri 12y ago
You don't use auth and capture -- you create a customer (with the card/token) in stripe and then create a charge against the customer.
Having a customer allows you to charge the user without entering in their info each time.
EDIT: I built beaconreader.com which is a crowdfunding site and we use stripe. One thing to note about creating customers is that on the backend Stripe (and other payment providers) tells the banks that it's a recurring charge, even if only charged once, which I believe allows them not to deal with the auth and capture step. I could be wrong, but there's something like that lets processors get away with it.
- onassar 12y agoHi zmitri: Do you have any more details on how Stripe and banks signal recurring charges. What you're describing sounds interesting, but with our app we see decent churn from the use of debit visa/mastercards
- zmitri 12y agoNo details whatsoever but I can across this because customers at certain banks asked why their one time charges were showing up as recurring in their bank statements. I emailed in to stripe asking what was up and they let me know it was standard practice to do that, and it would do so if I used a stripe customer.