#Juls
daring stream
hybrid juncoBOT
silk warren
Hi 👋 that looks like a server side request that is being made to create a Source for a Customer, since the request is coming from your server there isn't a surface for us to raise the authentication challenge to the end-customer so the authentication cannot be completed.
Is this a new integration that you're working on building?
daring stream
No. It is the usual
As far as I know, when we add the CC, a setup intent should be created. Then, we would retrieve the client secret, pass it to the Stripe JS functions, then we start the SCA Challenge
But here, no Setup Intent is created
silk warren
Agreed, I'm not seeing a Setup Intent being used here. Do you have multiple flows available to your customers, where not all of them use Setup Intents?
daring stream
No we have only one flow.
First, we add the Payment Method to the customer as default_source
Second, we update the subscription default source with the Id
silk warren
Then I would recommend reviewing your flow and try to identify why it didn't make a request to create a Setup Intent for this. Or are you relying on a Setup Intent being created by an automatic process of some sort?
daring stream
We rely on the setup intent being created automatically
Would it be advisable to create it ourselves?
The Setup Intent is always created when we change the subscription default source
silk warren
Where are you expecting the Setup Intent to have been created for this occurrence? Oh, I see, when updating the Subscription. Where is the Subscription update request for this one, did that not return the Setup Intent you were expecting to use?
daring stream
We expect it to be created as well when we add the default source to the customer.
In this case, the flow failed when adding the CC to the customer
silk warren
Updating a Customer is not expected to generate a Setup Intent
daring stream
Let me check 👀 . It is what we usually do
So, sorry if I mislead you.
We always update the customer default source first. We don't expect problems there.
After that, when we update the subscription source, and the setup intent happens.
The problem here:
After adding the customer source with the token id, the card directly failed. We could not update the subscription source because we had no Card Id returned
The problem is the card failing when being added to the customer source... is this expected? I just tried in test environment a 3DS card, and it was added to the customer without problem
silk warren
Card validations are performed when a card source is attached to a Customer, if the issuing bank requires an authentication challenge to be completed at that point then it is expected for the attachment to fail since there is not a way for the end-customer to complete an authentication challenge at that point.
I would recommend you consider revising your flow to use Setup Intents from the start, so these authentications can be handled in the confirmation step of those intent's lifecycle while the Customer is on-session to complete any authentication challenges:
https://stripe.com/docs/payments/save-and-reuse?platform=web&ui=elements
