Wallet routes let your team automate account reads, deposit instructions, recipient records, signed withdrawals, and transaction reconciliation.
Wallet reads expose NGN and USD wallet currencies. USDT and USDC are stablecoin rails for USD activity, not separate wallet currencies.
Fiat deposits credit the NGN wallet. Stablecoin deposits credit the USD wallet after network confirmation and transaction screening.
Partner API withdrawal quote and submit calls require an explicitly enabled
key and an Ed25519 signature over the exact request. They do not require an
emailed verification code or a separate withdrawal token.
Core Routes
Deposit Model
Crypto deposit addresses are created on demand. Your application requests the chain it needs, receives the address for that route, and should display the returned chain and address exactly. Do not create addresses for every chain unless your product actually needs to show them.
Fiat deposit account details are also read on demand. Show the returned account details exactly and reconcile credited deposits from the transaction timeline.
Recipient Model
Saved recipients are reusable destination records for Stabyl Pro workflows and internal account organization. Creating or updating a recipient does not move funds, and API withdrawals do not accept a saved recipient as a destination.
Reconciliation Model
Use wallet transactions as the source of truth for wallet activity. The timeline can include:
- fiat deposits
- stablecoin deposits
- fees
- adjustments
- refunds
- withdrawals
Use the transaction id as the stable public identifier in your own system. Treat status updates as append or update events: a transaction may first appear while processing and later move to a final state.
Authenticated wallet reads require X-Api-Key with wallets:view. Recipient management and Travel Rule submissions require wallets:transfer. Withdrawals require wallets:withdraw and a signed request. GET /partner/wallets/chains and GET /partner/wallets/fiat/banks are public. 
