Skip to main content
An on-ramp converts fiat into crypto. There are two ways to bring fiat in:
  • Auto-ramp accounts (this guide): a dedicated deposit account for the user. Anything paid into it over ACH, wire, or SEPA auto-converts to crypto and lands at a wallet address. Good for recurring or third-party funding, like payroll or invoices.
  • Linked bank on-ramp: link the user’s bank and pull funds on demand via ACH debit.

Before you start

  • Authenticate as an integrator and act on behalf of a verified user. See Authentication and Onboarding.
  • Confirm the user’s fiat_to_crypto capability is active. Capabilities tell you whether on-ramp is available and what’s blocking it (see Onboarding).

Create an auto-ramp account

Create a deposit account for the user, pointing at the wallet address, network, and token the converted funds should land in.
The response includes the fiat deposit instructions the user funds:

Fund it

Share the deposit instructions with whoever funds the account (the user, their employer, a customer). Any deposit that arrives auto-converts to token on network and settles to address. No further API call is needed to trigger the conversion. See What we support for the networks, tokens, and currencies available.

Track conversions

Each deposit that converts produces an on-ramp record. List them, or react to webhooks instead of polling:
The onramp.created, onramp.updated, and onramp.completed events fire as deposits are detected, converted, and delivered.

Linked bank on-ramp

Pull funds from a linked bank account instead.

What we support

Networks, tokens, and currencies.