Stripe - Requirement for Strong Customer Authentication

I received the following from Stripe warning of the need to change to a new version of their API. Can you confirm that a new version of the Stripe plug-in is being developed?

Thanks

On September 14, 2019, a new regulation for authentication will be introduced in Europe. Known as Strong Customer Authentication (SCA), this regulation will apply to online payments within the European Economic Area (EEA) where the cardholder’s bank and the business’s payment provider are both in the EEA. Some businesses outside of Europe may also be impacted depending on how European issuers implement the new authentication rules.

SCA requires that businesses use two independent authentication elements to verify payments. Transactions that don’t meet these new authentication requirements or qualify for any exemption may be declined starting September 14, 2019. 3D Secure 2—the new version of 3D Secure rolling out in 2019—will be the primary authentication method used to meet SCA requirements for card payments.

Stripe is building solutions to make it easy for you to comply with the new regulation and minimize the impact on conversion. We have released a beta of a new SCA-ready API—PaymentIntents, that lets you dynamically apply 3D Secure whenever it is required or there is high fraud risk. PaymentIntents will provide support for 3D Secure 2 automatically in early 2019. As soon as SCA requirements go into effect, PaymentIntents will dynamically trigger 3D Secure 2 when required and apply exemptions to SCA requirements when possible.

Currently in beta, you can find more about this API here. Over the coming months, we’ll be expanding the API’s functionality and releasing additional updates to other Stripe products to help you prepare for SCA.

hi, what features are you talking about?

please make it ready for the payments setting "sofort" from stripe.
i attached a screenshot from stripe, where the service "sofort" is possible to enable.

I also have this message from Stripe.

So, does your answer mean that the free V2 plugin will not be compatible with the new SCA?

Many thanks

I'm glad I'm not the only one who felt the response from Hikashop wasn't clear!

Let's put it another way....

Q. Will Hikashop release a new version of the FREE Stripe payment gateway which will be SCA compliant?
Q. If yes, approximately when?
Q. If not free, what will be the cost?

Thanks, Nicolas. That makes it clearer. It looks like the new regulation doesn't come in until September so I'll wait for the new V3 plug in to become available.

Thanks Nicolas, that's now clear.

Just a quick query. Is the payment a one off for this plugin or an annual subscription? Will it include all future updates?

Thanks

Dave

Hi - I have purchased the v3 plugin, but it does not appear to support 3D Secure transactions. It redirects to the listing page with an error 'Your card was declined. This transaction requires two-factor authentication.'. There does not appear to be any attempt to handle the 3D secure portion of the transaction. Until this is resolve (in terms of Stripe Payments) it is no better than the free v2 plugin. There is no real documentation supplied with the v3 plugin, nor does there appear to be any way to directly contact the developer (Obsidev). I'm a web developer myself and have purchased the plugin to save time, but as it's not functioning with the required 3D Secure features in place, I've wasted time rather than saved it. Happy to recieve message directly (off this board) or via this board in regards to this from ether Nicolas or Obsidev. If the update to support 3D Secure is close but not finished, is there any way I can get most recent build with know issues so I can resolve this myself as I have a limited timeframe to get this resolved for a client? Thanks Josh

Josh,

Thanks for trying this and reporting back.

Not a good start at all.

In my opinion, I selected to use Hikashop because of it's support for Stripe. To see Hikashop drop support for Stripe, and then recommend the purchase of a 3rd party Stripe plug-in which is either not ready for 3D secure or is failing, sucks. Quite a lot.

I can understand this re: Stripe V2 plugin, but I have purchased the Stripe V3 plugin on the basis that I thought it could do 3D Secure.
The v3 Plugin is meant to use Elements, so you can initiate 3D Secure using Payment Intents API calls.
There is a migration guide here:
stripe.com/docs/payments/payment-intents...onfirmation#elements
Is this something you are working on / have worked on ?
If so, can I see the work in progress so I might push it forward to a workable solution?

I've rewritten your v3 plugin to work using Payment Intentions. I've not built in reference storage for future transactions (and there well might be changes to this portion of Stripes API around July this year), but our account process does not require it in any case. However, not providing 3D secure support on a payment integration is a complete non-starter. For my clients in the UK + EU most card transactions involve 3D secure and trying to accept payment without it would be a complete waste of time (and loss of business). I remain somewhat disappointment that I've had to pay 40Euro for something which doesn't work (in real terms) - although I do understand your frustration (especially having just read through it) with Stripe, their documentation and the rapid changes they perform on their API suite.

Hi - yes - I've written custom payment integrations for Hikashop and other carts which do this also, so understand the points in regards to time + effort. As I say, I appreciate the work involved - also that Stripe have a habbit of moving the goal posts - however the integration many people using Hikashop need is fairly simple, and the post order creation method using the Stripe JS with Payment Intent will cover many peoples requirements. For me I purchased the v3 plugin to shortcut development by purchasing a plugin I thought handled 3D secure, but found it didn't. As we're all customers at some point, I'm sure you can understand why that is disappointing - especially as you say it's 'not very complicated' (in fact it could easily run in parallel within current plugin, but with config setting on/off to switch between whether it was enabled or not. Just a suggestion/thought - it may give you more time/less pressure to resolve the more complete implementation you are working on with card payment taken directly pre-order completion. Also, while relatively straight forward, it still takes some time to develop and test and time ultimately is money in this situation at any rate.
Josh