Required verification information

Learn what required verification information you need to collect for each country when using Connect.

Onboarding Custom accounts to a Connect platform requires that you collect certain information for each account (which Stripe verifies). Factors such as the capabilities you want to activate and the country the account is based in determine the information you need to collect. Use Connect Onboarding for Custom accounts for collecting the required information from users.

If you’re onboarding Express or Standard accounts, you don’t need to collect information because Stripe does it for you. But you can review what information is being collected from your users on this page.

Verification requirements differ based on:

The country connected accounts are created in.
The capabilities connected accounts requested.
The business type (for example, individual, company) and structure (for example, public corporation, private partnership).
The service agreement type the connected accounts are under.

As an added convenience, most arguments in the tables below are followed by a localized version, suitable as a label in your user interface.

Loading a table of required verification information

Processing live charges and receiving payouts

In the UAE, company documents such as the Trade License and Proof of Bank Account as well as relevant identity documents must be verified before a connected account can start processing live charges and receiving payouts. For all businesses except sole establishments and free zone establishments, the Memorandum of Association must be verified as well.

Uploading identity documents

For the company representative, beneficial owner(s) and executive(s), we require the following identity documents for verification:

Passport: all individuals
Emirates ID: UAE nationals & UAE residents
Residence visa: foreign nationals who are resident in the UAE

The Emirates ID can be provided in the parameter called verification.document. Passport(s) and residence visa(s) should be provided under a separate parameter called documents.

Keeping up to date with expired verification documents

In the UAE, Stripe is required to keep up to date with a company’s Trade License in addition to the primary identity document of the company’s representative, beneficial owners and executives. The primary identity document is either the Emirates ID for UAE nationals and residents, otherwise it is an individual’s Passport. Companies will have up to 28 days after the expiry date of these documents to provide an updated version. Expired documents will appear under company requirements or individual requirements and marked as currently due for two weeks before capabilities become disabled.

Ultimate Beneficial Owners

Stripe is required to verify all the beneficial owners of a business. These are the individuals who own 25% or more of the primary business. If a holding company has 25% or more ownership of the business, then the Memorandum of Association of this holding company as well that of the primary business must be uploaded. These documents must show the person(s) where relationship.owner is set to true.

Additional information on the company representative

This connected account needs to be activated by a person, known as the company representative, with significant responsibility to control, manage, or direct the organization and is authorized by the organization to agree to Stripe’s terms. The representative must either be an owner or an executive, which you specify by setting relationship.owner to true or relationship.executive to true. For a sole establishment or free zone establishment, the account must be activated by the owner of the business.

VAT Information

Stripe does not charge UAE VAT on Stripe fees to customers located in the UAE, where a valid UAE VAT ID has been provided. Local UAE VAT self-assessment obligations may be triggered upon receipt of a monthly invoice from Stripe. Stripe does charge UAE VAT at 5% on Stripe fees to customers located in the UAE, where a valid UAE VAT ID has not been provided.

Power of Attorney

If the company representative does not appear on the company’s Trade License or the Memorandum of Association, then you must upload a Power of Attorney that shows that the company representative has the authority to act on behalf of the company or a notarized letter of authorization.

Supported business structures

In the UAE, the only possible business type is company and the following business structures are accepted:

sole_establishment
free_zone_establishment
llc
free_zone_llc

Additional information on the account

If Stripe is unable to verify the company or if there are possible concerns about sanctions, you need to collect a proof-of-entity document to enable payouts. Collect this with the company.verification.document.front and company.verification.document.back arguments.

Additional information on the individual

Depending on the situation, you might need to collect a scan of an ID document to enable payouts if Stripe is unable to verify the individual or if there are possible concerns about sanctions.

Collect ID information with the individual.verification.document.front and individual.verification.document.back arguments.

Additional information on the representative

A person known as a representative must activate this connected account. This person must be a beneficial owner who is authorized to sign for the company. Indicate this relationship to Stripe by setting relationship.executive to true, or relationship.owner to true if the representative owns 25% or more of the company.

Depending on the situation, you might need to collect a scan of an ID document to enable payouts if Stripe is unable to verify the representative or if there are possible concerns about sanctions. Collect ID information with the verification.document.front and verification.document.back arguments.

