#vilesa - PaymentIntent

1 messages · Page 1 of 1 (latest)

viscid escarp
#

Hi there!

brisk cairn
#

yes I have seen that but it does not answer my question

viscid escarp
#

We do our 3DS flow through stripe mobile SDK, but we never used this parameter.
Can you clarify how you are integrating with Stripe currently?

brisk cairn
#

payment intent created by python backend
if 3DS : 3DS done through mobile SDK

unreal wind
#

Hi there. Stepping in here. What are you still confused about related to that parameter?

#

Are you using manual confirmation?

brisk cairn
#

what do you mean by "manual confirmation" ?

#

my questions are:

  • what's the default value for 'use_stripe_sdk'?
  • if the default value is False, then what does this 'use_stripe_sdk' attribute do? because I am not using it but still am able to run 3DS flows on mobile SDK
unreal wind
#

Likely you don't need to set that to true with your integration

#

It's not a common integration pattern. That setting is there just to provide the option

brisk cairn
#

so by manual confirmation you mean "confirm=False" ?

unreal wind
#

No it's really referring to finalizing card payments on the server (like in the above link)

brisk cairn
#

ok
what's the default value for "use_stripe_sdk" please?

unreal wind
#

False. Like I mentioned, manual confirmation isn't a common integration pattern. Only pass True if you're using that pattern, but it isn't likely that you are

brisk cairn
#

ok

#

I don't understand the docs: what does it mean to finalize a payment on the server when the payment requires a user 3DS step? how can we have a server side step after that?

unreal wind
#

3ds is still client side even if confirming server side

brisk cairn
#

ok i see thank you

unreal wind
#

No problem!

#

I don't recommend finalizing the payment on the server unless you have to though

#

We consider it a legacy flow