# Singapore verification requirements for Custom connected accounts

_(Updated: August 2026)_
Stripe regularly reviews and updates verification requirements to ensure full Compliance with all regulations and provide best-in-class protection for its users. These changes vary by region, guided by different regulatory, network, and partner rules, which inform the information we collect and verify to understand who our customers are.
We’re updating verification requirements for Singapore-based Custom connected accounts accepting [card_payments](https://docs.stripe.com/connect/account-capabilities#card-payments) or with [transfer](https://docs.stripe.com/connect/account-capabilities#transfers) capability enabled. Accounts must meet these requirements to continue accepting card payments and receiving payouts.
Changes include:
* **Constitution document collection**: We’re collecting Constitution of Companies, Partnerships and Non Profits who have not adopted a [Model Constitution](https://www.acra.gov.sg/register/business/registering-different-business-structures/local-company/company-constitution/). We will be surfacing [`documents.company_memorandum_of_association.files`](https://docs.stripe.com/connect/upcoming-requirements-updates?program=sg-2026#constitution-document-verification) to these accounts.
* **Collecting additional business and UBO information**: We’re updating the information we collect from businesses we currently support. This includes additional addresses for the legal entity and more information about the owners listed on the account.
See [more details about these changes](https://docs.stripe.com/connect/upcoming-requirements-updates?program=sg-2026).
## FAQ
* [Why is Stripe updating verification requirements?](#why-updating-requirements)
* [What new information is required?](#new-information)
* [Which capabilities are impacted?](#impacted-capabilities)
* [What accounts are affected?](#affected-accounts)
* [How do I update my integration?](#update-integration)
* [How do I find accounts that require updated information?](#accounts-to-review)
* [What are future requirements?](#future-requirements)
* [What happens if an account doesn’t provide the required information?](#missing-information)
* [Where can I learn more about these verification updates?](#more-information)
* [What are the deadlines?](#deadlines)
* [Does this affect other connected account types?](#other-connected-accounts)
* [Will requirements continue to change in the future?](#future-changes)
### Why is Stripe updating verification requirements for these accounts?
Payment regulations aim to create a safer, more secure financial ecosystem by helping prevent crimes like money laundering, fraud, and tax evasion. At Stripe, we’re subject to certain Know Your Customer (KYC) obligations that require us to collect, verify, and maintain identity information about businesses that use our services, 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.
### What new information is required?
We are asking users for the following:
* The date of incorporation, primary place of business, and place of administration for their legal entity.
* If their business has not adopted a [Model Constitution](https://www.acra.gov.sg/register/business/registering-different-business-structures/local-company/company-constitution/), a copy of its bespoke constitution or an equivalent document.
* Additional information for each Ultimate Beneficiary Owner including Nationality, Date of Birth and Address.
### Which capabilities are impacted by these new requirements?
The requirements apply to all connected accounts in Singapore with [card_payment](https://docs.stripe.com/connect/account-capabilities?accounts-namespace=v2#card-payments) and [transfer](https://docs.stripe.com/connect/account-capabilities#transfers) capabilities enabled.
### What accounts are affected?
These updated requirements apply to all Singapore connected accounts accepting [card_payments](https://docs.stripe.com/connect/account-capabilities#card-payments) or with [transfer](https://docs.stripe.com/connect/account-capabilities#transfers) capability enabled, with the following entity types:
* Sole Proprietorship
* Private Company
* Public Company
* Private Partnership
* Non Profit
### What changes do Custom platforms have to make to their integration?
If you use an API-based flow to onboard your connected accounts, you must update your integration to handle all requirement changes. Platforms have three options to choose from when deciding how to adjust their onboarding flow to ensure connected accounts meet these requirements.
Even if you have an API integration, you can still take advantage of hosted or embedded onboarding to implement the updated onboarding requirements.
* **[Embedded Onboarding](https://stripe.com/docs/connect/custom/onboarding#embedded-onboarding):** Add customisable embedded onboarding components to your site. These dynamically update to reflect new requirements.
* **[Stripe Hosted](https://stripe.com/docs/connect/custom/onboarding#stripe-hosted-onboarding):** Send users to our hosted onboarding experience. This flow also updates automatically to reflect new requirements, but provides less customisation. When your new connected accounts provide business information we're unable to verify, we'll surface detailed verification responses via the Accounts API. You'll need to adjust your integration to handle new verification responses.
* **API Onboarding:** Modify your existing onboarding flow using detailed verification responses from the Accounts API. This allows the most control, but requires the most effort to maintain.
[Visit our Integration guide](https://docs.stripe.com/connect/upcoming-requirements-updates?program=sg-2026) to learn about the changes, review timelines and access technical resources for updating your integration. We've released API updates to support new verification workflows for accounts in Singapore, allowing you to prepare for the necessary changes to your integration.
### How can I see which of my accounts require updated information?
See the status of affected connected accounts in the Dashboard's [Accounts to review](https://dashboard.stripe.com/connect/accounts_to_review) page.
To filter for Singapore requirements, click **Filter by: requirement updates** and select **Singapore 2026**.
### What are future requirements?
The `future_requirements` field on the [Account](https://docs.stripe.com/api/accounts/object#account_object-future_requirements), [Person](https://docs.stripe.com/api/persons/object#person_object-future_requirements), and [Capability](https://docs.stripe.com/api/capabilities/object#capability_object-future_requirements) objects eases the process of adapting to evolving compliance requirements.
Surfacing `future_requirements` provides a preview of upcoming changes to requirements for your connected accounts before they go into effect, so you can make necessary changes in advance.
### What happens if I don’t collect this information?
If an account doesn't provide the required information by the listed due date, their ability to accept payments and receive payouts will be paused. Typically, the timeframe to provide updated information is within 14 days of the due date to continue receiving payouts, and within 28 days to continue accepting payments. However, that timeframe might vary for certain types of issues.
### Where can I get more information on these verification updates and how they will impact my connected accounts?
See [this Stripe Doc](https://docs.stripe.com/connect/handle-verification-updates?accounts-namespace=v2#api-based-onboarding) for more information on handling verification updates for your connected accounts.
### Deadlines
* New Custom connected accounts created on or after **November 1, 2026** must meet the updated requirements during onboarding. Otherwise, they won’t be able to accept payments.
* Existing Custom connected accounts: All `future_requirements` will become current requirements on November 1st, 2026. The deadlines for providing requirements before their payments or payouts are disabled will be shown on the Dashboard.
### I also have other types of connected accounts, not just Custom connected accounts. Does this change impact those other accounts?
You don’t need to take action for connected accounts that aren’t Custom connected accounts. Your Stripe onboarding flow has automatically updated to handle changing requirements. We'll reach out to any connected accounts that need to provide updated business information.
### Will requirements continue to change in the future?
Yes. As global requirements change, we expect onboarding requirements to continue changing as well. If you use embedded onboarding components or Stripe-hosted onboarding, then Stripe automatically updates 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.