Use of this guide is no longer recommended if you’re based in Europe.
Starting in September 2019, a new regulation called Strong Customer
Authentication (SCA) will require businesses in Europe to request
additional authentication for online payments. We recommend using the
Payment Intents API instead of the Charges API to prepare for SCA.
Follow the Payment Intents API Quickstart to learn how to get started
with Elements using the Payment Intents API.
Is the code on Github using "Payment Intents API" or "Charges API"?
No problem. I've given the decision to my boss - use the current gateway and change to the (your?) new one by September, or give me the time to produce a new gateway.
If I do create a new gateway, I'd be happy to send it to you.
We will of course make sure that it will be done with plenty of time for people to make the upgrade so don't worry about that, but I do appreciate it would be better not to implement a solution to just swap it out a few weeks down the road.
I'm away on holiday from Thursday for a week so won't be deploying till I'm back, but if you wanted to test it in the meantime, I'd appreciate any feedback you had.
A big change in this is that a webhook registration is now a requirement and it's the webhook that is responsible for finalizing the transaction. There have been a couple of changes to the settings too so it's worth comparing those with the existing docs to see what's required.
Stripe gateway query
I am trying to add Stripe as a payment gateway and have seen the code on Github at https://github.com/TeaCommerce/Payment-Providers/blob/c859bcfe9830ada3dc52e3f9d4cec0632fd058c8/Source/TeaCommerce.PaymentProviders.UI/Views/StripePaymentForm.cshtml
In that code, there is a link to https://stripe.com/docs/stripe-js/elements/quickstart for more information.
On that page is this message:
Is the code on Github using "Payment Intents API" or "Charges API"?
Hi Gordon,
We are aware of these upcoming changes and will be looking at an update post Codegarden.
Annoyingly a lot of work went into updating the Stripe provider in the last release but these updates were only announced last month.
Oh, OK. Looks like I'll be making my own then.
Apologies if this isn't soon enough for your needs.
Unfortunately we don't get any warning about these things so all we can do is react and fit the work in as soon as possible.
If you do take a look at it before we do, it would be great if you could consider contributing a PR to the Payment Provider GitHub repository.
No problem. I've given the decision to my boss - use the current gateway and change to the (your?) new one by September, or give me the time to produce a new gateway.
If I do create a new gateway, I'd be happy to send it to you.
Awesome, thanks Gordon.
We will of course make sure that it will be done with plenty of time for people to make the upgrade so don't worry about that, but I do appreciate it would be better not to implement a solution to just swap it out a few weeks down the road.
And the decision is to use the current gateway - due to time constraints.
No problem. I'll update this thread once we've made the update.
Hey Gordon,
I've put together a PR for an updated Stripe provider you can find here:
https://github.com/TeaCommerce/Payment-Providers/pull/30
You can also review the updated docs on a preview site here:
https://deploy-preview-13--vibrant-easley-e6f6f9.netlify.com/3.3.1/payment-providers/stripe/
I'm away on holiday from Thursday for a week so won't be deploying till I'm back, but if you wanted to test it in the meantime, I'd appreciate any feedback you had.
A big change in this is that a webhook registration is now a requirement and it's the webhook that is responsible for finalizing the transaction. There have been a couple of changes to the settings too so it's worth comparing those with the existing docs to see what's required.
is working on a reply...