Optionally, you can collect the representative’s ownership information with relationship.representative and relationship.percent_ownership.

Additional information on directors

For companies (excluding partnerships), information on all directors must be collected. Directors are members of the governing board of the company. When you have finished collecting the required information from all directors or if your company does not have any directors, you need to set company.directors_provided to true. This lets Stripe know that you have completed this requirement.

If there are possible concerns about sanctions, you need to collect a scan of an ID document to enable payouts. Collect ID information with the verification.document.front and verification.document.back arguments.

Additional information on beneficial owners (for both executives and owners)

Information on all beneficial owners must be collected. Beneficial owners are persons who exercise significant management control over the company (executives) or who own 25% or more of the company (owners). When you have finished collecting the required information from all beneficial owners, you need to set both company.owners_provided and company.executives_provided to true. This lets Stripe know that you have completed this requirement.

Depending on the situation, you might need to collect a scan of an ID document to enable payouts if Stripe is unable to verify a beneficial owner or if there are possible concerns about sanctions. Collect ID information with the verification.document.front and verification.document.back arguments.

Optionally, you can collect ownership information on each person who owns 25% or more of the company with relationship.owner and relationship.percent_ownership.

Additional information on the account

Additional information on the representative

If Stripe is unable to verify the representative, you need to provide either the Social Insurance Number (SIN) or a scan of an ID document. To collect the SIN, use the representative.id_number argument. To collect an ID document, use the verification.document.front and verification.document.back arguments.

Additional information on the individual

If Stripe is unable to verify the individual, you need to provide either the Social Insurance Number (SIN) or a scan of an ID document. To collect the SIN, use the individual.id_number argument. To collect an ID document, use the individual.verification.document.front and individual.verification.document.back arguments.

Universal Beneficial Ownership Verification

After supplying the beneficial owner information, it is checked against the National Registry of Businesses (NRB). Depending on the results of this check, there are three outcomes:

The business is found in the NRB, and the information matches. The account is fully onboarded, and no additional action is required.
The business is found in the NRB, but the information doesn’t match. The account is fully onboarded, and no additional action is required. A discrepancy report is sent to the NRB.
The business isn’t found in the NRB. An attestation consisting of an IP address, date, and user agent of the person submitting the information must be provided. The person is attesting that the business is registered with the NRB, and the information given to Stripe matches.

In the case where the business isn’t found in the NRB, attesting that the beneficial ownership information is complete and correct is accomplished by providing the company.ownership_declaration.date and company.ownership_declaration.ip arguments.

curl https://api.stripe.com/v1/accounts/{{CONNECTED_STRIPE_ACCOUNT_ID}} \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc: \
  -d "company[ownership_declaration][date]"=1609798905 \
  -d "company[ownership_declaration][ip]"="8.8.8.8" \
  -d "company[ownership_declaration][user_agent]"="Mozilla/5.0"

Universal Beneficial Ownership Verification

After supplying the beneficial owner information, it is checked against the National Registry of Businesses (NRB). Depending on the results of this check, there are three outcomes:

The business is found in the NRB, and the information matches. The account is fully onboarded, and no additional action is required.
The business is found in the NRB, but the information doesn’t match. The account is fully onboarded, and no additional action is required. A discrepancy report is sent to the NRB.
The business isn’t found in the NRB. An attestation consisting of an IP address, date, and user agent of the person submitting the information must be provided. The person is attesting that the business is registered with the NRB, and the information given to Stripe matches.

curl https://api.stripe.com/v1/accounts/{{CONNECTED_STRIPE_ACCOUNT_ID}} \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc: \
  -d "company[ownership_declaration][date]"=1609798905 \
  -d "company[ownership_declaration][ip]"="8.8.8.8" \
  -d "company[ownership_declaration][user_agent]"="Mozilla/5.0"

Additional information on the account

Additional information on the individual

Depending on the situation, you might need to collect a scan of an ID document, an address document, or both to enable payouts if Stripe can’t verify the individual or if there are possible concerns about sanctions. In some cases, depending on various calculated risk factors, Stripe may be able to use Simplified Due Diligence and request only one document for verification at a later point in time.

These thresholds may change, but currently that point in time might be either 2,500 EUR processing threshold or six months of activity, whichever comes first.

