What You Can Build
Four products partners build on Rasto Business, and which half of the platform each one leans on.
The object model is the same whatever you are building. What changes is who your customers are, and which half of the platform you lean on: fiat in and convert, or hold and send on chain.
Contractor payouts
Each contractor is verified once, gets a dedicated USD account, and receives stablecoins whenever the payer sends money.
B2B invoicing and settlement
Businesses onboarded through KYB. Their buyers wire the account, and USDC lands in the seller's treasury address.
Dollar accounts in your app
Customers hold a balance and spend from it. Deposits arrive as fiat and settle into a wallet you show them.
Treasury and self-custody
You are your own customer. Receive into your own accounts, and hold the result in wallets only your Recovery Key controls.
Choosing your first surface
Fiat in, deliver out
Start with virtual accounts. There is no signing service to build, and webhooks carry the whole trail.
Hold and send
Start with wallets. Plan for a signing service first: sends are impossible without one.
Most integrations do both, in that order. Wallet sends need a signing service with a verifier you have written and tested, so start that work early even if it ships second. Registering and activating your two wallet keys is part of live onboarding either way: see Going Live.
What every use case shares
| Step | Object | Page |
|---|---|---|
| Terms accepted before anything else | tos_link or inline attestation | Terms of Service |
| One customer per real-world entity | customer | Customers |
| Explicit endorsement request, then an explicit submit | endorsement, verification | Verification & Endorsements |
| Reconcile from the API, react to webhooks | transaction, events | Reconciliation |