#bops-setupintent-sca
errant sequoia
ripe iron
the reason i ask is because we maintain a "master" set of payment methods attached to a customer in our US stripe account. the US account's payment method is cloned to respective country stripe accounts (UK/Canada/etc) at the point of actual first use in that country.
creating a new payment method for the US, attaching it to the customer, and using the payment method in the US can be done with just 1 SCA interaction by creating the PaymentMethod and then using PaymentIntent's setup_future_usage.
is it possible to create a new payment method, attach it in the US, clone the payment method to the other country's Stripe account, and use the payment method with just 1 SCA interaction?
thank you
hoary granite
is it possible for a SetupIntent with usage set to on_session to trigger SCA?
yep, it might require 3D Secure, any use of a SetupIntent might.
For the other question, if you're doing the flow where you save the card on a platform first and then do the payment on a connected account that could I suppose be two 3D Secure uses(one for the SetupIntent on the platform, and another for the PaymentIntent on the connected account), it's possible. The SetupIntent on the platform won't have much impact on the connected account payment getting exemptions since from the bank's perspective that first authentication was a different merchant.
Not sure I have a better answer there.
Do you know the connected account you're going to use for the payment at the time of saving the card? that might simplify things.
ripe iron
yeah, so i guess the solution would be to rework our notion of a "master" stripe account with all the payment methods. we have this in place so that we can query for all payment methods for a particular customer in 1 query in the US stripe account.
do you guys have a recommendation for our use case? essentially, we want the user to be able to see all their payment methods so that they can use their US credit card in the UK and vice versa. should we just store these in our own database?
hoary granite
I think the way you're doing it(the master customer on a platform account and then cloning cards to the relevant connected accounts makes sense) so I don't really have any other recommendation unfortunately
ripe iron
right, that was what stripe recommended to us in the very beginning I believe. so we'll have to accept 2 SCAs in the worst case.