3 ms·
"just about every payment gateway supports storing customers' info to charge at a later time." "No, you simply send the card details to the payment gateway whi
by drone 14y ago
"just about every payment gateway supports storing customers' info to charge at a later time."
"No, you simply send the card details to the payment gateway which vaults them. You get back a token to reference to make the actual charges in the future. You don't have to do an authorization up front. Virtually every payment gateway has such a feature. There's no need to implement storage on your own and take on the compliance burdens."
Neither Authorize.net nor MES do. (Two of the largest in the US, that I've been using for the past few years.) I only know of a few specialized players that offer such functionality.
- dangrossman 14y agoHuh? Both of them do. I've been using Authnet's vault for almost 8 years. I've also integrated with 8 other gateways that offer payment info vaulting. It's a standard feature for any competitive gateway at this point. http://www.authorize.net/solutions/merchantsolutions/merchantservices/cim/ http://www.authorize.net/solutions/merchantsolutions/merchan... http://merchante-solutions.com/files/MES_PaymentGateway.pdf http://merchante-solutions.com/files/MES_PaymentGateway.pdf I'm surprised you've been using these gateways for years and didn't know about these features. CIM is prominently advertised on the first page you see every time you log in to the gateway.
- drone 14y agoDang, color me educated =) I haven't had either of those features enabled in my UI, but that wouldn't surprise me as I've often had to ask them to re-enable basic features (like backoffice w/ MES) when they get accidentally turned off. I'm presuming these features need to be negotiated as part of the deal, and as I haven't needed them, they were never brought up.