#riptired_api

1 messages · Page 1 of 1 (latest)

snow sapphireBOT
#

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

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

radiant wasp
#

Hi 👋

Do you have an example Account ID I could review?

verbal imp
#

Yes: acct_1Pku0NRZQRYNbqJa

radiant wasp
#

Thanks, taking a look

#

Okay in this case the recipient agreement has to be full, which is the default if not specified. Accounts with recipient agreements cannot accept payments themselves.

verbal imp
#

So that means the account is fine as is?

radiant wasp
#

The account is fine but it won't work for the cross border payouts, since the Canadian connect accounts need to have a recipient service agreement.

verbal imp
#

I need to be able to pay them out so is that something I can change for their existing connected account or do they have to setup a new connected account

radiant wasp
#

That would require new Connect Accounts. This is why I recommended building the entire scenario in code in Test mode.

verbal imp
#

Ah okay -- I was using stripe hosted connected account onboarding to have the clients setup their connected accounts

#

Is it feasible to have them select a recipient service agreement through the hosted onboarding?

radiant wasp
#

No

#

That is because of what the recipient service agreement means.

A recipient service agreement clarifies that there is no service relationship between Stripe and the recipient, and that the recipient’s relationship is with the platform. Connected accounts under the recipient service agreement can’t process payments or request the card_payments capability.

#

Essentially Connected Accounts with the recipient service agreement have practically no interaction with Stripe ever

#

Everything goes through the Platform account

snow sapphireBOT
verbal imp
#

Got it, okay let me test this real quick

# 
stripe.Account.create(
    email="XXXX@gmail.com",
    controller={
        "fees": {"payer": "application"},
        "losses": {"payments": "application"},
        "stripe_dashboard": {"type": "express"},
    },
    country="CA",
    capabilities={"transfers": {"requested": True}},
    tos_acceptance={"service_agreement": "recipient"},
)
# 
stripe.AccountLink.create(
    account=XXXX,
    return_url="https://example.com/return",
    refresh_url="https://example.com/refresh",
    type="account_onboarding",
)
#

So basically I just need to go back and configure the connect accounts for them via API, create the links for them via API and then have them onboard again

north magnet
#

Hi there 👋 taking over, as my colleague needs to step away

You can't change an existing service agreement, so you would need to reonboard them to net-new accounts and just delete/reject the old accounts with the old service agreement

verbal imp
#

Yup, the above snippets would be the correct configuration for this kind of service agreement needed to do the cross border payout right

north magnet
#

Yup!

verbal imp
#

okay got it, is there anything else I need to be aware of for cross border payments if they are now a recipient level stripe connected account?

north magnet
#

Not that I can think of right now that's not already covered in this thread. Do run tests for all the different workflows you intend to use with them though, obviously

verbal imp
#

got it