jarmos

To be honest the last reply irritates me a bit as this is the official replacement for the previous plugin. How can it be in a state where things are still not ready and it causes basic issues?

There needs to be some kind of a real solution to this as it’s seriously interfering with business, not just a workaround.

We’re also seeing the same issue, especially in the past week or so.

Same here. We use Stripe as well as Braintree, Paypal, GoCardless.

Hi,

Yup.

Hi,

I do believe that Woocommerce Subscriptions can do this without Klarna’s support in a similar way they do with Paypal Standard or GoCardless when they don’t use their native options. We’re in the UK, though.

We do have $0 orders but they are renewal ones where the whole subscription period has been paid for already, so it doesn’t need to go through the payment gateway nor do I think it does.

When is this update happening as it for example prevents Hotjar from working?

Hi,

Thanks for the reply. However, Subscriptions supports Stripe and Stripe itself supports a flow from iDeal to SEPA payments: https://stripe.com/docs/sources/ideal/recurrin & https://stripe.com/gb/payments/payment-methods-guide#ideal. So the question is, is that somehow done in your plugin?

As for the SEPA payments and order statuses, I suspect you have the same issue as the GoCardless plugin has. Namely, after payment the order immediately gets on ‘processing’ while the actual payment is confirmed in 5-7 business days (https://stripe.com/gb/payments/payment-methods-guide#sepa-direct-debit).

What should happen is that the order is ‘on-hold’ until it’s confirmed or even paid out to the merchant.

Additionally, when the orders are payed by SEPA (as in, they are not immediately confirmed) then which status will they be given? It’s been a huge issue with GoCardless that immediately puts them on ‘processing’ while the payment might not even make it to the merchant.

Hi,

Got back from Braintree:

“In our original attached communication, we were attempting to be proactive in notifying merchants about upcoming PSD2 deadlines, but the dates were not meant to represent the release dates of Braintree’s production SDKs. I understand how our messaging could have been easily misinterpreted.

Generally speaking, Braintree has released updated JavaScript, iOS, and Android SDKs that are able to support 3DS 1.0 and 2.0 calls in beta, so developers can begin integrating and testing in the sandbox environment now. The production SDK, however, is not yet completed. Still, we encourage developers to begin testing in the sandbox environment as soon as they can so 3DS 2.0 can be implemented as soon as Braintree’s new production SDK is released.

Regarding the deadlines you mentioned, the April deadline is for issuing banks by the card brands (e.g. Visa, Mastercard, etc.) to support 3DS 2.0 messaging. This means that if an EU issuer does not support 3DS 2.0 and a merchant submits a 2.0 message, the card-brand will stand-in and provide a no-challenge authentication which grants the merchant a liability shift. This largely affects issuing banks but should not have a significant impact on your declines as a merchant.

The September deadline, however, is when the PSD2 regulations for issuing banks to enforce Strong Customer Authentication take effect. When this happens, there is a much higher chance that any given issuing bank will issue a soft decline when 3DS information is not present on the transaction. This deadline will likely have a larger impact on merchants.

To be clear, while I don’t have a specific date available, I can confirm that Braintree’s 3DS 2.0 production SDKs will be released in advance of the September deadline. That way your plugin’s team of developers will be able to implement it well before it affects your processing in any way. We will of course send notification to merchants and update our blog as soon as we have more information about a go-live date.”

So not sure what to do.

I’ve also contacted Braintree about their own email and the status of the SDK. Will report back once I get a reply.

What Braintree has been emailing us about for the past 3-4 months is this:

“Braintree recommends that merchants integrate 3DS 2.0 into their checkout experience by April 2019 per the card brands’ guidelines. The beta version of the web SDK is now available to integrate and test in the Sandbox. It will be ready to use in production soon. Please reference our 3DS 2.0 adoption guide for more information on how to make this change.

For merchants using a third-party shopping cart provider, you’ll want to reach out to them for details on their plans to meet PSD2 SCA requirements.

When is the deadline?
Although the date of enforcement isn’t until September 2019, card issuers may begin to require that transactions meet SCA requirements any time after April 14, 2019, so being ready when the 3DS 2.0 protocol is active is an excellent proactive measure that can help you avoid unnecessary declines.”

So you see how it should’ve been already done?

Hi,

Any news on the update? It really is a crucial issue that needed to be resolved 2 months ago.

Indeed – did try that too but did not work. Will share my details on Messenger.

Sure. The settings can be found here: on Dropbox. The link is this one. As you can see on the post page it’s not displayed but it i on the archive page.