Posted: March 6, 2019 at 7:35 am
|
Hi. I am an Espresso 3 user. Updating to Espresso 4 is not an option as I need the recurring events feature in the calendar. We noticed that you are passing your cardholder’s full credit card number to Stripe’s API. We strongly discourage you from handling this information directly because doing so: Potentially exposes your customer’s sensitive data to bad actors Excludes your payments from protection by Radar, Stripe’s fraud protection solution Requires your business to meet complex and burdensome PCI compliance requirements To keep your customer’s information safe, we were unable to process the unsafe charge you just sent us. In order to process payments securely on Stripe, change your integration to collect payment information using tokenization. Tokenization ensures that no sensitive card data ever needs to touch your server. 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. For any questions, just reply to this email and we’d be happy to help. Yours, The Stripe Team |
Hi, I can advise to use Event Espresso 4. EE4 does support multiple datetimes within one event, which can be used as an alternative to Recurring events. This way you can get set up with the latest Stripe Checkout available with EE4. |
|
|
This reply has been marked as private. |
You have the option to create a ticket for each datetime, but it does not automatically create a ticket for every datetime (it’s optional).
EE4 has its own calendar add-on: |
|
|
Hi, Josh. |
|
Based on what you tell me multiple events does not work for me. It is completely inadequate for what I need to do. |
One other option in that case, is follow Stripe’s advice where they note:
This option isn’t any less safe than using the original Stripe API, (they basically do not recommend using the original Stripe API anymore). Then when EE4 gets REM or when EE3 gets an updated Stripe gateway that’s production-ready, whichever happens first, you can update the software to make use of the new features. |
|
|
This reply has been marked as private. |
REM for EE4 is currently a work in progress. Since it requires a complete overhaul of the EE4 event editor and it’s being built on a similar stack as Gutenberg, I do not have a release date.
There is work that’s been put into updating EE3’s Stripe gateway. So far this has involved changes greater than a few dozen hundred lines of code. For example, the Stripe library needs to be updated, and the billing form requires being converted to Stripe Checkout. When the work is available for testing I can update this topic to let you know it’s ready if you’d like to test it. |
|
|
This reply has been marked as private. |
The support post ‘Urgent: Stripe is not processing.’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.