Orbital primary sources — 2026-05-02

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth was Orbital’s official site plus product and operator docs.
• Several API-reference pages were difficult to extract cleanly in this pass, but the website, getting-started guide, receivables docs, hosted-payment-page docs, and client-portal docs were enough to recover the product shape.

Primary-source snapshots

1) Homepage

• URL: https://www.getorbital.com/
• Key excerpt:
  • Orbital presents itself as one global platform that unifies stablecoin speed and traditional payments.
  • The homepage foregrounds pay-ins, payouts, 1st Name vIBANs, stablecoin wallets, and exchange.
  • It also says the platform is available through Web Platform, API, or OTC Desk.

2) Solutions page

• URL: https://www.getorbital.com/solutions
• Key excerpt:
  • Orbital says businesses can initiate pay-ins via embedded payment pages, eInvoicing, or API.
  • It says payouts can be funded from custodial wallets or named vIBANs and initiated through the web platform, API, or file upload.
  • The page also emphasizes multi-currency vIBANs, stablecoin wallets, and auto-exchange across fiat, exotic currencies, and major stablecoins.

3) Getting started

• URL: https://docs.getorbital.com/docs/getting-started
• Key excerpt:
  • The guide says Orbital helps regulated businesses accept crypto, manage treasury, and move funds globally with control, compliance, and automation.
  • Even though the extract was brief, it is an important positioning statement because it frames Orbital as an operational product for regulated businesses rather than a retail wallet.

4) Receivables Account

• URL: https://docs.getorbital.com/docs/receivables-account
• Key excerpt:
  • Orbital describes Receivables as a dedicated account where incoming cryptocurrency payments are collected and managed.
  • Businesses can collect funds through one-time payment links or persistent dedicated customer wallets.
  • The docs say incoming funds can be auto-converted into a preferred currency and then moved onward to Treasury Solutions, Payables, or external wallets.
  • Travel Rule payer details are required before generating one-time links.

5) Hosted Payment Page

• URL: https://docs.getorbital.com/docs/hosted-payment-page
• Key excerpt:
  • Orbital’s HPP is a pre-built hosted flow for wallet selection, QR-code generation, and crypto-deposit confirmation.
  • The docs mention support for wallets such as Binance Pay, WalletConnect, MetaMask, and TronLink.
  • The flow supports fixed deposit amounts plus returnUrl and notifyUrl handling, which makes it a merchant-facing pay-in orchestration layer rather than only a treasury dashboard.

6) Client Portal overview

• URL: https://docs.getorbital.com/docs/client-portal
• Key excerpt:
  • The client portal is described as the secure web interface for managing Orbital accounts, products, and transactions.
  • The navigation spans Accounts, Treasury Solutions, eCommerce, Receivables, and Exotic FX.
  • This is strong evidence that Orbital’s operating surface extends well beyond one payments endpoint.

7) API-reference landing pages

• URLs:
  • https://docs.getorbital.com/reference/pay-ins
  • https://docs.getorbital.com/reference/pay-outs
• Key excerpt:
  • The extracted pay-ins reference clearly frames Pay-Ins as API endpoints for receiving deposits.
  • The payout reference did not extract cleanly, but the docs surface and related site copy consistently frame payouts as a first-class product alongside pay-ins, receivables, exchange, and vIBAN-based treasury workflows.

Working conclusion

Orbital is best cataloged as a regulated stablecoin-and-fiat payment orchestration and treasury control plane. The decisive evidence in this pass was the combination of named vIBANs, receivables accounts, hosted pay-in flows, portal-level treasury operations, and repeated positioning around regulated business controls, compliance, and multi-rail money movement. The main caveat is that some API-reference pages were harder to extract cleanly than the docs articles and website pages, so future review could pull more endpoint-level detail if needed.