#cargodev_unexpected
misty nymphBOT
👋 Welcome to your new thread!
⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime!
🔗 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/1212058476738646097
📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.
⏲️ 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. Thank you for your patience!
north kestrelBOT
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.
digital ore
Hi 👋 you can't. You wouldn't use a Checkout Session there, as those are intended for customer interaction which it sounds like you won't have because you're charging a saved payment method.
Instead you would directly create the object that you want the Checkout Session to create, likely either a Payment Intent or Subscription, and provide the ID of the saved Payment Method when doing so.
brazen iron
If we generate a payment Intent generally, can that then be applied to create a checkout session?
digital ore
No
brazen iron
We want to create a single payment_intent that can be used by BOTH:
- Checkout-session
- Saved card on file
digital ore
That's not possible
brazen iron
Are there any work arounds or is it possible to do that in the future?
Why is that functionality restricted?
digital ore
Because they serve two very different purposes. Checkout Sessions are meant for direct user interaction, whereas Payment Intents are not that rigid and can be used for either custom frontend integrations using our Elements or being used to charge already saved payment methods.
For what you're describing, you would need to start by determining whether you plan to allow your customers to provide new payment method details (create a Checkout Session for them) or charge an existing Payment Method (create a Payment Intent).
I don't think I've heard of plans to change that.
brazen iron
We want to give our users the choice of how to checkout (either saved card, or new checkout session) --> possibly emailed to a 3rd party (trucker) to execute transaction
We want both to link to same underlying payment_intent
payment_intent_id in our backend links to a bunch of critcial corresponding data
and want the payment_intnet_success webhook to trigger the data linked to same payment_intent_id
and either method sets payment_intent as completed
so we don't have 2 outstanding
digital ore
Then it sounds like you need to offer the choice to your customer at the beginning of your flow before you create any objects, and then only generate one object to work with, either a Checkout Session or a Payment Intent depending on what the customer selected.
brazen iron
Ugh okay, thanks for feedback.
There's no change to update this in the future correct?
digital ore
Not that I'm aware of.