Marius Askildsen

Hi again and thanks for the update!

Just to clarify, I understand the credit card token is stored with Stripe. The problem is that this is forced upon the customer. I’ve never come across any major online retailer that will store credit card details or tokens (whether on their own servers or with their payment processor) against the customer’s will. The way it is now, the plugin doesn’t give the customer a choice in whether to store the token with Stripe. It just does it, which will look bad for the website using it. Customers get a bit funny about not having complete control over their credit card details. I know I would think twice about using a website again if it appeared to store my credit card token without my permission.

Great if you can give us an ETA asap for when this will be fixed. As it is now, I’m not able to launch my site because I’m relying on the Stripe plugin to work. I dislike PayPal too, just like you guys, so wanting to avoid using them at all cost.

Thanks Anna! Yes, the Woocommerce Stripe plugin lets customers choose whether or not to save a credit card token.

To play it safe I suggest making the Stripe Commissions and Gateway plugin NOT save tokens by default. That way customers won’t feel like their payment details are being stored against their will.

I know you don’t give definite dates, but do you have an approximate timeframe for when this may be fixed? I’m reluctant to launch anything with this issue still present (I want to rely only on this plugin for payments/commissions), so it’d be good to know at least whether we’re talking days, weeks or months. Thanks in advance! 🙂