#mike_paymentintent-sfu
drifting dewBOT
👋 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/1227259928985473127
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
finite sealBOT
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.
- mike-j_webhooks, 1 day ago, 6 messages
primal raven
What you describe doesn't match the example your shared, which is a payment that needs a payment method: https://dashboard.stripe.com/test/logs/req_15goqFsFniDyuO
For the shape of the problem you describe though, you need to ensure you have attached a payment method to a customer before using it for payment the first time
If you can share how you initially set up & store your payment method, I may be able to offer guidance
Or a specific example of the error you described
ashen hearth
Ah, I've got that many windows open, I may have grabbed the wrong one. Let me check what I've got going on...
Ok, that one I sent was when the PI is created. This is the one when the customer has gone through the motions with the webelement to pay, and the PI success is returned to us. It contains the payment method, and the customer id. evt_3P3c5KJk75hPCxYy0ZTBpSa7.
ashen stream
Hi @ashen hearth apologies for the delay. My teammate needed to step away, I'm catching up and will take a look at that Event.
It looks like that happens because the Payment Intent you used did not use the setup_future_usage parameter to prepare the Payment Method for future usage. You'll want to set that parameter based on how you plan to charge those Payment Methods in the future, whether the customer will be on_session or off_session for those payments.
tardy steppe
mike_paymentintent-sfu
👋 Taking over as the server is quite busy and I'm next on shift! Let me know if you have more questions about this @ashen hearth
ashen hearth
Hello all. No problem. I shall double check that value, though I thought I'd already set it as off_session. I'll re-ceck it tomorrow - thanks!