Strong Customer Authentication and Additional Info
OneMoreRound82 opened this issue · 3 comments
Does this adhere to the new SCA rule that is in effect of Septemeber 2019?
Is there a way to attach other details sent with the token such as name, address, receipt email?
Yes, provided your backend/frontend supports it, and yes, check out the Stripe docs for createToken
as linked in this project's Readme.
Yes, although I think that you should replace createToken()
use, with handleCardSetup()
.
Also, if in the past your FE application did register and charge in the same step, at this point, it must be separated.
- Register your customer (and BE should provide you the response with
clientSecret
) - Let the customer enter card details... On submit, call
handleCardSetup
- In
handleCardSetup
response, call your BE endpoint for successful or error of subscription
The entire billing logic must be changed.
This is my understanding, correct me if I'm wrong?
Can we still register and charge in a single step?
EDIT:
After some further research and reading, I found this link:
https://stripe.com/docs/payments/payment-methods#transitioning
So yeah, as I described above, you now need to approach payments differently. Not sure if it can be done in one step, or it must be from two steps.
In one of Stripe demo's for recurring payments (subscriptions) I have seen that it's done from a single step.
Hey folks, closing this. confirmCardSetup
is available in v1.0.0