#ali-i_canada-us-bank-accounts

1 messages · Page 1 of 1 (latest)

rain sentinelBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1368983772934176879

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

vagrant dagger
#

Also we do not recomend this approach when attempting to save bank accounts for future use.

#

We have an integration guide for exactly this situation here

boreal roost
#

req_iQiHAX8T9KO0jO please let me know if this is correct. claude is telling me this error is fine i should ignore it and micro deposit charge should happen in a few days. i think claude is wrong

#

for this We have an integration guide for exactly this situation here will this work for my connected platform account registered in canada for US users?

vagrant dagger
#

Genearlly all LLMS have been spectacularly wrong about Stripe APIs

#

will this work for my connected platform account registered in canada for US users?

How are you creating objects?

#

The request you shared is not a Connect Request

boreal roost
#

What a time to be alive to even have llms. a true gift. has gotten a lot right for me. have made a lot with stripe and llm just have not gotten traction but one day

vagrant dagger
#

Do you plan on having Us customers purchasing directly from your CA-domiciled account?

boreal roost
#

no we have users send moeny to each other. no purchases. but users should be able to send money to us and canadian users with this method. i know might have cross border limitations but atleast same country should work. canada works but us fails for microdeposit

#

getting the answe for this give me a sec How are you creating objects?

#

I'm creating objects directly on my platform account using the regular Stripe API endpoints. For example, I'm creating customers and payment methods on the platform, then using those to create payment intents with transfer_data to move money to the connected accounts. I'm not using the Stripe-Account header approach for these operations.
I'm doing this because my platform is registered in Canada, but I need to support both Canadian (ACSS) and US (ACH) customers. Since Financial Connections isn't available for Canadian platforms, I'm using microdeposits for US users. Is this approach problematic? Should I be structuring my API calls differently?

vagrant dagger
#

Okay US customers can save us_bank_account payment methods with Canada based merchants and you can use the guide I shared to use microdeposits instead of financial connections. we document how to set this up here

boreal roost
#

I'm creating Stripe objects directly on my platform account (registered in Canada), then using the transfer_data parameter to move money to connected accounts. I'm not using the Stripe-Account header approach because I'm handling payment methods on the platform side.
The reason I'm using microdeposits for US customers is because my platform is registered in Canada, and Financial Connections isn't available for Canadian platforms serving US customers. I'm aware of the documentation you shared, but I'm unsure if that approach will work given my platform's location constraint.
My specific questions are:

Will the approach in the docs you shared work for my Canadian platform with US customers, or do I need to keep using microdeposits?
Is my current implementation (creating PaymentMethod objects on the platform and using transfer_data) the correct approach for a Connected account scenario like mine?
Are there any specific changes I should make to improve my current implementation?

vagrant dagger
#

Sorry this just seems like copy/paste text without any review of the doc I shared

#

Can you please review the document I shared and ask questions specific to that?

boreal roost
#

you are absolutely right. this docs answers my question and looks very promising. i will implement it and only reach back out if i am blocked

#

Thank you. tbh great company and even better support. this discord server is awesome. can't wait for you guys to ipo

vagrant dagger
#

Thanks! We like being able to unblock developers in real time and keep everyone's integrations working 🙂