> ## Documentation Index
> Fetch the complete documentation index at: https://www.bitnob.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Bitnob API requests authenticate with an `X-Auth-Client` API key header against https://api.bitnob.com.
> Always use the sandbox environment for testing. Never put live API keys in sample code.
> Money amounts are integers in the smallest unit of the currency (satoshis for BTC, cents for fiat). Never use floats.
> Every state-changing request takes a client-supplied `reference` and must be treated as idempotent on retry.
> Quotes expire. Re-quote rather than reusing a stale quote id.

# Transfer between wallets

> Transfers to a Bitnob-issued deposit address settle instantly, cost no gas, and never touch the chain.

When the destination is an active Bitnob-issued deposit address, on your account or another Bitnob account, the value moves on the internal ledger instead of the blockchain: no gas, no confirmation wait, instant settlement. The request and [webhook](https://www.bitnob.dev/docs/stablecoins/webhooks.md) shapes are identical to external sends, except that `hash` starts with `oc_` and has no on-chain record.

| Property | Internal transfer | On-chain transfer |
| - | - | - |
| Settlement | Instant | Chain confirmation threshold |
| Network fees | None | Dynamic per chain |
| Bitnob transfer fee | Applies | Applies |
| Chain interaction | None | Broadcast and confirm |
| Webhooks | Same events | Same events |

## How routing works

You submit the transfer exactly like an [external send](https://www.bitnob.dev/docs/stablecoins/sending-stablecoins.md), with the destination set to a Bitnob-issued deposit address. Bitnob detects that the destination is internal and nets the transfer on the ledger; anything else routes to the chain.

To route deliberately, keep a registry of your own issued addresses, retrievable with [List addresses](https://www.bitnob.dev/api-reference/addresses/list-addresses.md), and check destinations against it before choosing what to promise the user about speed and fees.

## Where it pays off

* **Sub-account and business-unit moves**: treasury shuffles that would otherwise pay gas for no reason.
* **Instant customer credits**: users with Bitnob-linked wallets receive value with zero latency.
* **Aggregation before settlement**: sweep user funds internally, then settle outward in one batched on-chain send instead of many.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.