#leedurrant-test-off-session-SCA
mystic hamlet
Hello 👋
Let me take a look
So you're saying, you didn't setup 4000002500003155 for off_session usage but it still worked?
vapid ibex
That's correct. I added the card manually via the portal, as that way it doesn't perform any 3DS. Then I synched my app (bringing the card details in against the customer), and created an off_session payment intent using my existing functionality.
mystic hamlet
can you share the example PaymentIntent ID?
vapid ibex
pi_3LLqC6L4KF1uRfCk0dGCQL86
mystic hamlet
I wonder if customer portal sets it up for future usage by default
It is highly likely that it would since that's one of the perks of the customer portal.
vapid ibex
In a previous thread it was suggested that that wasn't the case, and the card is just tokenised.
mystic hamlet
ah interesting. Can you try using the API instead of the customer portal to see if that changes anything?
vapid ibex
I have a customer that is using my app not by design so as to save on Microsoft licensing costs. They are adding the card via the Stripe portal, and the payments are failing as not authorised. So I am trying to add some additonal code, but cant get it to a state that I can replicate with Test Data.
I did try adding a card using my app (hence using the api) and the same thing happened.
The manually created card is showing as being setup for future use via a seti_123 number, but that was unexpected.
I need to be able to have a card that always needs 3DS for an off_session payment
mystic hamlet
have you tried this?
4000000000003220