Cowrie Research

onboard

5 min read

Onboard

  • Name: Onboard
  • URL: https://www.onboard.xyz/
  • Category: cross-border payments and FX operator / stablecoin off-ramp and account-infrastructure company / dashboard-and-webhook workflow shell
  • Tags: ethereum-ecosystem
  • Summary: Onboard clears the bar for a company note because the practical dependency is no longer only there is an escrow-based P2P protocol or there is an on/off-ramp integration surface. The current live dependency is a named operator shell around Onboard Business and Onboard Pay: account approval, regulated entity posture, business-dashboard access, API credential issuance, IP-whitelisted payout keys, webhook-secret lifecycle, merchant-network workflow, and direct stablecoin-to-cash conversion all sit with one company boundary. The older protocol note still matters for the escrow and marketplace architecture; this note is for the operator shell users and integrators now inherit.
  • What it does:
    • Operates Onboard Business as a cross-border payments, treasury, multi-currency account, and FX workflow platform for companies moving money across borders
    • Offers API-based access for stablecoin wallets, local-currency payouts, account issuance, and related business payment flows through a company-managed dashboard and credential model
    • Runs Onboard Direct as a hosted stablecoin-to-cash offramp path linking wallet addresses to bank or mobile-money destinations for near-instant local-currency settlement
    • Maintains merchant and liquidity workflow around instant pay and merchant networks, rather than leaving the cash-out side to a purely neutral protocol layer
    • Packages webhook delivery, signed callback verification, API-key management, and payout-authorizing IP restrictions into the same operator shell that approves accounts and defines live service availability
    • Provides the legal and regulatory perimeter for the service through Gopay Financial Services Inc. d/b/a Onboard Pay, rather than through a detached protocol collective
  • Key claims:
    • The homepage now markets Onboard as Cross-Border Business Payments and FX Payouts, highlighting receive-payments, multi-currency transactions, real-time payouts, API access, and account-team support rather than only the older P2P-exchange framing
    • The homepage says Onboard operates under financial regulatory oversight across three continents and specifically references FinCEN MSB registration in the United States, FINTRAC MSB registration in Canada, and Nigerian regulated-partner infrastructure, which makes the named operator shell part of the real dependency
    • The terms page identifies Gopay Financial Services Inc. as the company providing the services under the Onboard Pay brand and says the platform offers multi-currency accounts, virtual accounts, collection and payout services, FX conversion, treasury/settlement services, API services, and supported digital-asset services
    • The getting-started docs say integrators must first apply for an Onboard Business account, wait for approval, sign in to the Business Dashboard, create API credentials, and register a webhook URL before making authenticated requests
    • The API-credentials docs say keys are created and managed inside the Business Dashboard and that IP restriction is required for keys that initiate withdrawals such as cash payouts or crypto transfers, which is direct evidence that production authority sits with the hosted operator shell rather than only with a public smart-contract surface
    • The authentication docs say every API request must include an API key plus an HMAC-SHA256 signature and repeat that payout- or transfer-capable keys must be IP-whitelisted, reinforcing that the live service is a gated operator environment rather than an open unauthenticated rail
    • The webhook docs say Onboard generates the webhook secret in the Business Dashboard, signs events with x-signature and x-timestamp, and retries deliveries until the endpoint returns 200 OK, which makes Onboard the publication boundary for account and transaction lifecycle truth
    • The Onboard Direct page says users can link bank or mobile-money accounts, receive a wallet address, send USDT or USDC on supported networks, and receive local currency in minutes, which is a much more company-run settlement flow than a neutral protocol primitive
  • Whitepaper: No classic standalone company whitepaper is the point here. The strongest primary materials for this pass were the current homepage, terms, Onboard Business API docs, Onboard Direct page, merchant-application page, and the focused source snapshot in ../whitepapers/onboard-company-primary-sources-2026-08-12.md, complemented by the older protocol-layer source packet in ../whitepapers/onboard-primary-sources-2026-04-26.md.
  • Sources:

Internal linkages

Protocol / company boundary

  • Keep onboard focused on the product and architecture surface: Smart Contract Escrow Accounts, mediator-assisted dispute flow, exchange matching, local-rail integration logic, and the old protocol / exchange / connect decomposition.
  • Keep this note focused on the named operator boundary above that surface: account approval, regulatory perimeter, business-dashboard access, API and webhook credential lifecycle, IP-whitelisted payout authority, direct stablecoin-to-cash workflow, merchant-network operations, and the publication of transaction/account state.
  • That split matters because how does Onboard's escrow and exchange architecture work? and which company currently decides who gets access, how payouts are authorized, and what counts as authoritative lifecycle truth? are related but not identical questions.

Control surface

  • Practical leverage sits in business and merchant admission, verification and compliance workflow, dashboard access, API-key issuance, IP-whitelisting for payout-capable keys, webhook-secret generation, signed lifecycle-event publication, supported corridor and payment-method exposure, and the hosted direct-offramp path.

  • The older non-custodial protocol story is still useful, but the current easiest path clearly depends on one company-run account, credential, and settlement shell.

  • Read Onboard as a company-run money-movement and stablecoin-offramp operator first, and only second as a neutral protocol or integration surface.

  • Last reviewed: 2026-08-12 UTC

Graph View

Backlinks