#latwelve-stripejs-sca

1 messages · Page 1 of 1 (latest)

static parrot
#

hello, are you only calling createPaymentMethod() ? that alone doesn't trigger SCA

limpid canopy
#

yep!

#

Is there any need to trigger 3d secure?

#

It just feels a bit weird having a payment method on file in their booking system that may or may not fail with their automatic payments

#

I don't really want to run a paymentIntent or anything like that but if theres something I can query to help ensure the paymentMethod is solid that'd be good

static parrot
#

I don't really want to run a paymentIntent or anything like that but if theres something I can query to help ensure the paymentMethod is solid that'd be good
so there is a misunderstanding here, let me ask some calrify

#

is your goal to charge the customer now? or days later?

#

also up front, you have to use SetupIntents or PaymentIntents to "set up" a card for SCA
so you cannot really avoid that, those are the two main ways to prompt customer authentication

limpid canopy
#

So my side is - pass a 3rd party booking system ONLY a paymentMethod and then the booking system is setup to take automatic payments at certain intervals ie 20% deposit.. then 80% 28 days before a booking etc.. so there isn't anything for me to put in as a paymentIntent

#

Hmm weird - so if I was to create a paymentmethod and pass it to them - theres a high chance it wont work because the customers not verified it fully with stripe?

#

I may have misunderstood what they've said but I dont think so

#

I've just sent them an email to qualify what they've said. Taking the first payment seems more sensible so maybe I have just misunderstood but the way they've worded it is like that :/

static parrot
#

sure I can explain

createPaymentMethod() does nothing related to SCA, juust creates a PaymentMethod out of card details

you need to create a SetupIntent, then confirm it client-side with a Stripe "card" Element

This process "sets up" the card for future charges, so it obtains customer authentication right now, and tries to avail them as exemptions for future payments

so your (or the plugins) creates future charges on that "set up" PaymentMethod

limpid canopy
#

Ok I think that makes sense - I'm familiar with PaymentIntents but not so much with SetupIntents -

so do I just use a card Element with SetupIntent and get rid of the createPaymentMethod? because the SetupIntent can return a payment mthod ID and I don't need to define any monetary values now?

#

Sorry just reading the docs

static parrot
#

correct, SetupIntent is just like a PaymentIntent, just that it moves no funds, creates no paymetn

limpid canopy
#

So element card -> PaymentMethod -> setupIntent

static parrot
#

it just prompts customer for authentication, and to use those up front authentications for exemptions

#

So element card -> PaymentMethod -> setupIntent
technically no

limpid canopy
#

Oops 😄

static parrot
limpid canopy
#

awesome - thank you

static parrot
#

1/ create SetupIntent server-side
2/ confirm client-side with confirmCardSetup()

#

so just 2 steps really

limpid canopy
#

Dreamy - thanks so much - sorry for the dumb qs!