emptyopen-ach

[warm mulch]

you pass source: 'tok_123' but that will not allow you to charge again after

And then on the Charge it would have details about the bank account in payment_method_details[ach_debit]

[cobalt relic]

sorry what do you mean by not being able to charge again? i would need to hit plaid's "stripe processor token" endpoint again to retrieve a new processor token value for each ACH charge request?

and regarding the webhooks, how do i link the charge to the subsequent webhooks?

[warm mulch]

yes if you do it this way.

Do you want to charge again? If so you need to first save the bank account on a customer. So you first call https://stripe.com/docs/api/customers/create and pass source: 'btok_123' and that will create a Bank Account ba_123 on the Customer and then you can charge that bank account when you need to

[warm mulch]

not sure I understand what that question means. The webhook would be about that specific charge you created, so you know its id for example since you just created it. Or you can put metadata on the charge on creation

Do you have a more specific question or context around your ask? Maybe you're brand new to Stripe, have never even done card payments and just jumping on ACH? Just getting a bit more details would help

[cobalt relic]

the company i work for (Fair.com) has definitely used stripe in the past - i was not involved with it, but we're creating a new product which in a way involves a simpler form of payment (one time payments, not subscription). we're looking to only support ACH transactions for now (since they are large value purchases).

in terms of webhooks, i just want to understand what the minimum info we need to store locally in order to interpret webhook events like ACH status update to "success" or "failure" for account/customer/xxx ID: 12345, and trace that back to our locally persisted Transaction

thanks for the info on creating a Customer, that sounds like the best way to do it. we may want to create multiple ACH charges per customer down the line

[graceful spear]

Hello! So you want to associate events delivered to your server with the transaction information on your end? Which specific event types are you asking about?

[cobalt relic]

yes, exactly. only ACH status update events at the moment

[graceful spear]

Which ones from this list specifically? https://stripe.com/docs/api/events/types#event_types

[graceful spear]

Are you still here? I'd love to help if you can tell me which specific events you're asking about!

[cobalt relic]

hi sorry, been juggling a few things today! i believe these would be the charge-related items, such as charge.failed and charge.succeeded. I believe we already capture these types of webhooks from stripe, actually. looking in the Stripe dashboard, I see some sandbox logs showing the webhooks and i also see our receipt of them. i think i'll be able to take a look at our legacy code for now to resolve any misunderstandings i have. thanks!

[graceful spear]

Happy to help! If you need anything else just let us know!