Arvind hariharan

[pearl patio]

Hi on Stripe ACH direct Debit, needed some information on how do we store Mandate information which is accepted by user on our backend database

[main sand]

So you existing ACH mandates collected with another processor, and what to use them with Stripe?

[pearl patio]

No i am asking how do we collect the mandate information once user accepts it. Is there any mandate ID we get in any API response?

[main sand]

Depends on how you're integrating. Are you using a Payment Intent, Setup Intent? Checkout? Elements?

[pearl patio]

Payment intent

[main sand]

Not sure if that's directly available via a Payment Intent. Why do you need to store that?

[pearl patio]

Is it not necessary to store the mandate information for future purpose? We just need to show the form and ask the user to accept it thats it?

[main sand]

The mandate data is associated to the generated Payment Method, if anything you should just store that pm_xxx ID as that is what you'll use to charge the same ACH details going forward

[pearl patio]

Give you give any doc links related to this or any sample API response where we can see this mandate data associated with payment method

[main sand]

Well there's a Mandate object that's created: https://stripe.com/docs/api/mandates

But it's not associated with any payment objects, just a Setup Intent directly: https://stripe.com/docs/api/setup_intents/object#setup_intent_object-mandate

[pearl patio]

Ok so how do we use this for ACH since it deals by creating payment Intent right?

I mean do we need to create a new mandate and store it by associating it with payment method

[main sand]

Well, you don't need to. That's the point I'm trying to make. The mandate stuff just shouldn't be a concern for merchants – Stripe takes care of that

[main sand]

No, the Payment Element takes care of creating the mandate: https://stripe.com/docs/payments/ach-debit/accept-a-payment?platform=web&ui=API#web-collect-mandate-and-submit

[pearl patio]

Okay so we just show the Mandate form HTML in the front end right. Dont need to store or handle it from our backend side.

[main sand]

Exactly

[pearl patio]

okay fine thanks

And one more query

For Micro deposits verification, we need to have our own form right where user will input his bank details etc in the payment page. The stripe.collectbankAccountInfo will not work in this case correct?

[main sand]

There's a self-hosted URL you can use, or you can build your own form and use verifyMicrodepositsForPayment

See: https://stripe.com/docs/payments/ach-debit/accept-a-payment?platform=web&ui=API#web-verify-with-microdeposits

[pearl patio]

I am asking about stripe.collectBankAccountForPayment

Is this valid before Micro deposit verification as well

?

Or do we need to use our own form

To collect the bank details

[main sand]

Yes, you'd still use collectBankAccountForPayment to initialise the collection of bank details. If the verification doesn't happen immediately at that point, via Financial Connections, then you'd use the microdeposit verification flow I shared

[pearl patio]

okay

So in both Cases instant verification and micro deposits verification , after creating a payment intent we call this collectBankAccountForPayment

[main sand]

Yes, as explained by the guide