Deposit addresses
Open multi-chain deposit addresses against your own user IDs; deposits credit automatically after on-chain confirmation.
A custody wallet platform for exchanges and digital-asset apps
Multi-chain wallets,
made simple.
For exchanges and digital-asset applications, connect deposit addresses, deposit notifications, sweeps and on-chain withdrawals. One API, wired into your product.
Focus on your product. We take care of the wallet.
FableWallet
One API
One API
Networks and assets follow your activation configuration; the supported scope per chain family is confirmed at activation.
Wallet operations
From the first deposit to scaled operations
One clear wallet-operations path that keeps multi-chain complexity backstage.
Deposit notifications
Deposits are notified to your systems by callback, keeping ledger and business in sync.
Sweeps
Consolidate funds from scattered addresses by policy, cutting manual transfers.
Treasury-pool operations
Dispatch centrally inside the tenant treasury pool to support withdrawals and operations.
On-chain withdrawals
Initiate on-chain withdrawals through one API; transaction status is notified by callback and you can query progress and results.
Example address 0x71…7f3cExample amount 12.48 USDTExample status Deposited
Every step is observable, and every movement of funds leaves a record (illustrative data, not real customers).
Deposit addresses are issued per user ID you own, and credit automatically after on-chain confirmation
New addresses join monitoring automatically, and deposits are notified to your business by callback
Sweeps and treasury-pool dispatch happen inside your tenant, cutting manual transfers
On-chain withdrawal status is notified by callback, with progress and results you can query
Use cases
Three typical scenarios
Whether you run an exchange, a digital-asset app, or business treasury operations, it is the same API.
Exchange
Deposits and withdrawals for users
Open deposit addresses per required network, get notified as deposits arrive, and run withdrawals through policy-based approval.
Multi-chain addressesAutomatic deposit alertsPolicy-based approvals
Digital-asset app
Embed wallet capabilities
Use the API to add a multi-chain wallet; users stay in your app to deposit, withdraw and check history.
One APIUsers stay in your appQueryable history
Business treasury
Internal transfers and treasury pool
Run internal transfers and centralised dispatch inside the tenant treasury pool to reduce manual work and steady your operations.
Internal transfersTreasury-pool dispatchLess manual work
Core capabilities
One API that keeps multi-chain complexity backstage
Wallet infrastructure built for scaled operations.
Keep the complexity backstage. Hand you a clear interface.
01
Unified custody
Custody multi-chain assets in one place, with addresses, balances and statements managed together.
02
Automatic monitoring and callback notifications
New deposit addresses join monitoring automatically, and deposits and transaction status are notified to your systems by callback.
03
Treasury dispatch
Internal transfers and centralised dispatch inside the tenant treasury pool give your funding a steady rhythm.
04
EIP-7702 gas delegation
On supported networks, manage gas delegation centrally for sweeps and withdrawals. Gas is paid from the tenant gas wallet, not funded for free by the platform; the actual scope follows your tenant activation and delegation status, and platform configuration is only the tenant default.
These capabilities depend on the networks, assets and configuration actually activated; chains and assets that are not activated are out of scope.
Integration path
Integrate in three steps
From docs to production, the path is clear.
- 1
Align on requirements
Confirm the networks, assets and use cases you need, and activate your account.
- 2
Connect the API
Configure API keys, obtain deposit addresses and wire up callbacks.
- 3
Validate and launch
Run deposit, sweep and withdrawal integration tests, then confirm production settings.
Engineers can start right here.
Quickstart, API reference, callback verification and the OpenAPI spec. The integration docs are currently in Chinese.
FAQ
Frequently asked questions
What kind of business is it for?
It suits exchanges and apps that need to offer their users digital-asset wallets, deposits and withdrawals. You keep your product and user system and add wallet capabilities through the API.
Do users need another app?
No. Your systems use the wallet through the API, and users keep operating inside your product.
How are fees decided?
Fees depend on your business configuration, networks and assets, and are confirmed before activation. Deposit and withdrawal costs are borne by the user; platform configuration is the tenant default.
Next step: tell us about your business.
Share your use cases, the networks you need and your integration plans.