Hi. This module seems extremely useful and I was able to test the card on file capabilities with Authorize.net. Question: will there be future integration with tokenized payment gateways like Stripe and Braintree? Both of these services submit the credit card client side so there is no card information stored. However, you can use their API to retrieve the same limited credit card information that is stored in the Card on File db tables.

Possible pain points that I see:

  • Needing and additional call out to the external API to retrieve said limited information after the payment was processed so it can be stored in the Card on File database tables.
  • Need to grab a new 1-time token while moving through the checkout process to submit the new payment (instead of a static reference used for Authorize.net CIM)
  • Need to load the altered credit card form on credit card update forms in the user account pages.

I think this would be pretty nifty, but it would clearly add some complexity. However, it would make this module open to all tokenized payment methods that reduce a majority of the PCI requirements.

Thoughts?

Comments

berenddeboer’s picture

Is Stripe integration useful for 1-time tokens? I think Commerce Stripe works perfectly for that.

What we need is Stripe customer creation integration. Writing that right now.

rickmanelius’s picture

Stripe (like Braintree payments) is really geared for 1-time tokens. The real issue is whether or not a customer is willing to make the move to Stripe as it's more friendly for developers versus a turnkey solution for someone just wanting to turn on authorize.net and be done with it.

torgospizza’s picture

This sounds similar to how Payflow works. I'd love to have some developer documentation to help integrate the two!

mesch’s picture

Issue summary: View changes

Commerce Card on File support is now available in Commerce Stripe rc6. The implementation follows closely that used for Commerce Authnet.

bojanz’s picture

Category: Feature request » Support request
Status: Active » Fixed

Issues like this should be feature requests for the integration modules of the mentioned gateways.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.