jack_best-practices

[verbal ether]

👋 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/1506865539941929080

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

⛔️ Stripe developers have stepped away for a short while

Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.

[hazy dune]

Full description ^

[vital flare]

Hi! Give me a moment to catch up!

I understand your main requirements are:

• Platform: US
• Connected accounts: Canada
• Fund flow: Separate charges and transfers

Can I check if you only want to create connected accounts in Canada or do you plan to create a connected account in other countries as well?

[vital flare]

1. For a non-US connected account that will only receive transfers and pay out to its local bank (never charge customers), is requesting configuration.merchant + card_payments the only supported path, purely to obtain the merchant config / stripe_balance.payouts + the Full SA?

• If the connected account is in Canada, you meet the requirements for CONNECT PAYOUTS as part of the cross -border payouts (https://docs.stripe.com/connect/cross-border-payouts). This means that full service agreement is needed for your connected accounts.
• Connected accounts under the full service agreement can process card payments which means that card_payments capability is required (https://docs.stripe.com/connect/service-agreement-types?connect-account-creation-pattern=typeless#full). This capability is only available via the merchant configuration.
• Due to this you need to include both recipient and merchant configurations when creating the connected account.
• And as our docs (https://docs.stripe.com/connect/service-agreement-types?connect-account-creation-pattern=typeless#choosing-type) mention, if you pass both these configurations, full service agreement will be automatically chosen.

2. With Accounts v2 + Stripe-hosted onboarding, how do I opt a recipient account into the Full Service Agreement (vs. the Recipient Service Agreement) so cross-border payouts work — or is that exactly what adding the merchant configuration does, and there's no other lever?

Can I check why do you need this? Have you create an Accounts v2 connected account with recipient configuration only?

3. Since Retrieve Account v2 doesn't expose the accepted service-agreement type, how can I verify which SA a connected account is on?

For this you will need to use GET /v1/accounts/{connected_account_id} (https://docs.stripe.com/api/accounts/retrieve) to get the service-agreement type.

[hazy dune]

Hey Sam thanks for taking a look.

I'll be creating connected accounts in the US and CA (and other EEA countries).

Yeah I've created connected accounts using the Accounts v2 API with only the recipients config, which is all that I need (these accounts are not going to be taking payments directly), but it didn't work when I tried to set the country to CA I got that error I mentioned in the note.

I was hoping there was a way to still only use the recipients config for all accounts, and opt them into the Full Service Agreement somehow.

And when I call this endoint: GET /v1/accounts/{connected_account_id}
I only get the date the terms were accepted, not the type

[vital flare]

Yeah I've created connected accounts using the Accounts v2 API with only the recipients config, which is all that I need (these accounts are not going to be taking payments directly), but it didn't work when I tried to set the country to CA I got that error I mentioned in the note.

Do you have the request ID so I can take a look?

[hazy dune]

Here's a sandbox account in the workbench

[vital flare]

I was hoping there was a way to still only use the recipients config for all accounts, and opt them into the Full Service Agreement somehow.

Is there a reason why you need them to have Full Service Agreement?

And when I call this endoint: GET /v1/accounts/{connected_account_id}
I only get the date the terms were accepted, not the type

Give me a moment to check on this.

[hazy dune]

Is there a reason why you need them to have Full Service Agreement?
It's required for cross border payouts:
https://docs.stripe.com/connect/cross-border-payouts#limitations

Also here's a request ID trying to create an account with only the recipients config, in CA, and it failing: req_v2WN1O2wWLhoYBDIu

[vital flare]

There are 2 ways to do this.

Method 1: Global Payouts
If the countries you wish to create connected accounts in are in the list here (https://docs.stripe.com/global-payouts/recipient-creation-options#requirements), you can use Global Payouts and create connected accounts with recipient configuration only.

Method 2: Connect Payout
If Global Payouts don't meet your needs, you have to create connected accounts with both recipient and merchant configurations based on what I mentioned earlier.

[vital flare]

Yes, this is expected based on what we discussed. If you request for stripe_balance.stripe_transfers.requested: true, you will need both recipient and merchantconfigurations. But if you only want recipient configuration, you will need to use Global Payouts.

[vital flare]

Regarding this, it is correct that the service agreement type is not provided for Accounts V2 because this is determined based on the configuration of the connected account you create.

[hazy dune]

So there’s no other way to accept the Full Service Agreement? It just seemed odd that I would need to add the merchant configuration when I’m not going to be needing any of that functionality

[vital flare]

Is there a reason why you are not using Global Payouts since you don't need the merchant configuration?

[hazy dune]

Global Payouts is much more work to use, this is from the docs:

Manage your own legal and compliance requirements. This might require a Money Transmitter license if you manage your customers’ funds.

So I want to use Connect Payouts so Stripe is still responsible for the legal and compliance requirements

And part of my confusion is that I was able to create an account with just the recipient configuration but based in the US, and it worked fine, here's a request ID for that: req_v2aKTvH3K07DFVomj

^ So that was the same request payload as the prior request I shared, just with country = "CA" instead of "US"

And reading this doc page made it apparent this was something you could explicitly choose between using the v1 API, whereas for v2 there's no way to control it (unless there's some other way?): https://docs.stripe.com/connect/service-agreement-types#choosing-type

So yeah, just confused why there's no explicit mention in the docs why the merchant config must be used when creating an account cross borders 🤷‍♂️

[vital flare]

Sorry still looking into this. Give me a moment.

[hazy dune]

All good, thanks for your time!

[vital flare]

Thanks for waiting! Looks like this is how it is at the moment and I don't have full context on it. I will need to check on this internally and get back to you via a ticket. I will drop you a note on how to create a ticket shortly.

[vital flare]

I will check on this as well and update you via the ticket.

[verbal ether]

Hello @hazy dune, we have sent you a direct message, please check it at https://discord.com/channels/@me/1506904387786768427

• 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.

[hazy dune]

Got it, thank you @vital flare! Will I be reached out to via email or back here?

[vital flare]

We will reach back to you via email.

[hazy dune]

Sounds good, thanks 👍