Collect ID information with the individual.verification.document.front and individual.verification.document.back arguments, and address information with verification.additional_document.front and verification.additional_document.back.

Additional information on the representative

You might need to collect a scan of an ID document and an address document to enable payouts, if Stripe can’t verify the representative’s provided information or if there are possible concerns about sanctions. In some cases, depending on various calculated risk factors, Stripe may be able to use Simplified Due Diligence and request only one document for verification at a later point in time.

Additionally, for partnerships you need to provide a relationship.percent_ownership value.

These thresholds may change, but currently that point in time might be either 2,500 EUR processing threshold or six months of activity, whichever comes first.

You can collect ID information with the verification.document.front and verification.document.back arguments.

Additional information on directors

You might need to collect a scan of an ID document and an address document to enable payouts, if Stripe can’t verify the director’s provided information or if there are possible concerns about sanctions. In some cases, depending on various calculated risk factors, Stripe may be able to use Simplified Due Diligence and request only one document for verification at a later point in time.

These thresholds may change, but currently that point in time might be either 2,500 EUR processing threshold or six months of activity, whichever comes first.

You can collect ID information with the verification.document.front and verification.document.back arguments, and address information with verification.additional_document.front and verification.additional_document.back.

Additional information on beneficial owners (for both executives and owners)

You might need to collect a scan of an ID document and an address document to enable payouts, if Stripe can’t verify the beneficial owner’s provided information or if there are possible concerns about sanctions. In some cases, depending on various calculated risk factors, Stripe may be able to use Simplified Due Diligence and request only one document for verification at a later point in time.

These thresholds may change, but currently that point in time might be either 2,500 EUR processing threshold or six months of activity, whichever comes first.

Optionally, you can collect ownership information on each person who owns 25% or more of the company with relationship.owner and relationship.percent_ownership.

Additionally, for partnerships you need to provide a relationship.percent_ownership value for any owners added to the account.

Universal Beneficial Ownership Verification

After supplying the beneficial owner information, it is checked against the National Registry of Businesses (NRB). Depending on the results of this check, there are three outcomes:

The business is found in the NRB, and the information matches. The account is fully onboarded, and no additional action is required.
The business is found in the NRB, but the information doesn’t match. The account is fully onboarded, and no additional action is required. A discrepancy report is sent to the NRB.
The business isn’t found in the NRB. An attestation consisting of an IP address, date, and user agent of the person submitting the information must be provided. The person is attesting that the business is registered with the NRB, and the information given to Stripe matches.

curl https://api.stripe.com/v1/accounts/{{CONNECTED_STRIPE_ACCOUNT_ID}} \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc: \
  -d "company[ownership_declaration][date]"=1609798905 \
  -d "company[ownership_declaration][ip]"="8.8.8.8" \
  -d "company[ownership_declaration][user_agent]"="Mozilla/5.0"

Additional information on the representative

If Stripe is unable to verify the representative, you need to provide a scan of an ID document. This can be collected with the verification.document.front and verification.document.back arguments.

Additional information on the owner

If Stripe is unable to verify the owner, you need to provide a scan of an ID document. This can be collected with the verification.document.front and verification.document.back arguments.

Additional information on the individual

If Stripe is unable to verify the individual, you need to provide a scan of an ID document. This can be collected with the individual.verification.document.front and individual.verification.document.back arguments.

Universal Beneficial Ownership Verification

After supplying the beneficial owner information, it is checked against the National Registry of Businesses (NRB). Depending on the results of this check, there are three outcomes:

The business is found in the NRB, and the information matches. The account is fully onboarded, and no additional action is required.
The business is found in the NRB, but the information doesn’t match. The account is fully onboarded, no additional action is required. A discrepancy report is sent to the NRB.
The business is not found in the NRB. A proof of registration document (screenshot of the registration or copy of the confirmation email) is required to be uploaded.

Uploading proof of registration Custom accounts

In the case the business is not found in the NRB, a screenshot of the beneficial owner information from the NRB must be uploaded using the documents.proof_of_registration.files argument.

Pass the file in the file parameter and set the purpose parameter to account_requirement:

Command Line

