#mdcopley08

1 messages · Page 1 of 1 (latest)

opal iglooBOT
icy hamlet
#

ok so just to recap (to fully understand)

1/ Airbnb will be pushing funds to an ACH Credit Transfer virtual bank account? And those funds you want to land in the connected account's Balance? (and then move to the Platform)

cause if so, I think you want to think of this differently. Waiting for you to confirm

hazy fjord
#

Yes, I'm confirming that is how we were thinking about it

icy hamlet
#

ok yeah so the approach would need to be re-structured

You as a Platform would need to create an ACH CT Source for Airbnb (e.g. they are your "Customer" in Stripe terms)

they pay that ACH CT virtual bank account -> your Platform Balance increases by $X

then your Platform transfers $(X-application_fee) to the connected accounts

#

so you reverse where the funds settle first

hazy fjord
#

Okay thank you, we were thinking through that originally but were trying to figure out how to tell which connected account we'd have to transfer the funds to based on the webhook event we receive from Stripe

From Airbnb's documentation, they say they send the "payout_id" as a unique id sent to the bank, would this information be available in the webhook data?

unknown.png
icy hamlet
#

looking

icy hamlet
#

can Airbnb pay out to different bank accounts? or only to one?

hazy fjord
#

Let me check on this real quick

onyx valve
#

👋 hmunoz had to head out, but give me a minute to catch up

hazy fjord
#

Okay no worries, thanks for the update

onyx valve
#

The reason we asked about the multiple bank accounts is that ideally, you'd create a separate customer + ACH CT source for each connected account you'd need to potentially pay out to

hazy fjord
#

That would be great! Is it possible to generate ACH CT for connected accounts?

onyx valve
#

It would be what hmunoz described earlier - you create a Customer + ACH CT source on your platform account (one customer +source pair for each of your connected accounts). So you're not actually generating an ACH CT source for the connected accuonts directly, you're creating customers+source on the platform that "represent" each of the connected accounts (and you'll need to keep track of which platform customer + source are tied to which connected accounts)

hazy fjord
#

Okay thanks - and when an ACH transfer goes to the Customer on our Platform account, are you saying we would just catch the webhook for when it happens, see which customer it's connected to, and then do a Transfer API call to the appropriate connected account?

#

And then last question - just circling back on the bank transfer info that gets sent to us in the webhook - will it contain any info from the ACH transfer, i.e. Memo or Merchant name that its being sent from?

onyx valve
#

Okay thanks - and when an ACH transfer goes to the Customer on our Platform account, are you saying we would just catch the webhook for when it happens, see which customer it's connected to, and then do a Transfer API call to the appropriate connected account?
Yup! That's right 🙂

And for generating the Customer + ACH CT Pairs, we'd first create an ACH CT, then attach it to a customer using this API call? https://stripe.com/docs/api/sources/attach
Yup!

#

And then last question - just circling back on the bank transfer info that gets sent to us in the webhook - will it contain any info from the ACH transfer, i.e. Memo or Merchant name that its being sent from?
I believe we try and populate some of this on the Source Transaction in customer_data, but it'll depend on what info airbnb is setting

hazy fjord
#

Okay great, this has been really helpful!

onyx valve
#

👍