boundaryboys04

[dreamy mauve]

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

• boundaryboys04, 2 days ago, 9 messages

[iron crypt]

Can you provide an example setupintent?

[upper pendant]

https://dashboard.stripe.com/events/evt_1On4jBEVZvhMCAQUGKd2tXIE

seti_1On4j8EVZvhMCAQUkrJrAb1t

[iron crypt]

Thanks looking

[upper pendant]

here is what we are doing in the backend,

var setupIntentService = new SetupIntentService();

            // Create Setup Intent
            var setupIntentOptions = new SetupIntentCreateOptions
            {
                Customer = customerId,
                PaymentMethod = paymentMethodId,
                PaymentMethodTypes = new List<string> { "card" },
                Usage = "off_session",
                Description = "Setup intent for customer: " + customerId
            };

            var setupIntent = await setupIntentService.CreateAsync(setupIntentOptions);


            // Confirm Setup Intent
            var confirmOptions = new SetupIntentConfirmOptions
            {
                PaymentMethod = paymentMethodId
            };

            var confirmedSetupIntent = await setupIntentService.ConfirmAsync(setupIntent.Id, confirmOptions);

[iron crypt]

Ah ok so synced with a colleague on this. SetupIntents don't always perform a real auth. Sometimes we don't reach out to the issuer (depending on various internal optimizations I can't share details about). So in those cases card checks (like cvc) won't be available since we didn't talk to the issuer.

[upper pendant]

do you see anything wrong with this logic and setupintent