curl https://files.stripe.com/v1/files \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \
  -H "Stripe-Account: {{CONNECTED_STRIPE_ACCOUNT_ID}}" \
  -F "purpose"="account_requirement" \
  -F "file"="@/path/to/a/file"

This request uploads the file and returns a token:

{
  "id": "file_5dtoJkOhAxrMWb",
  "created": 1403047735,
  "size": 4908
}

You may then use the token’s id value to attach the file to a connected account for identity verification.

curl https://api.stripe.com/v1/accounts/{{CONNECTED_STRIPE_ACCOUNT_ID}} \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc: \
  -d "documents[proof_of_registration][files][]"=file_5dtoJkOhAxrMWb

Additional information on the representative

If Stripe is unable to verify the representative, you need to provide a scan of an ID document. This can be collected with the verification.document.front and verification.document.back arguments.

Identity verification documents must be issued in Japan and show the person’s residency status.

Additional information on the individual

If Stripe is unable to verify the individual, you need to collect a scan of an ID document. This information can be collected with the individual.verification.document.front and individual.verification.document.back arguments.

Identity verification documents must be issued in Japan and show the individual’s residency status.

Special considerations

Collecting information for Japanese accounts is unique in that both kana and kanji language variations are required for a number of parameters:

first_name_kana
first_name_kanji
last_name_kana
last_name_kanji
name_kana
name_kanji
address_kana
address_kanji

You need to submit information for these parameters instead of their counterparts (that is, instead of first_name, last_name, and so forth). It might seem counterintuitive to provide two arguments that represent the same onboarding requirement, but Stripe can’t verify a Japanese account until we’ve received information for both language variations. These variations may be composed of full- or half-width hiragana, katakana, or Latin characters, with kanji-specific API parameters also allowing for kanji characters.

Japanese addresses

Both kana and kanji language variations apply to Japanese address requirements as well.

postal_code is always required when providing a Japanese address of either language variation. Stripe validates submitted addresses, and for a valid postal_code, we attempt to automatically fill attributes for matching state, city, and town for bothj address_kana and address_kanji.

Requests with address details that are incompatible with the provided postal_code fail.

line2 should contain the building name in addition to the room number if applicable. This attribute can be omitted when the address does not contain building details.

Here’s an example representation of a Japanese address, with explanations for how each part maps to its corresponding Stripe API attribute:

// 〒150-0001 東京都渋谷区神宮前1-5-8 神宮前タワービルディング22F
{
  "country": "JP",
  "legal_entity": {
    "address_kana": {
      "country": "JP", // 2-letter country code
      "postal_code": "1500001", // Zip/Postal Code
      "state": "ﾄｳｷﾖｳﾄ", // Prefecture
      "city": "ｼﾌﾞﾔ", // City/Ward
      "town": "ｼﾞﾝｸﾞｳﾏｴ 1-", // Town/cho-me
      "line1": "5-8", // Block/Building number
      "line2": "ｼﾞﾝｸﾞｳﾏｴﾀﾜｰﾋﾞﾙﾃﾞｨﾝｸﾞ22F", // Building details (optional)
    },
    "address_kanji": {
      "country": "JP", // 2-letter country code
      "postal_code": "１５００００１", // Zip/Postal Code
      "state": "東京都", // Prefecture
      "city": "渋谷区", // City/Ward
      "town": "神宮前　１丁目", // Town/cho-me (no kanji numerals)
      "line1": "５－８", // Block/Building number
      "line2": "神宮前タワービルディング22F", // Building details (optional)
    }
  }
}

Statement descriptors

Statement descriptors explain charges or payments and include information that banks and card networks require to help customers understand their statements.

We recommend setting the static components of statement descriptors in all three supported scripts (kanji, kana, and Latin characters) for Japanese connected accounts.

	PARAMETER
Statement descriptor	settings.payments.statement_descriptor
Statement descriptor (kanji)	settings.payments.statement_descriptor_kanji
Statement descriptor (kana)	settings.payments.statement_descriptor_kana
Statement descriptor prefix	settings.card_payments.statement_descriptor_prefix
Statement descriptor prefix (kanji)	settings.card_payments.statement_descriptor_prefix_kanji
Statement descriptor prefix (kana)	settings.card_payments.statement_descriptor_prefix_kana

You can set these fields with API.

