US verification requirements for platforms: Updates and FAQ

The Dashboard's Accounts to review page will show the status of connected accounts affected by any changes to verification requirements. To filter by country, click More filters > Verification requirement and then tick the box for the country you want to see. Here's a pre-filtered link for the US.

To make sure you’re up to date with the latest changes, we also recommend reviewing the new verification errors. And, you can listen for risk-related account updates via the Accounts API.

Deadlines

Custom accounts

Express accounts

All other connected accounts:

Requirements for individual accounts will take effect on a rolling schedule. The dates listed above are the earliest possible deadlines.

FAQ

Which accounts are affected?

The updated verification requirements apply to all users with the card_payments capability enabled in the US.

How can I see which of my accounts require updated information?

See the status of affected connected accounts in the new Dashboard's Accounts to review page. To filter by country, click More filters > Verification requirement and then tick the box for the country you want to see.

What specific requirements have changed for US connected accounts accepting card payments?

See more details about the changes.

What information is required to onboard new connected accounts in the US?

Use the interactive form to see details of the required verification info for specific account configurations.

How do my existing accounts provide the new information required?

For connected accounts that have access to the Stripe Dashboard, to the Express Dashboard, or to the embedded notification banner, Stripe will contact the account directly with details about the business information they need to provide and the deadline to respond. (Stripe has already contacted most of these accounts as of late July 2024, the remainder will be completed within the next month.)

For Custom connected accounts, you will need to take action to help your connected accounts provide this information, or to provide it yourself. See Custom account specific guidance.

What happens if my connected accounts don’t provide the required information?

If an account doesn't provide the required information by the deadline, their ability to accept payments and receive payouts will be paused. Typically, the time frame to provide updated information is within 14 days of the deadline to continue receiving payouts, and within 28 days to continue accepting payments. However, that timeframe might vary for certain types of issues.

My connected accounts don’t need to accept card payments. Do these requirements still apply to me?

If your US connected accounts don't need to accept card payments, you can unrequest the card_payments capability for them. If you unrequest card_payments in the US, the updated requirements wouldn't apply to your connected accounts, and you wouldn't need to adjust your integration or collect updated information from them.

Why is Stripe updating verification requirements for these accounts?

Payments regulations aim to create a safer, more secure financial ecosystem by helping prevent crimes such as money laundering, fraud, and tax evasion. Stripe has certain Know Your Customer (KYC) obligations that require us to collect, verify, and maintain identity information about our users, and for any individuals who ultimately own, control, or direct them. These requirements are frequently updated by Stripe, financial service regulators, card networks, and other financial institutions.

Will requirements continue to change?

Yes. As regulatory requirements evolve globally, we expect our onboarding requirements to continue changing as well. If you use embedded onboarding components or Stripe-hosted onboarding, we’ll automatically update your onboarding flow to handle the latest verification requirements. If you use API-based onboarding, you’ll need to manually modify your onboarding flow whenever requirements change. Learn more about the different onboarding methods in our documentation.