Bitnob primary sources — 2026-04-30

Project status in this pass

  • No canonical standalone Bitnob whitepaper or litepaper surfaced.
  • The clearest current source of truth is the official docs corpus and product-specific overview pages.

Primary-source snapshots

1) Docs homepage

  • URL: https://docs.bitnob.com
  • Key excerpt:
    • The docs landing page says: “Global money movement is hard. Your integration shouldn’t be. Payouts to 40+ countries. Stablecoins across multiple chains. Virtual cards. Bitcoin wallets. One integration.”
    • It breaks the platform into payouts, stablecoins, trading, card issuing, wallets, and blockchain RPC.
    • This was the fastest way to confirm that Bitnob is operating as a broad financial-infrastructure suite rather than a single wallet or trading product.

2) Stablecoins overview

  • URL: https://docs.bitnob.com/docs/stablecoins/overview
  • Key excerpt:
    • The page says Bitnob supports sending, receiving, and settling stablecoins across multiple blockchains with a “Stripe-quality developer experience.”
    • It explicitly says the mission is to bring critical crypto and payment infrastructure to Africa without compromising on global standards.
    • It frames stablecoins as foundational payment infrastructure for wallets, remittance platforms, merchant services, and treasury systems.

3) Payouts overview

  • URL: https://docs.bitnob.com/docs/payouts/overview
  • Key excerpt:
    • The Payouts API is described as a way to programmatically send money to bank accounts, mobile-money wallets, and cash-pickup locations across multiple countries.
    • The docs say businesses can fund payouts using Bitcoin, USDT, or fiat while Bitnob handles liquidity, conversions, regulatory clearing, and local disbursement.
    • This is strong evidence that Bitnob is selling a multi-rail payout and settlement layer, not just a crypto wallet.

4) Trading overview

  • URL: https://docs.bitnob.com/docs/trading/overview
  • Key excerpt:
    • The Trading API is positioned as programmatic access to USDT ↔ Bitcoin conversions with zero volume limits.
    • The page highlights real-time pricing, atomic execution, wallet-connected settlement, and webhook/log support.
    • It also says pricing uses liquidity from multiple exchange sources and OTC routing logic.

5) Wallet overview

  • URL: https://docs.bitnob.com/docs/wallets/overview
  • Key excerpt:
    • Bitnob wallets are described as managing Bitcoin, stablecoins, and fiat.
    • The page highlights real-time payments, on-chain and Lightning transactions, virtual-card integration, funding, withdrawals, and transaction tracking.

6) Blockchain RPC overview

  • URL: https://docs.bitnob.com/docs/blockchain-rpc/overview
  • Key excerpt:
    • The Blockchain RPC API is described as a unified JSON-RPC interface to 21+ blockchains including Ethereum, Bitcoin, and Solana.
    • This matters because it shows Bitnob is also packaging chain-access infrastructure into the same platform surface.

7) Card issuing course

  • URL: https://docs.bitnob.com/docs/card-issuing/card-issuing-course
  • Key excerpt:
    • The card-issuing docs are unusually expansive, covering registration, issuing, funding, authorizations, settlements, lifecycle states, limits, fees, fraud patterns, compliance, and program structure.
    • Even though this page is framed as a course, it shows Bitnob is productizing card-operations knowledge and workflows rather than only offering a thin API endpoint.

8) Changelog

  • URL: https://docs.bitnob.com/docs/changelogs/overview
  • Key excerpt:
    • Recent updates in early 2026 include USDC on Solana, richer payout-webhook FX breakdowns, Card Issuing API v2, migration notes for new card/customer resource models, and new Optimism RPC support.
    • This changelog breadth supports the view that Bitnob is an actively evolving multi-product infrastructure stack.

Working conclusion

Bitnob is best cataloged as crypto-finance infrastructure with a shared control plane across payouts, stablecoins, Bitcoin and Lightning wallets, trading, cards, and RPC. In this pass, the docs corpus—not a whitepaper—was the real primary-source surface.