Base URL
- Sandbox
- Production
To ensure secure data exchange, merchants should whitelist Saber Money’s IP addresses within their systems. This restricts access to trusted sources, helping to prevent unauthorized access.
Authentication
Every API request must be securely authenticated. Saber uses HMAC signature-based authentication.- API Key (Client ID) and API Secret (Client Secret) are issued to each merchant.
- To make a request, the client generates an API Signature by signing the payload with the secret.
- The API Signature, along with the Client ID, is passed in the request headers.
- This ensures requests are validated, secure, and cannot be tampered with.
Core entities
User
The central entity of the platform — almost every operation, fiat or crypto, requires a user context.
- KYC: must be completed and approved before a user can transact.
- Bank Account: a user can link one or more accounts, mandatory for fiat operations (payins and payouts).
- Wallets: each user is automatically assigned blockchain wallets across supported networks, used for deposits, withdrawals, and transfers.
Pool Account
A special account type mapped to the merchant’s business — the treasury account for internal operations:
- Liquidity management
- Handling Pool Buy or Pool Sell operations
- Acting as the settlement layer for certain transaction types
Transactions
All transactions on Saber are initiated and recorded at the user level, falling into two categories:- Crypto Transactions
- Fiat Transactions
- Deposit: a user deposits crypto into their assigned wallet.
- Withdrawal: a user withdraws crypto from their wallet to an external address.
- Internal Transfer: transfers crypto between two users within the Saber system.
Each transaction has a defined lifecycle with states (e.g.
initiated, pending, completed, failed), and developers can monitor these via webhooks or API fetch calls.Operations
- Admin Operations
- User Operations
Performed at the merchant level, not tied to any single user. Examples:
- Creating new users
- Internal transfers between users
Depending on Admin vs. User operation, signature generation varies slightly — see API Authentication.
Integration interfaces and tools
APIs
The primary integration point for all client and user operations — programmatic control over user creation, transactions, balances, and more.
SDK / Web Widget
A hosted user-facing component provided by Saber, used to collect KYC and bank account information without merchants building their own UI. Merchants generate a Widget URL and redirect the user, who completes the process on Saber’s secure environment.
Webhooks
Event notifications sent from Saber to the merchant’s server, providing real-time updates on transaction states, KYC status changes, and other events — critical for keeping merchant systems in sync with Saber’s backend.
Dashboard
A web-based portal for merchants to manage and monitor activity: track transactions and users, generate or rotate API/webhook keys, configure webhook URLs, and perform developer operations like initiating crypto withdrawals or checking balances.
Typical flow
1
Create User
The user is assigned wallets across blockchains.
2
Complete KYC
The user is verified and eligible for financial transactions.
3
Add Bank Account
Via API or Web Widget.
4
Initiate Transaction
Crypto or fiat (payin/payout/transfer).
5
Receive Status Updates
Via webhooks or status fetch endpoints.