#franco_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/1392217924005269504
đ 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.
- franco_api, 3 hours ago, 3 messages
Hello
Are you trying to create a mandate for the existing payment method OR just have the customers save a new payment method?
Sorry to close it before.
For this customer, we have a previusly working payment method with successful payments (PM_1), then it fails after multiple billings.
Then, to try to fix it, the user fill again the payment method (PM_2) (Same fingerprint), but the mandate fails for the payment intent
What we can do? What is the correct approach? An also, is there any change for the incomplete or pending payments (With the PM that has an invalid payment) to unlock?
Because we try to send the invoice again, and we don't want to charge them double
How are they adding these new payment methods?
For the PM_1 is on a proposal acceptance, that is when we create our payment intent.
The second one, we try to update it through the same way, but without accept a new proposal, so setting it through a new payment intent
Looks like you use SetupIntents to save these payment methods first and then charge them off-session using PaymentIntents?
Yes
Sorry, the incomplete payment, have the PM_1 too
The PM_1 was the one working fine, and then the mandate fails.
And the PM_2 is the new one, and seems to be working
Is there any change that the incomplete payment because of the mandate fails?
We don't want to duplicate the charge for the user
If the payment unlocks at any time
One option is to
1/ Create a new SetupIntent for the existing Payment Method
https://docs.stripe.com/api/setup_intents/create#create_setup_intent-payment_method
2/ Pass the mandate_data + confirm: true in the same request
https://docs.stripe.com/api/setup_intents/create#create_setup_intent-mandate_data
https://docs.stripe.com/api/setup_intents/create#create_setup_intent-confirm
That should generate a new mandate for the existing payment method
without needing to create a new payment method
Thanks!
I will check that
The new payment method should work for the payment intents right?
The mandate is correct
Correct