Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Developer tools
Get started
Payments
Finance automation
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Overview
Get started with Connect
    How Connect works
    Design an integration
    Migrate to account controller properties
    Compare SaaS platform configurations for Accounts v1 and Accounts v2
    Upcoming requirements updates
    Onboarding Quickstart
Integration fundamentals
Example integrations
Onboard accounts
Configure account Dashboards
Accept payments
Pay out to accounts
Manage your Connect platform
Tax forms for your Connect platform
Work with connected account types
HomePlatforms and marketplacesGet started with Connect

Upcoming requirements updates

Learn about the changes to required verification information and how this impacts your integration with Stripe.

Copy page

Payments regulations aim to create a safer, more secure financial ecosystem by helping prevent crimes such as money laundering, fraud, and tax evasion. Financial regulators around the world enforce Know Your Customer (KYC) requirements to make sure that identity information is collected, verified, and maintained from certain types of businesses, and for any individuals who ultimately own, control, or direct the business. These requirements are frequently updated by financial service regulators, card networks, and other financial institutions.

This guide provides an overview of the upcoming changes, and highlights the most significant changes. For the exhaustive list of requirements, refer to Required verification information.

To change how you integrate with Stripe, see Onboarding solutions for Custom accounts.

Last updated: January 4, 2023

What’s changing

  • Required information collected from connected accounts: We’re updating the information we require from sole proprietorships, non-profits and single-member LLCs and simplifying how we obtain legal guardian consent for accounts opened by minors. In addition, an email for the account representative is now required for all legal entity types, and a change for government entities and public companies.
  • How we verify business information and provide new detailed verification responses: We’re updating our criteria for valid business information and introducing new verification error codes when we unable to accept or verify information provided.
  • Threshold at which we verify tax identification numbers (TINs): For Custom and Express connected accounts, we’re lowering the payments volume threshold at which we verify TINs to align with current federal tax reporting thresholds.
  • How we prefill statement descriptors and statement descriptor prefixes: If a statement descriptor isn’t provided, the prefill logic has changed to use either the business profile name, the business URL, or the legal entity name of the connected account.

These changes will affect all users with a requested card_payments capability in the US.

Required information collected from connected accounts

New information collected and new fields added to the API:

  • Businesses that are company.structure of sole_proprietorship and single_member_llc, must provide their business address (“company address”). In the event that the business address is the same as the representative’s personal address, your connected accounts can provide the same values for both.
  • Legal entities that are company.structure of government_instrumentality, tax_exempt_government_instrumentality, governmental_unit, public_company, and public_corporation, public_partnership must provide an email for the account representative. This requirement now applies to all legal entity types.
  • To simplify how we obtain a legal guardian’s consent for accounts opened by minors, the Persons API has been updated with a new relationship type of legal_guardian as well as an additional_tos_acceptances field to record the legal guardian’s agreement to the Stripe Terms of Service. If the account representative’s date of birth indicates the individual is a minor, then an account requirement is triggered to add a legal_guardian before the account can be activated.

How we verify business information and provide new detailed verification responses

Updates to the information we already collect

We’ll request the following information from your connected accounts:

FieldUpdated requirementsAdditional considerations
SSN or ITIN collected from US-resident Representatives (Reps)Last 4 digits required at onboarding for all account types (including Custom and Express connected accounts)This is the current behavior for Standard connected accounts
SSN or ITIN collected from US-resident Representatives (Reps)If the last 4 digits fail to verify at onboarding, Reps will need to provide the full 9 digits at onboarding
SSN or ITIN collected from US-resident Representatives (Reps) or OwnersFull 9 digits required once payments volume exceeds $500KA Representative (Rep) is defined as a person with significant responsibility to control, manage, or direct the organization; and is authorized by the organization to agree to Stripe’s terms. For a representative, the full 9 digits are required at $500K only if no Owners are listed on the account.

New verification error codes

When we’re unable to verify information provided by your connected accounts, we’ll surface detailed verification responses as new error codes in the requirements.errors array. View docs.

Synchronous errors

FieldNew error codeError message
Product Descriptioninvalid_product_description_lengthYour product description must be at least 10 characters.
Product Descriptioninvalid_product_description_url_matchYour product description must be different from your URL.
(Full) Statement Descriptorinvalid_statement_descriptor_lengthYour statement descriptor must be between 5 and 22 characters.
(Full) Statement Descriptorinvalid_statement_descriptor_business_mismatchYour statement descriptor must be similar to your business name, legal entity name, or URL.
(Full) Statement Descriptorinvalid_statement_descriptor_denylistedGeneric or well-known statement descriptors aren’t supported.
(Short) Statement Descriptorinvalid_statement_descriptor_prefix_mismatchThe statement descriptor prefix must be similar to your statement descriptor, business name, legal entity name, or URL.
(Short) Statement Descriptorinvalid_statement_descriptor_prefix_denylistedGeneric or well-known statement descriptor prefixes aren’t supported.
LE Business Nameinvalid_company_name_denylistedGeneric or well-known business names aren’t supported.
Business Profile Name (DBA)invalid_business_profile_name_denylistedGeneric or well-known business names aren’t supported.
Business Profile Name (DBA)invalid_business_profile_nameBusiness profile names must consist of recognizable words.
Persons DOBinvalid_dob_age_under_minimumPerson must be at least 13 years old.
Persons DOBinvalid_dob_age_over_maximumDate of birth must be within in the last 120 years.
Persons phoneinvalid_phone_numberThe phone number doesn’t seem to be valid. Make sure it’s formatted correctly.
LE Business Phoneinvalid_phone_numberThe phone number doesn’t seem to be valid. Make sure it’s formatted correctly.
Company TaxIDinvalid_tax_id_formatTax IDs must be a unique set of 9 numbers without dashes or other special characters.
URLinvalid_url_formatFormat as https://example.com
URLinvalid_url_denylistedGeneric business URLs aren’t supported.

Asynchronous errors

FieldNew error codeError message
URLinvalid_url_website_inaccessibleThis URL couldn’t be reached. Make sure it’s available and entered correctly or provide another.
URLinvalid_url_website_business_information_mismatchThe business information on your website must match the details you provided to Stripe.
URLinvalid_url_website_incompleteYour website seems to be missing some required information. Learn about website requirements
URLinvalid_url_website_otherWe weren’t able to verify your business using the URL you provided. Make sure it’s entered correctly or provide another URL.
URLinvalid_url_web_presence_detectedBecause you use a website, app, social media page, or online profile to sell products or services, you must provide a URL for your business.

Update to the threshold at which we verify tax identification numbers (TINs)

To align with the IRS reporting thresholds for Forms 1099-K, 1099-NEC, and 1099-MISC, we’re updating the threshold at which we verify the TIN to when your payments volume reaches $600 or within 30 days of first charge, whichever comes first.

How we prefill statement descriptors and statement descriptor prefixes

If not provided, the statement descriptor is prefilled using the following supplied fields (in this order): business_profile.name (“doing business as”), business_profile.url, the legal entity name (either individual.first_name + individual.last_name or company.name)`. In addition, if the statement descriptor prefix isn’t provided, it’s prefilled from the first 10 characters of the statement descriptor.

See also

  • Connect onboarding for Custom accounts
  • Onboarding solutions for Custom accounts
  • Required verification information
  • Updating accounts
  • Handling identity verification with the API
  • Testing Custom account identity verification
  • Accepted verification documents
Was this page helpful?
YesNo
Need help? Contact Support.
Join our early access program.
Check out our changelog.
Questions? Contact Sales.
LLM? Read llms.txt.
Powered by Markdoc