FEATURE REQUEST: Charge via Stripe Customer ID for more Secured Transactions.

  • Profile Image
    Asked on June 30, 2013 at 09:35 AM

    We would be able to charge a customer via Stripe by passing the Stripe Customer ID into the form rather than credit card information. This is the second step of implementation of creating a customer in Stripe via a form. This allows credit card data to be stored securly on Stripe's Servers and then be accessed using the Customer ID which does not need to be stored securely because it can only be used with the Stripe Merchant Account that created the Customer ID.


    See: http://www.jotform.com/answers/231815


    See https://support.stripe.com/questions/can-i-save-a-card-and-charge-it-later


    The purpose of this is to collect credit card information when we sign up new resellers and charge them each time they place an order, without have to re-enter their credit card information.

    When we sign up a new reseller we need to get their credit card information on file, so that we can charge it WHEN they make purchases, which is usually NOT the same time they sign up. In the past we have stored it in a locked file cabinet, a pain for many reasons as you can image, including getting to it on the weekends.

    However, Stripe has it's own PCI complient virtual filing cabinet, they call it creating a customer. It sends all the data to Stripe, Stripe destroys the credit card information (making it NEVER recoverable to human eyes) and sends back the customer ID (that looks something like cus_34rirNeJBqKmYV).

    That customer ID is useless to anyone except us, but to us it is as good as a credit card number, actually better, because we can store it anywhere, unencrypted. That is because it ONLY works with our Stripe account, and no one elses. We can pass that customer ID to stripe with a dollar amount and create a charge, once, once a month, whenever.

  • Profile Image
    Answered on June 30, 2013 at 01:12 PM

    Hello, I've read your details and decided to open this up as a Feature Request for consideration by our Development Team. They will look into this to see what's suitable to best meet everyones needs and we will most certainly update you here if something like this is implemented. But at the moment I won't be able to say exactly when or if at all though I do think that this is a really good suggestion and thank you for your input.