Onboard

• Name: Onboard
• URL: https://www.onboard.xyz/
• Category: crypto-fiat on/off-ramp protocol / P2P exchange infrastructure / escrow-based emerging-markets payments access
• Summary: Onboard is a non-custodial peer-to-peer exchange protocol and integration platform for moving between fiat and crypto. Its official docs frame the system as an escrow-based protocol plus Onboard Exchange and Onboard Connect, with low-code and native APIs for wallets and dapps that want local payment channels, best-offer routing, and dispute-managed on/off-ramp flows.
• What it does:
  • Runs a non-custodial P2P protocol on EVM chains using a Smart Contract Escrow Account (SCEA) that locks assets until counterparties or a mediator approve release
  • Offers Onboard Exchange as a ready-made marketplace for crypto-fiat swaps and Onboard Connect as the integration layer for third-party wallets and apps
  • Supports low-code redirect integrations and native API integrations for embedded onramp/offramp user flows
  • Publishes payment-channel and currency support for local rails such as NGN, KES, GHS, MUR, UGX, bank transfer, and M-PESA-style methods
  • Documents a dispute-mediation model, no-KYC and KYC trade modes, and contract architecture pages rather than relying on homepage marketing alone
• Key claims:
  • The docs describe Onboard Protocol as a “non-custodial peer-to-peer (P2P) protocol” for secure exchange of assets without centralized custody
  • The protocol overview says deployment targets EVM-compatible chains such as Ethereum, Base, BNB Smart Chain, and Polygon
  • Onboard Connect claims over 100 local payment methods, low-code or native integration options, and seamless escrow powered by the protocol
  • The exchange docs claim users can get onchain in less than 3 minutes and can support micro-transactions as small as $0.5 at near-zero fees
  • The trade-flow docs make the real operating model concrete: counterparties are matched, crypto is locked in escrow, fiat is sent over local rails, then release is mediated by confirmations or disputes
  • The docs expose llms.txt, OpenAPI specs, technical-model pages, and contract lists, which makes this a strong docs-first primary-source target even without a canonical whitepaper
• Whitepaper: No classic standalone whitepaper was found in the official materials reviewed during this pass. The primary-source surface is the docs portal, llms.txt index, contract/architecture pages, exchange/integration docs, and public GitHub links surfaced from the docs; see ../whitepapers/onboard-primary-sources-2026-04-26.md.
• Sources:
  • https://www.onboard.xyz/
  • https://docs.onboard.xyz/introduction.md
  • https://docs.onboard.xyz/the-protocol.md
  • https://docs.onboard.xyz/protocol-concepts/architecture.md
  • https://docs.onboard.xyz/contracts/list-of-contracts.md
  • https://docs.onboard.xyz/onboard-exchange/connect/overview.md
  • https://docs.onboard.xyz/onboard-exchange/how-exchange-works.md
  • https://docs.onboard.xyz/onboard-exchange/supported-currencies-payment-channels.md
  • https://docs.onboard.xyz/llms.txt
  • https://github.com/OnboardGlobal
• Last reviewed: 2026-04-26 UTC