What is built, and what is planned

Hosted checkout with merchant identity, itemised order, shipping, tax, total and currency, refund-policy link and support contact. Card, USDC and Interac flows are simulated.

Live card capture requires provider-hosted or tokenized fields from a contracted provider.

Fixed-amount links that open a new checkout for each customer.

Live use requires an approved provider connection.

Onboarding wizard, payments with search and CSV export, payment links, settlements, refunds, disputes, API keys, webhooks, documents, team roles and support.

Real document uploads stay disabled until storage, scanning and retention controls exist.

Application queues, review checklists, explainable risk flags, provider submissions with evidence and second-person verification, audit log and runbooks.

Scheduled job that polls the provider for non-final payments, recovers missed webhooks, expires abandoned sessions and flags unsettled or mismatched records.

Depends on a provider's status and reporting APIs.

Request → authorization → provider submission → completion, with duplicate prevention. Disputes with deadlines, evidence checklists and outcome tracking.

Provider refund and dispute APIs vary; manual handling is supported.

Adapter architecture with a fully working Mock Provider, a MoonPay configuration scaffold based on public documentation, and a generic acquirer scaffold. Capabilities default to off until verified.

No provider is contracted.

Bank (fiat) or wallet (stablecoin) destinations with re-authentication, ownership attestation, review and team notification on every change.

Orion does not pool funds; settlement is by the provider.