curl https://api.stripe.com/v1/accounts \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc: \
  -d type=custom \
  -d country=JP \
  -d business_type=company \
  -d "capabilities[card_payments][requested]"=true \
  -d "capabilities[transfers][requested]"=true \
  -d "settings[payments][statement_descriptor]"="example descriptor" \
  -d "settings[payments][statement_descriptor_kanji]"="漢字明細" \
  -d "settings[payments][statement_descriptor_kana]"="カナメイサイ"

See Japanese statement descriptors for more details.

Universal Beneficial Ownership Verification

After supplying the beneficial owner information, it is checked against the National Registry of Businesses (NRB). Depending on the results of this check, there are three outcomes:

The business is found in the NRB, and the information matches. The account is fully onboarded, and no additional action is required.
The business is found in the NRB, but the information doesn’t match. The account is fully onboarded, and no additional action is required. A discrepancy report is sent to the NRB.
The business isn’t found in the NRB. An attestation consisting of an IP address, date, and user agent of the person submitting the information must be provided. The person is attesting that the business is registered with the NRB, and the information given to Stripe matches.

curl https://api.stripe.com/v1/accounts/{{CONNECTED_STRIPE_ACCOUNT_ID}} \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc: \
  -d "company[ownership_declaration][date]"=1609798905 \
  -d "company[ownership_declaration][ip]"="8.8.8.8" \
  -d "company[ownership_declaration][user_agent]"="Mozilla/5.0"

Additional information on the account

If Stripe is unable to verify the business entity, the entity doesn’t have a company.tax_id, or there are possible concerns about sanctions, you need to collect a proof of entity document to enable payouts. Collect this with the company.verification.document.front and company.verification.document.back arguments.

Companies with the card_payments capability

company refers to these types of entities:

Sociedad Anónima (S.A.)
Sociedad de Responsabilidad Limitada (S. de R.L.)
Sociedad Anónima Promotora de Inversión (S.A.P.I.)
Sociedad por Acciones Simplificada (S.A.S.)

Additional information on the individual

If the individual fails verification, doesn’t have an individual.id_number, or there are possible concerns about sanctions, then an ID document scan is required to enable payouts. This information can be collected with the individual.verification.document.front and individual.verification.document.back arguments.

Additional information on the representative

A person known as a representative must activate this connected account. This person needs to be an authorized signatory with legal powers to represent the company as set forth under the relevant corporate documents, and be authorized to agree to Stripe’s terms.

If Stripe is unable to verify the representative, the representative doesn’t have a representative.id_number, or there are possible concerns about sanctions, you need to collect a scan of an ID document to enable payouts. Collect ID information with the verification.document.front and verification.document.back arguments.

Additional information on owners

Information on all owners with more than 25% ownership of the company must be collected. When you have finished collecting the required owner information, you need to set company[owners_provided] to true. This lets Stripe know that you have completed this requirement.

If Stripe is unable to verify an owner, an owner doesn’t have a owners.id_number, or there are possible concerns about sanctions, you need to collect a scan of an ID document to enable payouts. Collect ID information with the verification.document.front and verification.document.back arguments.

Optionally, you can collect ownership information on each person with relationship.owner and relationship.percent_ownership.

Additional information on the account

Additional information on the individual

Depending on the situation, you might need to collect a scan of an ID document, an address document, or both to enable payouts if Stripe is unable to verify the individual or if there are possible concerns about sanctions.

Depending on the situation, you might need to collect a scan of an ID document to enable payouts if Stripe is unable to verify the individual or if there are possible concerns about sanctions. Collect ID information with the individual.verification.document.front and individual.verification.document.back arguments.

Additional information on the representative

Optionally, you can collect the representative’s ownership information with relationship.representative and relationship.percent_ownership.

Additional information on directors

Additional information on beneficial owners (for both executives and owners)

Optionally, you can collect ownership information on each person who owns 25% or more of the company with relationship.owner and relationship.percent_ownership.

Enhanced identity verification

To comply with Singapore’s Payment Services Act 2019, we’re collecting additional information (see below) and performing enhanced identity verification on certain connected accounts. Your platform needs to integrate with Connect Onboarding in order to satisfy the identity verification requirements.

If you don’t integrate with Connect Onboarding, you won’t be able to onboard connected accounts subject to enhanced identity verification.

