Skip to main content
Two choices shape your integration: your program type, and your management model. The first decides who you verify. The second decides where funds sit and who makes the call on authorization and settlement. Both affect other products, not just cards.

​
Program type: consumer or corporate

Your program type determines who you issue to and how they’re verified:

​
Management model: Rain-Managed or Partner-Managed

Either way, Rain provides the infrastructure underneath. What changes is how much you run yourself:

​
Compare the models

Here’s how the two differ on the things that affect your build:

​
What each choice changes downstream

Your program type and management model affect four areas of your build.

​
Application flow

Your program type determines which application you submit to onboard a customer:
  • Consumer: submit a consumer application to run KYC on the individual.
  • Corporate: submit a corporate application to run KYB on the company. This also creates the company’s first user, and every user and UBO you add goes through its own KYC application on top of the company’s KYB.
See Onboard a cardholder for the full flow.

​
Funding

Your management model determines how you fund spending:
  • Rain-Managed: deposit supported tokens into each user’s smart contract. Their credit limit updates automatically once the deposit is confirmed.
  • Partner-Managed: hold collateral in your Rain account. Rain deploys a collateral contract per chain that serves as your reserve balance, and you pay off charges by ACH or crypto.
See Fund the card for details.

​
Wallet requirements

Your management model also determines whether each user needs a wallet:
  • Rain-Managed: each user must have a wallet address, which becomes an admin on their smart contract. If your users don’t have wallets, you can use a provider such as Turnkey, Zerodev, Dynamic, or Privy to provision them.
  • Partner-Managed: your company handles wallets on its own side.
For a Partner-Managed program, you can’t update a user’s wallet address once collateral contracts are live. The API returns a 423 Locked error if you try.
For a Rain-Managed program, update the wallet with update a user.

​
Payments verification

Who verifies the owner of a payments account follows the same split as the table above. See Payments compliance for the full picture, including transaction monitoring and on-chain screening.

​
What’s next

Set up access

Accept your Dashboard invite, get your API keys, and authenticate your requests.

Onboard a cardholder

Submit a KYC or KYB application and confirm approval before issuing a card.

Run a Rain-Managed program

Find customer contracts, check credit limits, and process collateral withdrawals.

Run a Partner-Managed program

Add collateral and pay off your balance when your company manages funds.