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

# Payments Compliance

> The second verification gate: account owner identification, transaction monitoring, and on-chain screening for money movement.

Payments verification is **separate from Cards KYC/KYB**. Being approved to issue cards does not, on its own, let a customer move money or open a virtual account. Each payments customer completes account-owner verification and is screened on an ongoing basis before and while they transact.

## Account owner verification (CIP)

Every virtual account has an **account owner**, either a person or a company, who must complete a Customer Identification Program (CIP) check before the account can transact.

| Status  | What it means                                                 |
| ------- | ------------------------------------------------------------- |
| Pending | Verification is in progress. The account cannot transact yet. |
| Passed  | The account owner is verified. The account can transact.      |
| Failed  | Verification did not pass. The account cannot transact.       |

* **Standard Compliance:** Rain runs the CIP check on the account owner.
* **Hybrid Compliance:** you verify the account owner in your own compliance program; Rain still screens the party.

## Transaction monitoring

Rain monitors money-movement transactions for sanctions exposure, suspicious patterns, and travel-rule information. Monitoring applies to the **fiat legs** of a transfer: inbound deposits into a virtual account and outbound payouts from one.

## On-chain screening

Rain screens the on-chain source and destination of funds with blockchain analytics (Chainalysis) and blocks transactions tied to high-risk activity, for example addresses linked to sanctions, theft, or illicit services.

## What Rain can block

Rain gates money movement and virtual accounts **independently of card issuance**. Rain can:

* Approve a customer for cards but **not yet** clear them for money movement or virtual accounts.
* Block a customer from money movement or virtual accounts for compliance reasons while card issuance stays active.

If a payments action is blocked, the API rejects the request. Check the customer's payments verification status before you initiate transfers or create payment routes.

## Restrictions

Rain also subjects payment routes to regional, country, and industry restrictions applied at creation time. See [Restrictions & Availability](/docs/restrictions-and-availability).

## What's next

<Columns cols={2}>
  <Card title="Restrictions & availability" icon="ban" href="/docs/restrictions-and-availability">
    Regional, country, and industry limits on payment routes.
  </Card>

  <Card title="Onramps" icon="arrow-down-to-line" href="/docs/onramps">
    Receive funds into a virtual account.
  </Card>

  <Card title="Offramps" icon="arrow-up-from-line" href="/docs/offramps">
    Pay out to an external account.
  </Card>

  <Card title="How compliance works" icon="shield" href="/docs/compliance">
    The compliance overview and the Cards KYC/KYB gate.
  </Card>
</Columns>