#zperkins_ach-mandate-collection
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/1498800858345767127
đ 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.
- zperkins_ach-refund, 5 days ago, 5 messages
Hi there,
I am a bit confused, the doc you shared is about ACH payment using Checkout Session not about creating a Payment Method using the Payment Element
However, when you confirm the PaymentIntent server-side, Stripe cannot automatically capture the mandate acceptance metadata (IP address, user-agent) on your behalf the way stripe.confirmUsBankAccountPayment() does client-side.
If you confirm server side, you would need to add mandate_data to your Payment Intent confirmation request https://docs.stripe.com/api/payment_intents/confirm#confirm_payment_intent-mandate_data
yeah, sorry, I was trying to link to the closest thing, there wasn't anything super exact for my scenario.
So, with regards to that, it's my understanding that if the bank comes back with a Request for Authorization, it would be up to us to provide evidence in that case, since we collected the mandate. Is that correct?
Yes, and since you collected the mandate data and not Stripe, Stripe might open a dispute while when you handle the mandate collection through Stripe client side (i.e Payment Element) Stripe will handle this for you.
A helpful guide for you might be this: https://docs.stripe.com/payments/accept-a-payment-deferred?platform=web&type=setup
This guide here might be even more helpful: https://docs.stripe.com/payments/finalize-payments-on-the-server?platform=web&type=setup
gotcha, yes, these are helpful
I think the easiest thing for us might just be to move things around so we can confirm our payment intent from the front end
since we're not really using this for future use, just grabbing it to immediately make a payment
But just to go down this path slightly more, do you know if there are any docs on what exact evidence is needed if a Request for Authorization comes through?
Yes, if there are no additional steps that you need for your business, then simply confirming client side is the most striaghtforward and hustlefree approach
Let me check about evidence docs
https://docs.stripe.com/payments/ach-direct-debit#requests-for-proof-of-authorization i think might be it, only thing I'm maybe missing is what the content of the authorization document may be
Yes, that's what I meant with "Stripe will handle the dispute" for you when you use Stripe for the mandate collection.
We also have this dispute best practices guide: https://docs.stripe.com/disputes/best-practices
Yes, I was just thinking down the path of if we were to collect the mandate ourselves
alright, thank you
I think I have what I need now, appreciate it
No worries. We are always happy to help.