#Vitaly-ACH-PaymentMethods

1 messages · Page 1 of 1 (latest)

ornate hedge
vital scroll
#

I think we already got such access, and we add all applicable headers for beta, but the response from Inbound Transfer request (parameters: payment method, financial account, ...) is the following:
"Only verified bank accounts can be used as a payment_method. Please create a new verified PaymentMethod and try again."

#

so the main question is how to get an instantly verified account for PaymentMethod?

#

If not via Plaid

#

Or how else to create Inbound Transfer, if without Payment Method.
Thank you in advance!

ornate hedge
#

You will need to be logged into your Stripe account to access that doc

#

There are guides there both for collecting bank account details ahead of time and for accepting a payment when you collect bank details.

vital scroll
#

I see the documentation

#

So this is compatible with Treasury API, and we can use it to transfer money to a Financial Account?

ornate hedge
#

Ah sorry, I misunderstood and thought you were interested in ACH Debit for your customers.

#

Can you provide the request ID for the above error message?

vital scroll
#

np

#

1 sec

#

req_MpWkfyPloYE5Bb

ornate hedge
#

Thanks, give me a sec

vital scroll
#

It says

#

To reuse a bank account for future payments, it must be attached to a Customer.

#

We dont have Customer object, we use Connect Account

#

will it work without Customer?

ornate hedge
#

My understanding is yes. Sorry I have yet to test out this beta flow myself. Give me a moment to confirm

vital scroll
#

sure, thanks for your help

ornate hedge
#

Can you try testing using pm_usBankAccount as the origin_payment_method and send me the request ID?

vital scroll
#

1 sec

ornate hedge
#

Ah sorry I missed it in the doc

vital scroll
#

req_vfPUt3Qz8toGLa

ornate hedge
#

You just need to set attach_to_self: true

#

And exclude the Customer object

#

For the SetupIntent

#

That will attach the PaymentMethod to the Connected Account

#

As opposed to using a Customer

vital scroll
#

pm_usBankAccount worked, I have received my test 1$ in the expected financial (treasury) account

#

cool!!!

#

so, maybe we can somehow avoid using SetupIntent ?

#

🙂

#

we already implemented so much of Plaid client side

ornate hedge
#

No, sorry, you set attach_to_self: true on the SetupIntent creation request.

vital scroll
#

now we will need to re-implement it using Stripe client side

ornate hedge
#

You can't use Plaid with PaymentMethods.

vital scroll
#

how, in general, PaymentMethod should be created, to get it verified instantly?

#

without Plaid

#

or there is no such way

ornate hedge
#

The SetupIntent handles the verification. Instant verification will always be attempted but sometimes a fallback to micro-deposits will be necessary.

vital scroll
#

for the SetupIntent we need to re-implement all our bank selection logic, which was done using Plaid, so it is a bit more than was planned

ornate hedge
#

Yes I'm sorry that you were under the impression you could use Plaid with Treasury. It was never built that way.

vital scroll
#

i see

#

thanks for your help, it was fast

#

will see our next steps

ornate hedge
#

Let us know if we can help any further!

vital scroll
#

sure

#

what exactly is expected in this field of PaymentMethod?

#

us_bank_account.linked_account