Enhanced identity verification applies to:

Connected accounts belonging to individuals, and
Connected accounts that are used for the following activities:
- Financial services
- Receiving donations
- Rewards-based crowdfunding

Financial services are services, provided with or without the use of technology, that are financial in nature including, but not limited to, facilitating payments between two parties, remittances, collecting deposits, lending, or providing investment services.

Rewards-based crowdfunding, or seed crowdfunding, is a method of financing where entrepreneurs solicit financial donations in exchange for a product or service that may be available at a later date.

Additional information on the individual

We require the individual to be verified by means such as Myinfo, or by taking a selfie with an identity document using Stripe Identity. To collect such information, your platform must integrate with Connect Onboarding.

Additional information on the representative (enhanced identity verification)

For accounts subject to enhanced identity verification, Stripe requires the representative of the account to be verified by means such as Myinfo, or by taking a selfie with an identity document using Stripe Identity. To collect such information, your platform must integrate with Connect Onboarding.

Additional information on the representative (standard identity verification)

For accounts not subject to enhanced identity verification, if Stripe is unable to verify the representative, you need to provide a scan of an ID document. To collect an ID document, use the verification.document.front and verification.document.back arguments.

Additional information on the representative (all)

This connected account needs to be activated by a person, known as a representative, who must be an owner of the business entity, or a controller, defined as an individual with significant management responsibility for the entity, such as an executive officer or senior manager (for example, CEO, COO, CFO, General Manager, Vice President, etc.).

Additional information on the representative (all)

This connected account needs to be activated by a person, known as a representative, who has effective control over the organization, such as the president, secretary, or treasurer of the committee or management team.

Additional information on beneficial owners and directors (enhanced identity verification)

Accounts belonging to companies and subject to the enhanced identity verification are also required to provide information on all their beneficial owners and directors. Beneficial owners are persons who own 25% or more of the company (owners).

If Stripe is unable to verify a beneficial owner, you need to provide a scan of an ID document. To collect an ID document, use the verification.document.front and verification.document.back arguments.

Determining which accounts are subject to enhanced identity verification

In Connect Onboarding, we show a usage survey by default to determine which of your connected accounts are subject to enhanced identity verification. The usage survey asks your connected accounts to declare whether they’re using the account to perform any of the listed activities.

The usage survey asks your accounts the following questions:

Will your account be used to accept donations? For example, charity, non-profit or crowdfunding (Yes / No)
Will your account be used for rewards-based crowdfunding? (Yes / No)
Will your account be used to provide financial services? (Yes / No)

However, in the regional settings page, you may also confirm whether your platform allows your connected accounts to be used for any of the listed activities. The setting determines if users see the usage survey.

You’re responsible for the accuracy and completeness of any information about the current and expected business activities of your platform and its connected accounts that you provide to Stripe as part of the onboarding process. Failure to provide accurate and complete information about your platform and its connected accounts may result in the termination of your Stripe account.

If you’re not sure whether your platform’s connected account users will use their account for any of the above-mentioned activities, select option 1, for the connected user to provide their own confirmation.

If you select:	Usage survey	Owner and director details
Option 1: Some of my platform’s connected accounts may be used to facilitate financial services, rewards-based crowdfunding, or receive donations.	Shows the usage survey in Connect Onboarding for all non-individual connected accounts.	Only required if they use their accounts for any of the three listed payment activities.
Option 2: All of my platform’s connected accounts are used to facilitate financial services, rewards-based crowdfunding, or receive donations.	Hides the usage survey in Connect Onboarding for all connected accounts.	Required for all connected accounts.
Option 3: None of my platform’s connected accounts are used to facilitate financial services, rewards-based crowdfunding, or receive donations.	Hides the usage survey in Connect Onboarding for all connected accounts.	Not required for all connected accounts.

Closure of unverified accounts

As required under Singapore’s Payment Services Act, we’re permanently closing Singapore accounts that remain unverified for over 120 business days. These are accounts whose charges or payouts have already been suspended, so this closure affects only inactive accounts.

To help you identify affected accounts, we upload monthly reports titled “Unverified account list” to your Dashboard under the reporting and documents section, in which you’ll find the list of impacted accounts and their requirement deadlines. Any accounts closed in the last month are in the report titled “Closed unverified account list.”

