Ramp Flow, Step by Step
A ramp provider settles on its own chain, and your app may serve users on another one. This page plays a buy or a sell end to end so you can see how the funds get from one to the other. Pick the chains your app enables in the dashboard, the wallet custody, the currency and the direction: the diagram rebuilds the flow for that combination.
The route shown is a provider that settles USDT on Polygon. When the app does not enable Polygon, Pollar creates a rail wallet for the user there, and Circle's bridge moves the USDC between Polygon and the user's chain. For how routes, quotes and orders work in the API, see Ramps.
The SDK creates a key on the device and sends it with the login. That key is the user's credential with the wallet provider: nothing gets signed without it.
Each combination crosses with the 3 custody types in the next table: 24 cases. Custody changes who signs, not which wallets exist.
| Enabled chains | Wallets created at sign-in | Polygon wallet | Destinations when buying with BOB | |
|---|---|---|---|---|
| None | None: a session without a wallet. | Not used. | None: no routes are offered. | |
| Stellar | Stellar. | Rail wallet, created when ordering. | USDC on Stellar. | |
| Solana | Solana. | Rail wallet, created when ordering. | USDC on Solana. | |
| Polygon | Polygon. | Visible, from sign-in. | USDT or USDC on Polygon. | |
| Stellar + Solana | Stellar and Solana. | Rail wallet, created when ordering. | USDC on Stellar and USDC on Solana. | |
| Stellar + Polygon | Stellar and Polygon. | Visible, from sign-in. | USDC on Stellar and USDT or USDC on Polygon. | |
| Solana + Polygon | Solana and Polygon. | Visible, from sign-in. | USDC on Solana and USDT or USDC on Polygon. | |
| Stellar + Solana + Polygon | Stellar, Solana and Polygon. | Visible, from sign-in. | USDC on Stellar, USDC on Solana and USDT or USDC on Polygon. |
| Custodial (Pollar) | Co-signed (2 of 2) | Self-custody (1 of 1) | |
|---|---|---|---|
| Where the keys live | In Pollar's wallet services, encrypted. | At the wallet provider, in a vault the user's device and Pollar control together. | At the wallet provider, in a vault only the user's device controls. |
| Who signs a ramp step | Pollar, without the user. | The device approves first; Pollar checks the transaction and approves second. | The device alone. Pollar sends it to the network but cannot sign. |
| Rail wallet | Pollar creates it when the order is placed. | A request to add a Polygon account, which the user approves. | Same as co-signed, without Pollar's approval. |
| Recovery | Not needed. | Required before receiving funds on mainnet. The user adds it directly with the wallet provider (passkey or email code); Pollar does not set it. | |
| If the user is offline | The order moves on by itself. | The order waits with the funds in the user's wallet. A pending request expires after 24 h and opens again; the order does not expire while funds sit in the rail wallet. | |
| Network | Testnet only. On mainnet new wallets are created at the wallet provider. | Mainnet and testnet. | Mainnet and testnet. |
The ramp provider delivers to the user's own Polygon wallet, and the swap and the burn leave from that wallet. For the mint, Pollar only delivers the message Circle signed and pays the gas: the destination and amount are fixed in it.
The existing rail wallet becomes visible, with its balance and history. No new one is created. If the app disables a chain, its wallets become rail wallets and stay the user's.
If a step fails after the funds arrive (swap or bridge), the balance stays in the user's rail wallet. The widget shows the funds in transit with a button to retry.
With wallets at the wallet provider, ramp steps ask for confirmation one by one, even if the app has an auto-approval window. Gas, reserves and fees are always paid by the app.
Example amounts (127 BOB for 10 USDT). The real rate is the ramp provider's quote.