> ## Documentation Index
> Fetch the complete documentation index at: https://rain-sandbox-trial.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Verification Requirements & Screening
> The field-by-field tables for a person and a business, the country rules Rain applies, and what every applicant is screened against.
Everything here is a field you send, a rule Rain applies to it, or a check Rain
runs on it. Which tables apply to you depends on your compliance model, so start
with [Who verifies what](/docs/who-verifies-what) if you have not settled that.
For the statuses an application moves through, see [Application states](/docs/application-states). For accepted document types and formats, see [KYC/KYB documents](/docs/kyc-kyb-documents).
Text fields accept **English** and **Spanish** only. Uploaded **documents** can be in any language, including non-Latin scripts.
## Consumer requirements (KYC)
What you collect for an individual depends on your compliance model. Under Standard Compliance, Rain verifies identity in full. Under Hybrid Compliance, you collect only identifying fields because you have already verified the person.
### Consumers under Standard Compliance
Collect and submit the following for each individual:
| Requirement | Notes |
| ----------------- | ------------------------------------------------------------------------------------------------- |
| Full name | First name is required. |
| Date of birth | The applicant must be 18 or older. |
| Email | — |
| Phone | Country code and number. |
| National ID | In the US, a 9-digit SSN is required. |
| Physical address | Line 1, city, postal code, and country are required; line 2 and region are optional. |
| IP address | The applicant's IP address at submission time. |
| Identity document | Passport, ID card, driver's license, or residence permit. Upload front and back where applicable. |
| Selfie | A photo or video selfie. A liveness check is mandatory. A selfie alone is not sufficient. |
Verification begins once the personal information, identity document, and selfie are all present. Rain then runs background screening automatically (see [Screening](#screening)).
### Consumers under Hybrid Compliance
Because you have already verified the applicant's identity in your own compliance program, no identity document or selfie upload is needed. The application API still requires the same identifying fields as any consumer application:
| Requirement | Notes |
| ---------------- | ------------------------------------------------------------------------------------ |
| Full name | First name is required. |
| Date of birth | The applicant must be 18 or older. |
| Email | — |
| Phone | Country code and number. |
| National ID | In the US, a 9-digit SSN is required. |
| Physical address | Line 1, city, postal code, and country are required; line 2 and region are optional. |
| IP address | The applicant's IP address at submission time. |
Rain still runs AML, PEP, and sanctions screening on the applicant.
## Business requirements (KYB)
As with consumers, business requirements depend on your compliance model. Under Standard Compliance, you submit the company's full profile. Under Hybrid Compliance, you submit only its identifying fields.
### Businesses under Standard Compliance
Collect and submit the following for the company:
| Requirement | Notes |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Company display name | Required. |
| Legal entity name | Required. |
| Business/entity type | — |
| Registration number | Required. The company's state registration number, distinct from the tax ID. |
| Tax ID | Required. Distinct from the registration number. |
| Website | Required. If the company has no website, enter `N/A` and upload alternate documentation (for example, a service contract, partnership documentation, or a business description). |
| Physical address | Required. |
| Industry | Recommended. Applications without it are flagged but not rejected. See [Industry codes (KYB)](/docs/industry-codes-kyb) for how to classify the business. |
Supporting company documents may include a certificate of incorporation, incorporation articles, directors registry, state registry, shareholder registry, good standing certificate, incumbency certificate, proof of address, trust agreement, information statement, or power of attorney. See [KYC/KYB documents](/docs/kyc-kyb-documents) for which of these Rain accepts and in what format.
### Businesses under Hybrid Compliance
You manage your own company due diligence. Rain requires the company's identifying fields and runs AML, PEP, and sanctions screening on the company, on every representative, and on every UBO.
### Beneficiaries
Verifying a business also means verifying the people behind it. A corporate application includes its **representatives** (authorized signers) and its **Ultimate Beneficial Owners (UBOs)**, and what each one submits differs.
See [Ultimate Beneficial Owner (UBO)](/docs/ultimate-beneficial-owner-ubo) for who qualifies, what representatives and UBOs each provide, and how their checks run under each compliance model.
## Country and jurisdiction
Rain checks several country signals for each applicant: the **provided address country**, the **country extracted from submitted documents**, the **identity document's country of issue**, and the **IP address country**. It then applies the strictest applicable rule:
| Jurisdiction | Outcome |
| -------------------------------------------- | ---------------------------------------------------------------------- |
| Supported US state or supported country | Approve, if no other flags are raised. |
| Unsupported US state or soft-blocked country | Reject, unless the applicant clears with a supported proof of address. |
| Hard-blocked country | Reject. |
Under **Hybrid Compliance**, only hard-blocked countries are rejected outright; the unsupported-state and soft-blocked rules are relaxed.
Some countries have specific requirements:
* **United States:** a 9-digit SSN is required.
* **Nigeria:** identity is confirmed electronically (E-KYC) instead of by document upload; a selfie is still required.
## Screening
Every applicant, under both Standard and Hybrid Compliance, is screened for:
* **AML, PEP, and sanctions** matches. To reduce false positives, always submit the applicant's full legal name rather than initials or nicknames.
* **On-chain risk** (via Chainalysis) when a wallet address is provided. Rain blocks customers tied to high-risk on-chain activity.
A match against a sanctions, PEP, or watchlist source can place an application in manual review or result in a final rejection. See the [rejection catalog](/docs/rejection-catalog) for the reasons that cannot be appealed.
## Conditional requirements
Depending on your program configuration, applications may also require:
* **A wallet address:** if your program does not self-manage authorizations, each applicant must include at least one wallet address (EVM, Solana, Tron, or Stellar).
* **A collateral contract address:** if your program uses external collateral contracts, a contract address is required, plus a chain ID if your program spans multiple chains.
## Using an external compliance vendor
If you already verify customers with Sumsub or Persona, you can share that verification with Rain instead of re-collecting it. See [Reuse an existing verification](/docs/reuse-existing-verification) for the options and how to choose between them.
## What's next
Which documents to collect for people and businesses.
Track an application through to its outcome.
Who qualifies as a UBO in a business application.
Share verification you already ran with a vendor.