Skip to main content

Documentation Index

Fetch the complete documentation index at: https://stabyl.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Wallet routes let your team automate account reads, deposit instructions, recipient records, and transaction reconciliation. They do not expose production withdrawal submission. 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.
Withdrawals can appear in transaction history when initiated from the Stabyl Pro web account, but they cannot be submitted by API.

​
Core Routes

RoutePurpose
GET /partner/wallets/currenciesList wallet currencies and supported settlement rails
GET /partner/wallets/balances/overviewRead current balances
GET /partner/wallets/chainsList supported blockchain routes
GET /partner/wallets/crypto/addressGet one deposit address for a chain
GET /partner/wallets/fiat/deposit-accountGet the fiat deposit account
GET /partner/wallets/transactionsReconcile wallet activity

​
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 withdrawal workflows and internal account organization. Creating or updating a recipient does not move funds.

​
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. Recipient management requires an API key enabled for recipient actions.