#david2_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1309608899959324824
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- david2_best-practices, 5 hours ago, 4 messages
- david2_api, 1 day ago, 15 messages
- david2_webhooks, 3 days ago, 20 messages
Hi, taking a look at the request id now.
I think the problem is that you've created a payment method and then passing that payment method to create a SetupIntent: https://dashboard.stripe.com/test/logs/req_DW3m703KRAektQ with usage: "off_session",. So when you pass the mandate on that payment intent confirmation call, it would not work, https://dashboard.stripe.com/test/logs/req_qmoSVPvnxxh9u8. As you can see on the response of the SetupIntent creation, the mandate is already created.
If you're looking to save payment method details during the payment, you can use this integration https://docs.stripe.com/payments/save-during-payment. The current integration you have is not efficient. You seem to be creating the payment intent. Then, creating the SetupIntent using that payment method, and finally creating the charge.
so, this went through by providing mandate_data
evt_3QO2arAQbHn4ElzT1quuLgPS
Why is that? I was under the impression that the mandate from the setupIntent is the one I wanted to use, rather than having to create a "new" mandate at paymentIntent confirmation time.
Looking
Can you confirm which integration path you're following? Are you using this, https://docs.stripe.com/payments/accept-a-payment-synchronously?platform=web#create-payment-intent?
I'm not sure what to call it, but the gist is:
- create a paymentIntent
- Collect payment method (ACH bank account)
- Show the user a mandate, create a setupIntent
- A week later (or whatever per business rules), confirm the charge using that setupIntent and mandate.