USD Onramp

USD onramp lets your users convert USD into stablecoin, pulled directly from a Plaid-linked bank account. Every onramp flow follows the same four steps: Create User → KYC → Bank Account Linkage → Transaction.

Both USDT and USDC are supported for USD onramp.

Create User

POST /api/v2/user

{
  "email": "user@example.com",
  "phone": "+12025550123"
}

Response:

{
  "success": true,
  "data": {
    "user_id": "550e8400-e29b-41d4-a716-446655440000"
  }
}

Save user_id — every subsequent call needs it as the X-User-Id header.

KYC

USD supports only the KYC Partner URL method — there is no KYC Widget or KYC Sharing option for USD. The user must submit US ID documents only.

Request a Partner KYC URL:

POST /api/v2/user/kyc/partner-url

Headers: X-User-Id: <user_id>This call is asynchronous. The first response may come back pending:

{
  "success": true,
  "data": {
    "status": "PENDING"
  }
}

Poll the same endpoint again after a few seconds until the status becomes ACTIVE, at which point the response includes the KYC URL:

{
  "success": true,
  "data": {
    "status": "ACTIVE",
    "url": "https://withpersona.com/verify?..."
  }
}

Redirect the user to url to complete identity verification. See Partner URL for the full reference.To return the user to your app afterwards, append redirect-uri as the last query parameter on the returned Persona URL:

&redirect-uri=<url-encoded-url>

Bank Account Linkage

USD bank accounts are linked through Plaid, using the Bank Account Widget:

const sigString = clientId + timestamp + "sdk" + userId
const secret = HmacSHA256(sigString, clientSecret).toString().toUpperCase()
// redirect to: https://app.saber.money/bank/add?client_id=...&user_id=...&timestamp=...&secret=...

The URL is valid for 10 minutes from generation. The user selects and authorizes their bank account via Plaid on this page.To return the user to your app once they exit the Plaid flow, append redirect_url as the last query parameter:

&redirect_url=<url-encoded-url>

Once the user adds their bank account and it’s successfully linked and approved, the client can fetch the list of approved bank accounts:

GET /api/v2/user/bank_account?status=APPROVED

A user can have up to 10 active bank accounts at any point in time.

See Bank Account — Through Hosted Widget for setup details.

Transaction

Two variants:

Pool Buy — collected funds are converted to stablecoin and deposited into the pool wallet on the Saber system.
External Buy — collected funds are converted to stablecoin and sent to a specified wallet address on a given network.

The flow is identical for both — the only difference is that External Buy requires wallet_address and network in the request. See Available Networks and Tokens for supported networks and per-network limits.

The request body must also include source_id — the ID of the linked, approved bank account funds should be pulled from.

Two kinds of quotes are available — a Live Quote (informational, executes at market rate) or a Locked Quote (rate held ~30-60s, supplied as quote_id in the buy request):Live quote:

GET /api/v2/wallet/s/quote?from_currency=USD&to_currency=USDT&from_amount=100

Locked quote:

GET /api/v2/wallet/w/quote?from_currency=USD&to_currency=USDT&from_amount=100

Save id from the locked-quote response as quote_id.

Pool Buy
External Buy

POST /api/v2/wallet/transaction/pool/buy

{
  "source_id": "<bank_id>",
  "fiat_symbol": "USD",
  "crypto_symbol": "USDT",
  "fiat_amount": 100,
  "payment_method": "bank_transfer_ach_pull",
  "quote_id": "<quote_id>"
}

quote_id is only required when using a Locked Quote — omit it when using a Live Quote.

{
  "source_id": "<bank_id>",
  "fiat_symbol": "USD",
  "crypto_symbol": "USDT",
  "fiat_amount": 100,
  "payment_method": "bank_transfer_ach_pull",
  "quote_id": "<quote_id>",
  "wallet_address": "0x318d2aae4c99c2e74f7b5949fa1c34df837789b8",
  "network": "BSC"
}

Checking status

GET /api/v2/wallet/transaction?transaction_type={POOL_BUY|EXTERNAL_BUY}&transaction_id={id}

Status values mirror the offramp equivalents (CREATED, PROCESSING, COMPLETED, FAILED, CANCELLED, REFUND_INITIATED, REFUND_COMPLETED, etc.). Poll until the status reaches a terminal state, or configure a webhook URL to receive completion pushes instead — see Order Lifecycle and Webhooks.

User limits and EDD

SSN is optional at KYC time, so limits are tiered based on whether an SSN was submitted:

US Customers	24-Hour Limit	7-Day Limit
Individual customers without SSN	$2,999.99	$15,000.00
Individual customers with SSN	$5,000.00	$15,000.00

There is no EDD widget for USD. For higher limits, the client requests an EDD link via the same async Partner URL pattern as KYC (POST → poll until status: ACTIVE → receive url):

If an SSN was already submitted at KYC, the user is taken directly to a broader questionnaire with a Persona link, where they upload the relevant supporting documents.
If no SSN was submitted, the first EDD pass collects the SSN; the second pass then runs the actual EDD process (questionnaire and document upload).

Getting Started

Client Admin Operations

Offramp

Onramp

User Operations

Checking status

User limits and EDD

Onramp Operations

User KYC — Partner URL

Bank Account — Hosted Widget

User Limits and EDD

​Checking status

​User limits and EDD

​Related pages

Onramp Operations

User KYC — Partner URL

Bank Account — Hosted Widget

User Limits and EDD

Checking status

User limits and EDD

Related pages