EUR/GBP Onramp

EUR/GBP onramp lets your users convert Euros or Pounds Sterling into stablecoin. Every onramp flow follows the same four steps: Create User → KYC → Bank Account Linkage → Transaction — though EUR/GBP onramp handles the linkage step a little differently, as covered below.

Both USDT and USDC are supported for EUR/GBP onramp.

Create User

POST /api/v2/user

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

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

EUR/GBP supports two KYC methods. For onramp specifically, the user’s address (address line 1, town, country) is mandatory.

KYC Sharing
KYC Widget

POST /api/v2/user/kyc

Headers: X-User-Id: <user_id>

{
  "legal_name": "Hans Mueller",
  "poi": "<proof-of-identity-document-id>",
  "poa": "<proof-of-address-document-id>",
  "dob": "1990-01-31",
  "email": "user@example.com",
  "phone": "+491701234567",
  "country_iso3": "DEU",
  "address_line_1": "10 Musterstrasse",
  "town": "Berlin",
  "country": "DEU"
}

Response:

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

Since KYC Sharing means Saber isn’t collecting the KYC itself, the client must explicitly pass address_line_1, town, and country in this call.

See KYC Sharing for the full field reference. Saber may request supporting KYC documents at any time — these must be shared within 72 hours of the request.

Redirect the user to a signed URL:

const sigString = clientId + timestamp + "sdk" + userId
const secret = HmacSHA256(sigString, clientSecret).toString().toUpperCase()
// redirect to: https://app.saber.money/kyc?client_id=...&user_id=...&timestamp=...&secret=...&redirect_url=<url-encoded-url>

The URL is valid for 10 minutes from generation. Append the optional redirect_url as the last query parameter (URL-encoded) to send the user back to your app when they exit the flow.

Since the address fields are captured as part of the widget’s own KYC flow, no separate address submission is needed here.

See KYC Hosted Widget for the full parameter reference.

Bank Account Linkage

There is no bank account registration step for EUR/GBP onramp — funds are pulled directly via an Open Banking redirect at payment time, covered in the next step.

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.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=EUR&to_currency=USDT&from_amount=100

Locked quote:

GET /api/v2/wallet/w/quote?from_currency=EUR&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

{
  "fiat_symbol": "EUR",
  "crypto_symbol": "USDT",
  "fiat_amount": 100,
  "payment_method": "open_banking",
  "quote_id": "<quote_id>"
}

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

{
  "fiat_symbol": "EUR",
  "crypto_symbol": "USDT",
  "fiat_amount": 100,
  "payment_method": "open_banking",
  "quote_id": "<quote_id>",
  "wallet_address": "0x318d2aae4c99c2e74f7b5949fa1c34df837789b8",
  "network": "BSC"
}

Response: the payment_method: open_banking response includes a payment URL. Redirect the user there to select their bank and complete payment.

{
  "success": true,
  "data": {
    "id": "xxxxxx",
    "status": "CREATED",
    "payment_url": "https://pay.saber.money/...",
    "expiry": "xxxxxx"
  }
}

The payment URL is valid for 1 hour. If the user doesn’t complete payment within that window, the link expires.

See EUR/GBP Open Banking best practices for guidance on handling the redirect flow well.

Checking status

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

Status values mirror the offramp equivalents (CREATED, PROCESSING/PAYMENT_INITIATED, 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

Each user has a lifetime transaction limit (currently $200,000 USD equivalent — this figure is suggestive and subject to change; confirm current limits with Saber). Once a user’s limit is breached, no further transactions can be created until Enhanced Due Diligence (EDD) is completed to raise it. EDD is completed via the EDD Hosted Widget, with a turnaround time of 2-3 working days.

Getting Started

Client Admin Operations

Offramp

Onramp

User Operations

Checking status

User limits and EDD

EUR/GBP Open Banking best practices

Onramp Operations

User KYC

​Checking status

​User limits and EDD

​Related pages

EUR/GBP Open Banking best practices

Onramp Operations

User KYC

Checking status

User limits and EDD

Related pages