Using Connect with Custom connected accounts

A Custom connected account is almost completely invisible to the account holder. You, the platform, are responsible for all interactions with your connected accounts and for collecting all the information needed to verify each account.

With Custom connected accounts, you can modify the connected account’s details and settings through the API, including managing their bank accounts and payout schedule. Because Custom connected account holders can’t log in to Stripe, it’s up to you to build the onboarding flow, connected account dashboard, reporting functionality, and communication channels.

Creating a Custom connected account involves the following steps:

1. Make sure you meet the minimum requirements.
2. Properly identify the country and any related requirements.
3. Create the account.
4. Complete the identity verification process.

Requirements for creating Custom connected accounts

To use Custom connected accounts, you must meet all of these requirements:

• Minimum API version: You must be using an API version at least as recent as 2014-12-17. You can view and upgrade your API version in the Dashboard if needed.
• Terms of Service update: Creating Custom connected accounts requires an update to your terms of service, because it must include a reference to Stripe’s services agreement. Stripe recommends that you consult your lawyers on whether you should update your terms acceptance language to include reference to Stripe’s terms.
• Handling information requests: Instead of requesting information – such as a Social Security Number or passport scan – directly from your connected account user, Stripe requests the information it needs from you. You must collect that information from your connected account and provide it to Stripe. Otherwise, Stripe might disable payouts to the connected account.
• Platform in a supported country: Platforms in Australia, Austria, Belgium, Brazil, Bulgaria, Canada, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hong Kong, Hungary, India, Ireland, Italy, Japan, Latvia, Lithuania, Luxembourg, Malta, Mexico, the Netherlands, New Zealand, Norway, Poland, Portugal, Romania, Singapore, Slovakia, Slovenia, Spain, Sweden, Switzerland, Thailand, the United Kingdom, and the United States can create Custom accounts for any country Stripe supports. Contact us to be notified when platforms in your country can use Custom connected accounts.
• Countries that don’t support self-serve: Due to restrictions that apply when using Connect in the United Arab Emirates, India, and Thailand, platform users in these countries can’t self-serve Custom connected accounts. To begin onboarding for Custom connected accounts in these countries, contact us.
• Platforms in the UAE: Platforms in the UAE can only use Custom connected accounts based in the UAE with the following charge types: destination_charges and separate charges and transfers. Destination charges using the on_behalf_of attribute are not yet supported for UAE platforms.

• Vetting for fraud: Because your platform is responsible for losses incurred by Custom connected accounts, you must scrutinise all accounts that sign up via your platform for potential fraud. Refer to our risk management best practices guide for more information.

Note that there’s an additional cost for active Custom connected accounts. A Custom connected account is considered active if it has received at least one successful payout in a given month.

curl https://api.stripe.com/v1/accounts \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d country=US \
  -d type=custom \
  -d "capabilities[card_payments][requested]"=true \
  -d "capabilities[transfers][requested]"=true

{
  ...
  "id": 
"{{CONNECTED_ACCOUNT_ID}}",
  "type": "custom"
  ...
}

Webhooks

After an account is created, all notifications about changes to the account are sent to your webhooks as account.updated events. Provide your Connect webhook URL in your account settings and then watch for these events and respond to them as needed.