Cowrie Research

orbital

4 min read

Orbital

  • Name: Orbital
  • URL: https://www.getorbital.com/
  • Category: regulated stablecoin-and-fiat payments company / vIBAN-and-custodial treasury operator / multi-jurisdiction settlement control plane
  • Summary: Orbital belongs in companies/, not projects/, because the useful question is not what protocol does Orbital run? but which named operator onboards businesses, chooses which Pay Perform group entity and regulatory perimeter they land inside, issues named vIBAN and wallet surfaces, screens transfers, applies a transaction-decision engine, and publishes the workflow truth around pay-ins, payouts, exchange, and treasury operations? The practical leverage sits in customer admission, jurisdiction/entity routing, account and wallet provisioning, transaction-monitoring policy, conversion workflow, and the company-run operating shell around fiat-and-stablecoin money movement.
  • What it does:
    • Operates one business-facing platform for pay-ins, payouts, exchange, stablecoin wallets, and multi-currency 1st Name vIBANs across web, API, and OTC access paths
    • Packages receivables workflows where merchants collect crypto through hosted payment links or dedicated customer wallets and can auto-convert receipts into target currencies
    • Provides custodial wallet and treasury flows so customers can hold, exchange, and move stablecoins and fiat balances inside one operator-managed shell
    • Exposes a client portal spanning accounts, treasury solutions, eCommerce, receivables, and exotic-FX workflows rather than a single narrow checkout widget
    • Runs transaction screening, blockchain / Travel Rule analysis, and a transfer decision workflow that can approve, refer, reject, or refund transfers
    • Sits on top of a multi-entity Pay Perform group spanning UK, Gibraltar, Estonia, and Switzerland regulatory perimeters, which makes the company boundary analytically more important than the surface product label alone
  • Key claims:
    • The homepage presents Orbital as one global platform that unifies pay-ins, payouts, exchange, stablecoin wallets, and named multi-currency vIBANs, available through Web Platform, API, or OTC Desk
    • The getting-started docs say Orbital helps regulated businesses accept crypto, manage treasury, and move funds globally with control, compliance, and automation, which is company-shaped operating-language rather than protocol language
    • The receivables-account docs describe a dedicated account where incoming crypto payments arrive through one-time links or dedicated customer wallets, can be auto-converted, and can then flow onward to Treasury Solutions, Payables, or external wallets
    • The client-portal docs show one operator surface for Accounts, Treasury Solutions, eCommerce, Receivables, and Exotic FX, reinforcing that Orbital is a unified workflow shell rather than one product endpoint
    • The Legal Disclosures page says Orbital is the trading name for the Pay Perform group of traditional financial and digital-asset service providers and names regulated entities in the UK, Gibraltar, Estonia, and Switzerland, which is exactly why the entity boundary matters here
    • The Legal & Compliance page says all transfers go through screening and transaction-monitoring rules, with blockchain and Travel Rule analysis for crypto transfers feeding Orbital’s Transaction Decision Engine, which determines whether to approve, refer, reject, or refund a transfer
    • The Terms of Use say Orbital services are intended for corporate users only and that specific Orbital Group companies hold the licences or permissions required for particular services, again reinforcing the multi-entity operator shell
  • Whitepaper: No classic standalone Orbital whitepaper is the point here. The strongest materials are the official site, product docs, and legal / compliance pages already captured or adjacent to ../whitepapers/orbital-primary-sources-2026-05-02.md.
  • Sources:

Internal linkages

Protocol / company boundary

  • There is no especially useful standalone Orbital protocol boundary doing the analytical work here.
  • The important surface is the company-run workflow for customer admission, regulated-entity routing inside the Pay Perform group, vIBAN and wallet provisioning, screening and transaction-decision policy, receivables and payout handling, exchange, and lifecycle truth.
  • That is why Orbital belongs in companies/: the real leverage sits with the named operator and entity group that controls access, compliance posture, and money-movement workflow, not with a neutral deployed protocol.

Control surface

  • Practical authority sits in onboarding and jurisdiction assignment, account and wallet issuance, supported currency and rail coverage, hosted pay-in and receivables workflow, payout routing, transaction-monitoring thresholds, Travel Rule handling, the transaction-decision engine, and whatever permissions / review policy Orbital applies inside the client portal and API shell.

  • The sticky dependency is workflow memory: once a business builds around Orbital-managed vIBANs, custodial wallets, receivables accounts, conversion rules, review queues, and transfer-state publication, the lock-in is to the company-run operating shell rather than to a generic stablecoin or payments primitive.

  • Read Orbital as a regulated payments-and-treasury operator first, not as a neutral protocol or durable project-layer note.

  • Last reviewed: 2026-08-12 UTC

Graph View

Backlinks