Skip to main content
Before any onramp or offramp transaction can be initiated, a user needs to exist in Saber’s system and clear a few prerequisite steps. User Operations covers that entire identity and account layer.

Prerequisites

1

User Creation

Every flow starts by creating a user record in Saber’s system. This gives you a user_id that every subsequent action — KYC, bank linkage, transactions — is tied to, letting you map Saber users back to your own internal user records. See User Creation.
2

KYC

Users must complete KYC before transacting. Depending on the corridor, this happens through a hosted widget, KYC Sharing (if you’ve already collected KYC yourself), or a KYC Partner URL. See User KYC.
3

Bank Account Linkage

Users need a linked, approved bank account before offramp payouts can go out, or before certain onramp payment methods (like USD’s ACH pull) can be used. Depending on the currency, this happens through a direct API call or a hosted widget. See Bank Account.

Ongoing capabilities

Alongside these prerequisites, two things apply continuously to a user’s account rather than as a one-time setup step:

Wallet Operations

Each user has a wallet within Saber’s system that holds their crypto balance. Wallet operations cover checking balance and, where applicable, depositing or withdrawing from that wallet.

User Limits and EDD

Every user has a transaction limit. Once reached, no further transactions can be created until Enhanced Due Diligence (EDD) is completed to raise it — either through a hosted EDD widget or a Partner URL flow, depending on the corridor.

User KYC

Bank Account

User Limits and EDD

Related topics

Overview