Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.spherepay.co/llms.txt

Use this file to discover all available pages before exploring further.

Onramper Accounts let you automate fiat-to-stablecoin conversion without issuing a per-transfer API call for each deposit. You create a virtual bank account for each customer, and any fiat deposited to that account is automatically converted to the linked stablecoin and delivered to the customer’s on-chain wallet — no polling, no manual conversion step.
Onramper Accounts are an add-on product. They use different endpoints than the Transfers API and do not support bank account creation via the Transfers API.

​
How it works

When you create an Onramper Account, SpherePay provisions a dedicated virtual bank account tied to a specific on-chain wallet address. The full flow is:
  1. You create an Onramper Account for a customer, linking their virtual bank account to a destination wallet.
  2. You share the virtual bank account details (account number, routing number, beneficiary name) with your customer.
  3. The customer makes a fiat deposit to the virtual account via ACH, Wire, or SEPA.
  4. SpherePay automatically converts the deposit to the configured stablecoin.
  5. The converted stablecoin is delivered to the customer’s on-chain wallet — no additional API calls required.

​
When to use Onramper Accounts vs. the Transfers API

Use Onramper Accounts when you want fully automated, deposit-triggered conversion with no per-transfer API call. Use the Transfers API when you need explicit per-transfer control, webhooks, or a custom flow triggered by your backend.

​
One account per customer

An Onramper Account has no per-transfer attribution. If multiple customers share a single virtual account, identifying who sent a deposit requires manually matching by amount, timing, or source bank — which is error-prone. Always create one Onramper Account per customer, even if they share the same destination wallet.

​
Supported rails and currencies

DirectionCurrencyRails
Fiat inUSDACH, Wire
Fiat inEURSEPA
Stablecoin outUSDCArbitrum, Avalanche, Base, Ethereum, Polygon, Solana
Stablecoin outUSDTEthereum, Tron

​
Integration steps

Before you begin, confirm that Onramper Accounts are enabled for your SpherePay application. Contact your sales representative if you need access.
1

Onboard the customer

Each customer must be registered via the Create Customer API, have accepted the Terms of Service, completed KYC (for individuals) or KYB (for businesses), and have a customer status of approved.
2

Create an Onramper Account

Call POST /v2/virtual-account with the customer ID, source currency, destination stablecoin, network, and wallet address.
{
  "customerId": "customer_1ab2c3d4",
  "sourceCurrency": "USD",
  "destinationCurrency": "USDC",
  "network": "ethereum",
  "walletAddress": "0x1234...abcd"
}
The response includes the virtual bank account deposit instructions and the destination configuration.
{
  "id": "virtualAccount_987xyz654",
  "active": true,
  "fees": {
    "totalBpsRate": "20",
    "integratorFee": {
      "bpsRate": "10"
    },
    "platformFee": {
      "bpsRate": "10"
    }
  },
  "depositInstructions": {
    "currency": "USD",
    "bankName": "Bank of Example",
    "bankAccountNumber": "000123456789",
    "bankRoutingNumber": "1234567890",
    "bankBeneficiaryName": "John Doe",
    "bankBeneficiaryAddress": "123 Main St, Anytown, USA"
  },
  "destination": {
    "currency": "USDC",
    "walletAddress": "0x1234...abcd",
    "network": "ethereum"
  },
  "created": "2025-04-20T21:49:46.697Z",
  "updated": "2025-04-20T21:50:18.854Z"
}
3

Retrieve account details

Use GET /v2/virtual-account/{virtual_account_id} to retrieve the virtual account and confirm the deposit instructions are correct before sharing them with your customer.
4

Share bank account details with your customer

Provide the customer with the depositInstructions from the response: account number, routing number, beneficiary name, and beneficiary address. Instruct them to use these details when making a fiat transfer from their bank.
5

Customer makes a fiat deposit

Once your customer deposits fiat to the virtual account, SpherePay automatically converts the funds and delivers the stablecoin to the configured wallet address. No further API calls are required on your end.
Conversion is instant once funds arrive at the virtual account. Transfer time from the customer’s bank to the virtual account depends on the rail (ACH, Wire, or SEPA).

​
Additional API operations

In addition to creating and retrieving virtual accounts, the API supports:
  • PATCH /v2/virtual-account/{id} — update the destination wallet or currency
  • GET /v2/virtual-account — list all virtual accounts
  • PATCH /v2/virtual-account/{id}/deactivate — deactivate a virtual account
  • PATCH /v2/virtual-account/{id}/reactivate — reactivate a deactivated account
To check the status of individual transfers, use the List Virtual Account Transfers endpoint.

​
Account verification

Some financial platforms require customers to verify ownership of their virtual account before linking it. SpherePay supports two verification methods:
  • Micro-deposit verification — a small amount (under $1) is deposited and withdrawn to confirm ownership.
  • Challenge deposit verification — one or more small deposits are made, and the customer confirms the exact amounts.
Deposits under $1 are always treated as verification events, not transfers.

​
Supported regions

Onramper Accounts are available to end-users globally, except in regions sanctioned or otherwise prohibited by law. Contact SpherePay for a current list of restricted regions.
Last modified on May 12, 2026