ebellotpu6

[carmine patio]

Is there a way to disable the verification on the confirmSetupIntent?

[delicate panther]

Generally you'd only use the Setup Intent in scenarios where there's no initial payment. If you're processing a payment immediately, or creating a Subscription then the Setup Intent is redundant and should be dropped.

[carmine patio]

No, my flux is:

1. Create setupIntent and add payment method and customer to it.
2. Sign a contract with another interface
3. Make the payment

This flux is mandatory for my Product Owner, so by now, the customer has to validate two times (steps 1 and 3). My question is if I could only verify on step 3?.

[delicate panther]

Can you share an example of how you're creating the Setup Intent and subsequent payments?

[carmine patio]

Setupintent:
`var service = new SetupIntentService();
var options = new SetupIntentCreateOptions
{
PaymentMethodTypes = new List<string> { "card" },
Customer = customerStripe.Customer.Id,
Metadata = new Dictionary<string, string>
{
{ "storageId", storageId },
},
PaymentMethodOptions = new SetupIntentPaymentMethodOptionsOptions
{
Card = new SetupIntentPaymentMethodOptionsCardOptions
{
RequestThreeDSecure = "any"
}
}
};

            var setupIntent = service.Create(options, null);`

PaymentIntent:
var paymentIntentService = new PaymentIntentService(); return paymentIntentService.Create(new PaymentIntentCreateOptions { Amount = request.Amount, Currency = "EUR", Customer = request.CustomerId, PaymentMethod = request.PaymentMethodId, Description = request.Description, Metadata = new Dictionary<string, string> { { "storageId", request.StorageId }, { "centerId", request.CenterId }, { "invoiceType", "deposit" } }, Confirm = true, OffSession = false, });

[hollow crow]

Hi! I'm taking over this thread.

Why do you need a SetupIntent here? Couldn't you directly create the PaymentIntent and use setup_future_usage to save the card for future usage?

Otherwise if you do SetupIntent + PaymentIntent, then yes it's possible that the bank will ask for 3DS 2 times in a row.

[carmine patio]

I don't now, all your teammates recommended me to use setupinent

Maybe because I have to create a subscription and a payment on the 3rd step?

[stone hare]

hey @carmine patio if you want we can pick up the conversation from yesterday

how may I help you?

[carmine patio]

I am working with off_session payments so I have to verify if the payment method requires 3DS Auth when I want to confirm the payment or subscription. I understand that this is necessary, but the problem is that when the customer fill the paymentElement with the card details, it is also required to verify the 3DS Auth, so in result, the customer have to verify 2 times the same payment method.

This is my flux:

1. Create setupIntent and add payment method and customer to it.
2. Sign a contract with another interface
3. Make the payment

This flux is mandatory for my Product Owner, so by now, the customer has to validate two times (steps 1 and 3). My question is if I could only verify on step 3?.

[stone hare]

yes as we discussed yesterday there's no workaround the 2 validations if you want to implement this path

[carmine patio]

okey

[stone hare]

it's unfortunate I agree, but again you need to know that this is not always required

and if it is you don't have any other option

[carmine patio]

I take this opportunity to thank you, the confirmcardpayment method has worked correctly

[stone hare]

let me know if you need any more help