#ishu22g-confirmation-api
1 messages · Page 1 of 1 (latest)
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.
- ishu22g, 10 hours ago, 59 messages
- ishu-test-cards, 13 hours ago, 11 messages
- ishu22g-future-payments, 3 days ago, 30 messages
1/ ideally, the step to confirm the PaymentIntent is done client-side by the customer. But have you tried calling the confirm endpoint?
https://stripe.com/docs/api/payment_intents/confirm
2/ You could create the PaymentIntent with confirm: true parameter. That way you're telling stripe to confirm the payment if it moves to requires_confirmation status
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
@dapper warren , I am not using paymentIntent, but setupIntent instead
Ah I see then you'd use this instead for 1/
https://stripe.com/docs/api/setup_intents/confirm
Let me check
ishu22g-confirmation-api
👍
I see
Now #1, i.e., test flow works
I am calling /confirm endpoint after creating setupIntent
So ideally, in order for #2 flow, i.e., end user/production flow to work,
Once end user submits their payment/card information using Stripe Elements form. I will send a request to the same endpoint to setupIntent flow to be completed. Correct?
Are you using the defer intent flow? If so, yeah.
https://stripe.com/docs/payments/accept-a-payment-deferred
I think what I am using is more similar to this https://stripe.com/docs/payments/save-and-reuse
Will the logic that I mentioned still work?
I believe so