What you can build
Each product is a slice of the same platform, not a separate integration:How Rain is different
Most card programs can’t settle on a weekend. That’s a structural constraint that limits working capital, and it compounds across every market you operate in. Rain settles seven days a week, including holidays, so a program parks days less collateral than it would with a banking-hours issuer. Partners fund transactions with stablecoins across a growing list of supported blockchains, so funding doesn’t wait on banking hours either. Because Rain is a Principal Member rather than a reseller, the economics pass through more directly.The payments infrastructure that works differently.
One platform, not six integrations
Every product shares three layers: customer records, compliance, and the ledger. Sharing them is what makes your second integration faster than your first:- Customer records: a user or company you create for cards is the same user or company you reference when you open a virtual account or send a payout. You don’t maintain parallel customer directories.
- Compliance: verification, sanctions and PEP screening, and ongoing monitoring run on shared infrastructure. Rain still grants approval per product: clearing cards KYC or KYB does not by itself clear a customer to move money.
- Ledger and event stream: every balance change lands on the same ledger, and every state change emits a webhook from the same event catalog.
What’s next
See the platform architecture
How your tenant, compliance, and the ledger connect across products.
Compare products
Pick the product you want to start with and jump into its docs.
Understand customers and identity
Tenants, companies, users, and how to map Rain records to your own.
Issue your first card
Go from API key to a funded card.