@petimi,

We actually released the Braintree SDK update prior to May 1st to allow for continued API interactions with the Braintree Gateway.

We’re now planning out the SCA integration and are in active development.

Do you have any news on the Braintree gateway update perhaps that you mentioned in the article?
We have been getting messages from Braintree like this – “Our records show that you are using a legacy SDK version that is not compatible with an upcoming update to our root SSL certificate provider for API traffic on May 1, 2020.”

“If you do not update to a compatible SDK by May 1, you may not be able to process payments through your Braintree account until you make the necessary update.”

I reckon this would need to be updated in the Braintree EDD Addon to reflect their API changes?

could you shed some light on this please?
thanks

SCA has been rolled out.

The Chargeback protection from Stripe is only available when using the new Stripe Checkout feature, which we haven’t yet finished. It’s still on our todo list but there’s not an immediate timeframe for it.

Chargebacks are really frustrating. We deal with them as well.

@Eric

We do plan to try and implement some support for it. The main reason for not just swapping out the Checkout from v1 to v2 is primarily because they just are not the same experience.

There are some limitations with the new checkout however, that affect our recurring payments addon. For instance, you cannot purchase multiple subscriptions at the same time via the new checkout interface, so that causes a major hurdle in using it.

Thanks for your answer. Now, we are working with the newest version. But, we made many “test-payments” with different cards from different banks and card holders , but no one had to authenticate. Is this normal? We tried with 6 different “German” bank cards which in other shops have to authenticate.

Thank for your answer. Now, we are working with the newest version. But, we made many “test-payments” with different cards from different banks and card holders , but no one had to authenticate. Is this normal? We tried with 6 different “German” bank cards which in other shops have to authenticate.

@james,

Thank you! The team at Sandhills really put in the work for all of our products. As far as 3.0, we’re going to re-assess now that we’re able to get back to EDD Core development. We pulled all resources to get this first SCA release out.

Hi Ramona,

I can fully respect your frustrations and feelings like this. We should have done a better job communicating our entire process with our customers, informing them of our progress on the integration. As with many regulatory things like SCA, the plans for it were set in motion nearly 2 years ago. It took quite a while for the gateways to be ready to support it, some of them are just not supporting it. We worked directly with Stripe as they were one of the more vocal and developer friendly platforms that reached out to use to help us get our SCA compliance working. We finally got the support for SCA with Stripe in June when they updated their PHP Library to fully support SCA.

Once we had the updates we got to work, and started building out what is the betas you are looking at now. It was very important that we not just get Stripe SCA compliant but our recurring gateway as well. Releasing one without the other would have been unhelpful to our customers.

We always have the interests of our customers at the forefront of the things we’re doing, which is why we tested this in our live sites first, to make sure we could catch any bugs and not have failed payments on our customers’ site, worked directly with Stripe for the last 5 months so that we could offer a reliable SCA transition, and committed to having both our Recurring Payments and Stripe integration ready by the deadline, instead of just releasing Stripe support.

The development team at Sandhills put in a lot of work on all the SCA releases for all our products and I’m extremely proud of what they have built and how easy the transition has been.

We fully intend to release the final update later today, so please check back shortly.

Hi Frank,

I understand your frustrations. I want to be clear, that we have been working on this for nearly a month and a half for EDD. For our other products as well. We’ve been working directly with Stripe on this to get not just our primary Stripe Gateway working, but also the recurring payments add-on, so that payments will continue to work after the September 14th deadline. I think it’s important to know that we’ve been in contact with Stripe for the last few months, working with their development team, understanding their new API and helping them improve their platform as well.

I’m sorry we’ve not been able to meet your satisfaction and apologize for not communicating with everyone earlier than the last two blog posts. Our primary goal was to have the continued support for Stripe SCA payments so our customer’s sites would not fail to meet the regulations, and that took time to get correct and working in a way we felt comfortable with it.

On 11. September you wrote you’re running this beta on your sites for nearly a week prior to launching the beta and afterwards you wrote that the update will be fully released by the time by the 14th.
Today is the 12. of September! I suppose I’m not the only one of your paying customers who runs an online shop with several thousand customers itself. Reading your post sounds like a bad joke. SCA has been known for 2 years, especially for you as a provider of online shop software. I can’t believe you to start beta testing only about one week and publishing an update one or two days before the final deadline. Why is that? Can I still assume that you are courageous in the interests of your customers?

When exactly will you provide the final update?

Kind regards, Ramona

Not happy in any kind.

Betatesting here. The upgrade routine triggers this error:

Warning: call_user_func_array() expects parameter 1 to be a valid callback, function ‘edd_upgrades_screen’ not found or invalid function name in /usr/home/web/wp-includes/class-wp-hook.php on line 286

I sent you an email, not sure if you prefer another channel to do this.

Hi Haptiq,

At this time it is a limitation/requirement to have the single field. While there are ways to create individual fields with Stripe Elements, for complexity and being sure we could hit the deadline for SCA in time, we focused on the default and suggested format from Stripe.

I will look into ways we can improve the customization of the fields in a future release.

Hey Marco,

The update will be fully released by the time by the 14th. We’ve been running this beta on our sites for nearly a week prior to launching the beta, in order to make sure things were working as expected.

As far as active subscriptions, they will not need to be re-processed with authentication, just new purchases.

Is this required by Stripe to only have the one card field in their checkout to be SCA compliant? Is this a technical requirement or is it possible to use individual cardNumber, cardExpiry, and cardCvc fields as well?

Fwiw: I’d prefer having individual fields, with clear labels – not just placeholders, that vanish, once the customer starts typing into the field.

Again, thanks for the update!