New to SpherePay? Start with How it works and Concepts. Know your business outcome but not your flow type? Read this page first, then Solutions.
How to use this section
1
Confirm scoping inputs
Work through Before you pick a guide with your SpherePay representative — parties, rails, volume, and transfer model.
2
Route to a guide and pattern
Use Route by discovery outcome to pick First-Party or Third-Party Flows and the pattern inside that guide.
3
Validate before engineering
Complete the guide’s scoping output, kickoff list, and blocker checks before writing integration code.
4
Go deeper where needed
Follow links into Concepts, Solutions, and API Reference for object definitions, business examples, and payloads.
What these guides are for
Before you pick a guide
Confirm these inputs with your SpherePay representative during or immediately after discovery:- Who owns the funds at each step
- Customer of record — who SpherePay must onboard and verify
- Sender and beneficiary — may differ from the customer of record
- Platform role — whether your platform is in the flow of funds
- Downstream users — businesses, consumers, or both
- Fiat currency and rail — see Supported rails
- Stablecoin and network — see Supported assets
- Transfer model — one-off API transfers vs reusable deposit/cash-out instructions
- Balance model — movement/conversion only vs fiat balance holding
- Volume — expected monthly volume, average and maximum transaction size
Route by discovery outcome
Pick a guide
First-Party Flows
Same legal entity owns source and destination — one-off transfers, Onramper Accounts, and Offloader Wallets.
Third-Party Flows
Different parties or platform-mediated flows — supplier payouts, platform B2B, and consumer embed paths.
First-party or third-party?
If the routing table above does not match cleanly, use this fork:Map to Solutions
Implementation Guides define how to build. Solutions define what business outcome you are shipping. Use both:Treasury management
First-party treasury on-ramp/off-ramp — pair with First-Party Flows.
Payment acceptance
Platform fiat acceptance — often Third-Party Flows or Onramper pattern.
Payroll
Third-party disbursements — pair with Third-Party Flows.
Cross-border trade finance
Supplier and invoice settlement — pair with Third-Party Flows.