#dan_checkout-payment-intents
lone gulchBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1466531393906409747
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
desert sparrow
Hi 👋
The point of the checkout session is provide the UI where the customer confirms the associated payment intent. The only way to confirm a payment intent associated with a Checkout Session is through the Checkout UI.
worn belfry
Is there a way to revert the checkout session to run paymentintent.confirm in the event that we no longer want to make it a checkout session?
desert sparrow
No but the way you are framing these questions make it sounds like you are not using Checkout as we expect it to be used.
Can you take a couple steps back and describe how you wound up in this situation?
iron frost
We want to have a conditionally available checkout session - where users can choose to pay with card on file (NOT inside checkout)
And if they choose to avoid checkout session, and pay with default card on file, we want to cancel checkout session
If they don't pay with default card on file, then we route to checkout session
desert sparrow
Okay in that case you would need to create an entirely different Payment Intent to charge the card on file that is not related to the Checkout Session.
iron frost
bummer - our sql logic is all tied to the original payment_intent ID
is there any other option?
desert sparrow
You could defer creating the Checkout Session or Payment Intent until you know which one your customer wants
iron frost
but once checkout session is initialized, it locks payment_intent to be checkout session from that point forward?
desert sparrow
The checkout session creates the Payment intent itself.
iron frost
ahh gottcha
desert sparrow
That Payment Intent, created by the Checkout Session, cannot be used outside of that Checkout Session
The point of Stripe Checkout is to handle the creation/confirmation/capture of the Payment Intent along with creating the UI for the user
So, if you are using Checkout, you should not be directly interacting with those Payment Intents really until they are completed