|
thinkbiglearnsmart
|
March 7, 2019 at 1:04 pm
Hello,
We’re testing the Stripe gateway on EE3 and getting the following error inside the Stripe logs:
“message”: “Sending credit card numbers directly to the Stripe API is generally unsafe. We suggest you use test tokens that map to the test card you are using, see https://stripe.com/docs/testing.”,
“type”: “invalid_request_error”
We’ve been using the test credit card numbers in the Stripe docs. Is tokenization implemented in EE3’s Stripe gateway? Does it still work?
Thanks.
|
|
Josh
|
March 7, 2019 at 1:08 pm
Hi,
The current version of EE3 does not use tokenization in the Stripe gateway. That’s coming in a future update.
|
|
thinkbiglearnsmart
|
March 7, 2019 at 1:34 pm
I wonder if since the creation of this gateway Stripe has increased their requirements because as-is, I’m not able to successfully complete a test transaction due to this error. Can you confirm that this should be working?
|
|
Josh
|
March 7, 2019 at 1:38 pm
Yes. Since the time that the original EE3 Stripe gateway was built (it uses the original Stripe API), Stripe no longer recommends using the original API. It can still work but it requires making a change in the Stripe account. This is part of the notification from Stripe:
In rare cases, you may have to continue handling full credit card information directly. If this applies to you, you can enable unsafe processing in your dashboard.
|
