Orchestration

SpherePay provides four ways to move money between fiat and stablecoins. All four are on-ramp or off-ramp solutions — they differ in how much control you need, how much UI you want to build, and whether transfers are one-off or recurring.

Product Comparison

Product	How It Works	Best For
Transfer API	You create a transfer intent. SpherePay returns deposit instructions (account + unique memo) for that specific transfer. The customer sends funds to those instructions; SpherePay matches the memo to process it. Instructions change per request.	On-demand transfers where you control timing, amount, and attribution
Ramp Widget	An embeddable JavaScript widget that handles the full on/off ramp experience — customer onboarding and transfer UI — directly on your website. SpherePay manages everything; you embed it with your Application ID.	Merchants who want to offer ramp functionality with minimal frontend work
Onramper Accounts	Creates a permanent virtual bank account (fixed account + routing number) tied to a specific wallet address. All deposits to that account auto-convert and forward to the linked wallet — no memo or per-transfer action required.	Customers who repeatedly on-ramp to the same wallet; create one per customer to track deposits
Offloader Wallets	Creates a permanent on-chain wallet address tied to a specific bank account. All incoming stablecoins auto-convert and forward to the linked bank account — no per-transfer action required.	Customers who repeatedly off-ramp from the same wallet; create one per customer

Onramper Accounts and Offloader Wallets are not multi-tenant

Both products use fixed addresses with no per-transfer attribution. If multiple customers share a single account or wallet, there is no way to identify who sent the funds. Always create one account per customer.

Prerequisites

Before initiating any transfer, the customer must have:

A verified identity — Complete KYC/KYB for all transacting parties
A registered bank account — Required for the fiat side of any transfer. See Bank Accounts.
A registered wallet — Required for the crypto side of any transfer. See Wallets.

Transfer Products

Transfer API

Create on-demand on-ramp and off-ramp transfers with full control over timing and amount.

Ramp Widget

Embed SpherePay's full ramp UI — onboarding and transfer — directly on your website.

Onramper Accounts

Permanent virtual bank accounts that auto-convert deposits to a linked wallet.

Offloader Wallets

Permanent on-chain addresses that auto-convert incoming stablecoins to a linked bank account.

Payment Instruments

Bank accounts and wallets are required prerequisites for transfers — they represent the fiat and crypto sides of a transaction.

Bank Accounts

Wallets

Common Flows

On-Ramp (Fiat → Stablecoin)

Transfer API — instructions are unique per request:

SpherePay returns: account number + routing + unique memo
Customer sends USD → SpherePay-provided account (with memo)
SpherePay matches memo → converts → sends USDC to customer wallet

Onramper Account — fixed account, no memo required:

Customer sends USD → fixed virtual bank account (permanent)
SpherePay auto-converts → sends USDC to the linked wallet

Off-Ramp (Stablecoin → Fiat)

Transfer API — instructions are unique per request:

SpherePay returns: on-chain deposit address for that transfer
Customer sends USDC → SpherePay address
SpherePay converts → sends USD via ACH/Wire to customer bank

Offloader Wallet — fixed address, no per-transfer action:

Customer sends USDC → fixed on-chain address (permanent)
SpherePay auto-converts → sends USD to the linked bank account

Next Steps

Supported Rails & Currencies — What's available by region and currency
Transfer Lifecycle — Transfer statuses and what each means