#minaturecookie-sca
1 messages · Page 1 of 1 (latest)
@zenith gull
how can I best prevent authentication failures at that later date?
just follow our recommended integration so that you use a SetupIntent at the time of saving the card to allow 3D Secure to be run, and then mark the payment at that later date asoff_session:trueso it can claim an exemption. https://stripe.com/docs/payments/save-and-reuse
imply that authentication can cause off-session PaymentIntent creation to fail,
not sure I follow what that means — I mean to be clear, yes the off-session payment might require authentication, and you need to be able to handle that outcome. https://stripe.com/ie/guides/strong-customer-authentication#what-happens-if-an-exemption-fails But hopefully it won't happen too often if you integrate the way described, but it is up to the issuing bank at the end of the day.
Yes there's no concept of a single use-mandate. If your future payment was guaranteed to be within 7 days you could may be use auth-and-capture instead(https://stripe.com/docs/payments/capture-later) , but otherwise, SI + PI yep.
what % of PaymentIntent creations can we expect to fail, as a UK/EU average, due to authentication being required off-session?
I don't have that information I'm afraid
is there anything we can do to minimise the authentication required here?
you just integrate per the docs link above and you have the best chance of not requiring auth, by default
Thanks for the speedy response!
what % of PaymentIntent creations can we expect to fail, as a UK/EU average, due to authentication being required off-session?
I don't have that information I'm afraid
Fair enough. Do you know ball-park? Are we looking at 1%? 50%? 99%?
Do you know if it's possible to get that figure, or how we might go about trying to estimate that figure?
I don't know the ballbark no
we might go about trying to estimate that figure?
it's easy enough to work out by instrumenting your live integration since you know when an off-session payment gets declined withauthentication_required. I'm sure we track all this ourselves and have stats but it's not something I'm privy to or can share unfortunately
Unfortunately we're developing this new future-payment method for a ballot we're running in January. All of our current payments are immediate charges. So we wouldn't be able to gather the data ourselves until the ballot closes at the end of January, at which point it will be too late!
Is there possibly a colleague you could ask who might have access to the authentication_required stats on Stripe's side?
there is not
you can contact https://support.stripe.com/email and ask/escalate! I don't know if we're in a position to share this kind of information though.