> ## 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.

# Compliance Comes First

> Nothing unlocks before verification. What Cards KYC/KYB and payments verification each gate, and the application states along the way.

Verification is the first gate on Rain, not a feature bolted onto one
product. Card issuance, virtual accounts, and every other form of money
movement all sit behind it. Nothing downstream unlocks until the relevant
check passes.

## Two separate approvals

Clearing one product's compliance check doesn't clear another. Cards KYC or
KYB approval unlocks card issuance. Payments verification unlocks money
movement and virtual accounts. A customer can be approved for cards and still
blocked from opening a virtual account, or the reverse.

| Approval                  | Unlocks                                     | What it checks                                                              |
| :------------------------ | :------------------------------------------ | :-------------------------------------------------------------------------- |
| **Cards KYC/KYB**         | Card issuance                               | Identity verification on the individual or company applying for a program   |
| **Payments verification** | Virtual accounts, payment routes, transfers | Account-owner verification (CIP) on whoever owns the money-movement account |

See [Payments Compliance](/docs/payments-compliance) for the full picture on
the payments side, including transaction monitoring and on-chain screening.

## KYC or KYB, depending on program type

Your program type determines which check a customer goes through for Cards
compliance:

| Program type  | Who you issue to                                                      | How customers are verified                                        |
| :------------ | :-------------------------------------------------------------------- | :---------------------------------------------------------------- |
| **Consumer**  | Individuals, for example customers signing up for a branded card      | KYC on each individual                                            |
| **Corporate** | Businesses or employees, for expense management or corporate spending | KYB on the company, plus its users and ultimate beneficial owners |

See [Flow of Funds](/docs/first-steps) for how program type and management
model shape the rest of your build.

## Application states at a glance

Every application moves through a defined set of states as it clears
verification:

| State               | Terminal? | Action required? |
| :------------------ | :-------- | :--------------- |
| `approved`          | Yes       | No               |
| `pending`           | No        | No               |
| `manualReview`      | No        | No               |
| `denied`            | Yes       | No               |
| `locked`            | Yes       | No               |
| `canceled`          | Yes       | No               |
| `needsVerification` | No        | Yes              |
| `needsInformation`  | No        | Yes              |
| `notStarted`        | No        | Depends          |

See [Application States](/docs/application-states) for what triggers each
state, what to do in it, and what transitions to expect next.

## What's next

<Columns cols={3}>
  <Card title="How compliance works" icon="shield-check" href="/docs/compliance">
    The full Compliance tab: KYC/KYB documents, UBOs, and vendor token
    sharing.
  </Card>

  <Card title="Payments Compliance" icon="building-columns" href="/docs/payments-compliance">
    Account-owner verification, transaction monitoring, and on-chain
    screening for money movement.
  </Card>

  <Card title="Application States" icon="list-check" href="/docs/application-states">
    Every state in full: what triggered it and what to expect next.
  </Card>
</Columns>