Treasury connected account onboarding guide

When a Connect platform uses Stripe Treasury to offer financial services to its connected accounts, the account onboarding process must consider fraud prevention and regulatory compliance. For example, financial services providers must employ Know Your Customer (KYC) and Know Your Business (KYB) client data collection and verification procedures. Use this guide to implement a Treasury onboarding process for your connected accounts.

KYC and KYB onboarding

Before you launch your embedded finance capabilities, implement an onboarding flow that collects the necessary KYC and KYB information from your connected accounts. The US Treasury Financial Crimes Enforcement Network (FinCEN) sets and enforces the legal requirements for customer due diligence, which each financial institution or partner can supplement with additional requirements.

When onboarding connected accounts to Treasury, Stripe only presents your platform with the core business compliance requirements. Your platform is responsible for collecting the required KYC and KYB information during onboarding and passing it to Stripe. The specific process depends on the type of onboarding flow you implement. Stripe then performs checks to determine if the connected accounts meet KYC and KYB requirements and to flag potential risks of money laundering or fraud. Those checks include:

• Verifying ID documents using public and private databases
• Checking application information against databases of known fraudulent actors and criminals (such as known terrorists and money launderers)
• Validating addresses
• Verifying that an application is from a registered business with the appropriate licences

Required information from your connected accounts

To open a Treasury financial account for a connected account, you must collect information including, but not limited to:

• Business name
• Legal entity type
• Tax ID number
• Merchant category code (MCC)
• Company name
• Company address
• Information about company owners, including:
  • SSN
  • Date of birth
  • Title
  • Ownership percentage

To review the full requirements for opening a financial account associated with a connected account, see Required verification information.

Ways to onboard connected accounts to Treasury

You can onboard your connected accounts onto Connect and Treasury using Stripe-hosted, embedded, or API onboarding.

Benefits of Stripe-hosted onboarding include:

• You don’t need to design or build a custom onboarding UI. Stripe provides a customisable web form that collects the required identity information from your connected accounts.
• Stripe-hosted onboarding dynamically adjusts input fields depending on account capabilities, product usage, country, and business type.
• You can use Stripe-hosted onboarding if you need support for mobile browsers, accessibility, and localisation.
• Stripe-hosted onboarding allows you to automatically collect all currently required information up front or incrementally, depending on what’s needed (see onboarding flows). To use Stripe Treasury products, connected accounts must provide all information to satisfy KYC requirements up front.

Benefits of embedded onboarding include:

• A themeable onboarding UI with limited Stripe branding. It’s similar to Stripe-hosted onboarding, but your connected accounts interact with the embedded component without leaving your application.
• Like Stripe-hosted onboarding, you get a customised and native onboarding flow, without the complexity and maintenance associated with updating your onboarding integration as compliance requirements change.

Benefits of API onboarding (custom onboarding) include:

• It gives you full control over the onboarding UI and process.
• You don’t need to redirect connected account holders to an external Stripe-hosted page.
• You can design the information collection flow for your connected accounts.

Keep up with changing requirements

Changing requirements can necessitate gathering additional information from connected accounts. Although hosted onboarding dynamically updates to reflect new requirements, platforms using API onboarding need to make sure they update their UI and collect this information. If a connected account has already onboarded using hosted onboarding and the requirements change, you can forward them the hosted onboarding link. Clicking it prompts them to provide the new required information. You can obtain new requirements for accounts using the methods detailed in the Required verification information guide.

You can also use a mixture of hosted and API onboarding. If you use hosted onboarding but have already collected some information from a different source, you can pass that information to Stripe through the identity verification process and pre-fill the hosted onboarding page with the provided information. In that case, the connected account can modify or verify the information within the Stripe-hosted UI.

Tips for onboarding

To make sure onboarding is successful and boost conversion for your Treasury product, keep the following tips in mind:

• Consider onboarding connected accounts to the treasury capability to start, even if you don’t plan to create a Treasury financial account until later. If you decide to perform Treasury onboarding later, prevent friction by setting clear expectations during onboarding that additional information might be required to use all aspects of the product.

• If you already have a Connect integration, or have otherwise collected identifying information from your connected accounts, you can use the API to pass data you already have. Doing so reduces the amount of information a connected account needs to provide through hosted onboarding.

• For issued cards, provide the card use case to help cardholders understand how it works.

• If a connected account has recently incorporated their business, they might not have their TIN entered in the IRS database yet. In that case, their TIN might come back as unverified until the IRS database updates. The account is still usable, and Stripe periodically attempts to reverify the TIN.

• Hosted onboarding allows you to test out your integration. If you want more customisation, you can switch to custom onboarding.

• Only onboard connected accounts that Stripe and Treasury can support. Review the Treasury requirements for supportability, and follow the guidelines on marketing Treasury to users.

• Offering incentives to onboard, such as a free subscription period or incentive funds, can help boost activation and engagement.