#50an6xy06r6n
1 messages · Page 1 of 1 (latest)
Just to make sure I'm covering my bases, have you read this? https://support.stripe.com/questions/collecting-ach-direct-debit-mandates-from-customers
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
And also the section titled "Mandates" here? https://stripe.com/docs/payments/ach-debit#mandates
Totally okay if you have, I just want to make sure we're on the same page before moving forward
yes I've read all of those
Okay, perfect. So, to clarify, the Payment Element doesn't actually show the mandate. You are responsible for displaying the mandate and collecting the required permissions from your end-users, then caching the mandate data (e.g. timestamp of acceptance, whether the end-user was online or offline, ip address of online acceptance [if applicable], etc.): https://stripe.com/docs/api/setup_intents/create#create_setup_intent-mandate_data
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
ah ok I didn't see that. It seemed to work in the sandbox without that for some reason
Stripe displays a mandate on the payment page for you if you use one of the following hosted products:
Checkout
Payment Element
Hosted Invoices Page
I think this is why I thought the Payment element was supposed to show the mandate
Ahhhh, okay. I may have overlooked something. I thought this was required ahead of rendering the Payment Element, as that is what my test integration does, though it may be out of date.
Can you link me to the doc you're looking at?
I think this is one of the ones you just sent me.
I will say that I didn't see any kind of mandate actually appear when I tested the flow. The API reference you sent makes sense, but I'm also not super clear on what the confirm=true flow looks like
Huh...
Let me test on my end, as I thought this had to be supplied ahead of time, so either I'm wrong or the docs are wrong. I'd like to know which, so I'll circle back in a few minutes
Okay, apologies for the wait, so here's what I found
You control what is displayed via the terms object when you create your Payment Element: https://stripe.com/docs/js/elements_object/create_payment_element#payment_element_create-options-terms
The default is to show the mandate text and we will collect the necessary mandate info automatically
It should look something like this:
The “terms” link links out to https://stripe.com/en-au/legal/ach-payments/authorization which contains the text about the mandate
Ah ok that's helpful
Do you have the power to get someone to update the documentation? Seems like there's quite a bit that's just sort of not documented about how this works
Wait also we're using the payment element for an offline setup intent, so the flow is a little different than shown in your screenshot
I can definitely add that feedback and look into updating the docs to make that known. If I'm also confused about it, then clearly something could be clarified better there
Ok last couple of questions:
- We're also cloning this bank account to a connected account, and I see this in the documentation pertaining to that case:
When collecting a bank account that you intend to clone to connected accounts, you must communicate to the customer that their authorization extends to connected accounts on your platform. For example, you can communicate this message to a customer through the mandate terms. Failure to communicate this message to your customers could result in customer confusion and increase the risk of disputed payments.
Does the default mandate cover this? The "merchant's affiliated entities" line seems to, but I want to be sure.
- The default mandate also has this clause:
You may amend or cancel this authorization at any time by providing notice to the Merchant with 30 (thirty) days notice prior to the scheduled debit.
This is just a standard part of an ACH mandate right? There's not actually any technical limitation on the Stripe side for the 30 days?
Does the default mandate cover this? The "merchant's affiliated entities" line seems to, but I want to be sure.
To my knowledge, that's covered via the terminology of the mandate the user accepts by default.
This is just a standard part of an ACH mandate right? There's not actually any technical limitation on the Stripe side for the 30 days?
Correct. That just says that they can provide notice to you that they want to essentially "un-accept" the mandate.
is there an actual flow for doing that beyond just deleting the payment method?
👋 stepping in as two-shoes needs to step away