We’ll close any account that hasn’t been verified by its designated deadline. The account owner needs to provide the missing verification information before the deadline to keep the account open. If the information is provided after the deadline has passed, we’ll release any remaining balance to the account holder’s bank account, but we won’t be able to reactivate their Stripe account.

Stripe sends emails to Standard and Express accounts that remain unverified for too long, to inform them of the impending closure and to remind them to update their account details. Stripe won’t communicate with Custom connected accounts directly. That means you, as the platform, can contact them to avoid account closures.

Accounts that are closed under this process have their disabled_reason set to rejected.other.

Unique Entity Number (UEN) verification

UEN information may be verified with the data made available at data.gov.sg under the terms of the Singapore Open Data License version 1.0.

Additional identity verification

To comply with regulatory requirements in Thailand, we require additional identity verification for certain connected accounts. This entails taking a selfie and uploading an ID document using Stripe Identity. Your platform needs to integrate with Connect Onboarding to satisfy this identity verification requirement.

Additional identity verification applies to the representatives and beneficial owners of connected accounts belonging to individuals, sole proprietors and unregistered partnerships.

If you don’t integrate with Connect Onboarding, you won’t be able to onboard connected accounts subject to additional identity verification.

Registered address requirement

The registered address requirement refers to the Household Registration address. Please provide an address as per the ‘Tabien Bann’ or Household Registration book, also known as the Blue book for Thai nationals, or Yellow book for non-Thai nationals. To collect a Household Registration address, use the registered_address parameter.

If the user is neither a Thai national nor resident of Thailand, collect their current residential address with the same parameter instead.

ID number requirement

The ID number requirement refers to the 13-digit code found on the front of a Thai ID card, and secondary ID number requirement refers to the laser code found at the back of a Thai ID card. To collect a Thai ID number use the id_number parameter, and to collect a laser code use the id_number_secondary parameter.

These requirements are only applicable to Thai nationals, so leave the parameters empty if the user isn’t a Thai national.

Additional information on the individual

If Stripe is unable to verify the individual or if they’re not a Thai national, you need to collect a scan of an ID document. To collect an ID document, use the individual.verification.document.front and individual.verification.document.back parameters.

Additional information on the representative

If Stripe is unable to verify the account representative or if they’re not a Thai national, you need to provide a scan of an ID document. To collect an ID document, use the verification.document.front and verification.document.back parameters.

Additional information on beneficial owners

Accounts belonging to companies and registered partnerships are required to provide information on all beneficial owners. A beneficial owner is defined as any individual who owns 25% or more shares of the business. If there is no such person, then any individual who exercises significant control over the company is considered a beneficial owner. Otherwise, please provide information on any individual holding the position of senior management.

If Stripe is unable to verify a beneficial owner or if they’re not a Thai national, you need to provide a scan of an ID document. To collect an ID document, use the verification.document.front and verification.document.back parameters.

Additional information on the company

If Stripe is unable to verify the company, you need to provide a scan of a company verification document issued less than 6 months ago. To collect the company verification document scan, use the company.verification.document.front and company.verification.document.back parameters on the Account object.

Additional tax information

If Stripe is unable to verify the company.tax_id, upload a copy of an IRS Letter 147C document or an IRS SS-4 confirmation letter as an alternate attempt at verification. This information can be collected with the company.verification.document.front argument, and should include the connected account’s company.name and company.tax_id.

Additional information on the account

To enable card payments, a validated city, state, and ZIP code for company.address is required. Card payments will be disabled if the company.tax_id (EIN) hasn’t been verified before 30 days or 1,500 USD in payments, whichever comes first.

To enable payouts, company.address needs to be a validated full address and the company.tax_id (EIN) needs to be verified. Payouts will be disabled if a full address hasn’t been validated or the company.tax_id is not verified before 30 days.

Additional information on the individual

To enable card payments, a validated city, state, and ZIP code for individual.address is required.

To enable payouts, individual.address needs to be a validated full address. Payouts will be disabled if a full address hasn’t been validated before 30 days.

If the individual fails verification with ssn_last_4, then the full SSN is required and their identity needs to be verified in order to enable card payments. Use the individual.id_number argument to collect this information.

