> ## 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.

# About Bitnob

> Bitnob's founding rationale, the problem it addresses in emerging markets, and the use cases the platform is designed around.

Bitnob was founded on the belief that financial services should be accessible regardless of location. The name references the genesis block, the first block in the Bitcoin chain. Our roots are in African markets, and the infrastructure is open to developers and businesses anywhere.

The goal is to bring crypto and payment infrastructure to Africa without compromising on global standards, and to shorten the time between an idea and a first transaction.

## The problem

Businesses in emerging markets that want to adopt crypto or modern payment rails face high costs and steep technical barriers. This hits startups hardest, since they rarely have the capital or in-house expertise to integrate financial services from the ground up. Established providers tend to overlook local currency handling and country-level regulatory requirements, which makes it hard to build products that fit African contexts.

The demand is not only local. Companies worldwide need to reach customers, suppliers, and markets in Africa. The platforms that serve them are usually either narrow in scope or too expensive for smaller players to onboard. Bitnob exists to reduce that friction while keeping African payment rails central rather than an afterthought.

## What the platform covers

> [card] Crypto rails
>
> Bitcoin, stablecoins, and Lightning for near-instant transfers.

> [card] Fiat on and off ramps
>
> Convert between local currencies and digital assets, and settle to bank accounts and mobile money.

> [card] Cards and extended services
>
> Issue virtual cards, handle merchant payments, and distribute funds across channels.

> [card] Direct onboarding
>
> Published pricing and self-serve signup, so a small team can integrate without a sales process.

## Who uses it

The infrastructure supports remittance applications, fintech platforms operating across African countries, and businesses that need to accept, store, and distribute digital assets or handle local currency payments.

Common integrations include payment gateways building crypto-enabled checkout, payroll services paying out in digital assets, and B2B platforms bridging distant markets.


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