#leo-setupintent-3ds
plucky void
tame stone
hi @tiny sandal!!! sorry about it, I pressed enter by mistake hehehe
let me send you the payloads
tiny sandal
sorry I didn't realize you were editing the question 😅
As long as you have done 3DS on the SetupIntent then when you create a confirm the PaymentIntent it will just work
if it doesn't it's likely because you use the wrong test card that always require 3DS
tame stone
ohhh got it
I used this ones:
4000002760003184
4000002500003155
4000000000003220
I basically got the same behaviour in all of them....
tiny sandal
Can you give me a concrete example of a PaymentIntent with 3155 where this happened?
tame stone
yes sure!!!
for PaymentIntentId pi_3Mio87IBMqTXbYso1UXw8lZ1
"status": "requires_action"
I'm sending these props:
urlencoded.append('amount', amount);
urlencoded.append('currency', currencyCode);
urlencoded.append('confirm', true);
urlencoded.append('customer', customer);
urlencoded.append('payment_method', payment_method);
urlencoded.append('capture_method', 'manual');
urlencoded.append('setup_future_usage', off_session);
urlencoded.append('return_url', siteURL);
tiny sandal
The PaymentMethod id is a src_123 which is a really old integration path. How did you end up with that if you're using SetupIntents properly?
tame stone
I'm working with an already existing integration... should I use the PaymentMethods API??
tiny sandal
I mean I don't know, that was the first thing that puzzled me because of the way you framed the original question
so yeah you have quite an old/backwards integration. Doesn't really make sense to use SetupIntent if you're already collected and attached the card to a customer with the legacy API
But ultimately: you forgot to pass off_session: true and 3155 only skips 3DS for new off session payments (which is what the docs explain)
tiny sandal
awesome!
tame stone
I removed the "setup_future_usage" and added the "off_session" one
tiny sandal
👍
tame stone
@tiny sandal thank you so much!!! have a great day!!