Additional information on the representative

This connected account needs to be activated by a person, known as a representative, with significant responsibility to control, manage, or direct the organization; and is authorized by the organization to agree to Stripe’s terms. The representative must either be an owner or an executive, which you specify by setting relationship.owner to true or relationship.executive to true.

If Stripe is unable to verify the representative or if the person does not have an SSN, you need to collect a scan of an ID document to enable card payments. This information can be collected with the verification.document.front and verification.document.back arguments.

Additional information on owners

Information on all owners with 25% or more ownership of the company must be collected. When you have finished collecting the required owner information, you need to attest this by setting company.owners_provided to true. This lets Stripe know that you have completed this requirement.

If there are any unverified owners in the company, payouts on the connected account can become disabled at 750,000 USD in charges and charges can become disabled at 1 million USD, unless the following information is collected:

owners.dob.day
owners.dob.month
owners.dob.year
owners.address
owners.ssn_last_4
owners.phone

If Stripe is unable to verify an owner or if an owner does not have an SSN, you need to collect a scan of an ID document. This information can be collected with the verification.document.front and verification.document.back arguments.

Optionally, you can collect company ownership information. This can be done using the relationship.owner and relationship.percent_ownership attributes. Set relationship.owner to true and relationship.percent_ownership to the user’s ownership percentage. If relationship.percent_ownership is unspecified, the default is 25%.

Supported business structures

Optionally, you can collect information on the legal structure of your user’s business with the company.structure argument. See Business structure for more details.

Below lists the supported business structures for privately held companies:

multi_member_llc
private_partnership
private_corporation
unincorporated_association

Below lists the supported business structures for publicly traded companies. If you further classify the business with any of these structures, the representative does not need to be an owner nor an executive, and you do not need to provide information on additional owners.

public_corporation
public_partnership

Supported business structures

Optionally, you can collect information on the legal structure of your user’s business. This can be done using the company.structure argument. See Business structure for more details.

Below lists the supported business structures for government entities:

governmental_unit
government_instrumentality

If your user is an instrumentality with tax-exempt status, you can set the company.structure to tax_exempt_government_instrumentality.

Supported business structures

While uncommon, there are circumstances where an individual business operates and is treated more like a company, such as a single-member LLC. For these users, you can optionally collect information on their legal structure with the company.structure argument.

If your user’s business has only one member or owner and is registered as an LLC with a U.S. state, you can set the business_type to company and the company.structure to single_member_llc. You collect the same required information, except you use the company hash and the Persons API, instead of the individual hash. For any requirement in the individual hash, you need to map it to the account’s representative, such as setting representative.first_name instead of individual.first_name.

If your user has obtained a business identification (for example, has a tax ID that’s separate from their personal ID, or a business address that’s different than their home address), you can set the business_type to company and the company.structure to sole_proprietorship. You collect the same required information, except you use the company hash and the Persons API, instead of the individual hash since it pertains to the natural person. For any requirement in the individual hash, you need to map it to the account’s representative, such as setting representative.first_name instead of individual.first_name.

Supported business structures

Optionally, you can collect information on the legal structure of your user’s business with the company.structure argument. See Business structure for more details.

Below lists the supported business structures for non-profit organizations:

incorporated_non_profit
unincorporated_non_profit

The U.S. federal government grants tax-exempt status to certain government entities that are considered non-profit. If your user is an instrumentality with tax-exempt status, you can set the business_type to government_entity and the company.structure to tax_exempt_government_instrumentality. Then, collect the appropriate verification requirements from them.

Tax reporting information

By default, the requirements for transfers do not collect all information at the appropriate thresholds to file IRS Form 1099-K or Form 1099-MISC. If your business has U.S. federal 1099 filing requirements and plans to file these through Stripe, request the appropriate tax reporting capability and make sure to collect the necessary information from your users.

Threshold information

In addition to the onboarding requirements, there is a second threshold to keep payouts enabled, which depends on your industry and Stripe’s review of your platform profile. The company.tax_id (EIN) needs to be verified before 10,000 USD in charges for some platforms, and before 3,000 USD for other platforms.

Threshold information

individual.dob.day
individual.dob.month
individual.dob.year
individual.ssn_last_4