The stack
The diagram below traces a single request from your tenant to the event it triggers. Read it top to bottom.What each layer does
Each layer, and where it’s documented:Why Rain arranges the stack this way
Two choices in this architecture matter for how you build:Compliance sits above the products, not inside each one
Verification is a gate you pass through, not a feature of the cards product. That’s why the gate clears a customer for one capability and not another: it grants access per capability. Cards KYC or KYB approval unlocks card issuance. Payments verification unlocks money movement and virtual accounts. Clearing one does not clear the other. See Payments compliance for how compliance gates the payments side.Every product shares one ledger, so they reconcile against each other
A card authorization and an inbound fiat deposit for the same customer land in the same account, in different books. You reconcile once, against one source, rather than stitching together per-product balances.What’s next
Understand customers and identity
Tenants, companies, users, and how to map Rain records onto your own.
Compare products
Pick which product to start with.
Read how compliance works
The two verification pipelines and what each one unlocks.
Read the ledgering system
Accounts, books, and how double-entry ledgering works at Rain.