Skip to main content
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. See 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: See Flow of Funds 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: See Application States for what triggers each state, what to do in it, and what transitions to expect next.

What’s next

How compliance works

The full Compliance tab: KYC/KYB documents, UBOs, and vendor token sharing.

Payments Compliance

Account-owner verification, transaction monitoring, and on-chain screening for money movement.

Application States

Every state in full: what triggered it and what to expect next.