Skip to main content
Oynk has two operational presentation surfaces:
  • The public activity dashboard visualizes indexed and privacy-safe off-chain activity.
  • The authenticated console supplies signup, verification, sign-in, organization selection, role-specific shells, and a business-compliance draft form.

​
Connected activity views

The overview exposes gross movement, reference-paired estimated settlement, inflow, outflow, transfer and settlement counts, tracked wallets, sync timestamps, a timeline, and recent transactions. The transaction workspace filters loaded records by chain, route, asset, direction, date, and text and links on-chain records to explorers.

​
Planned destinations

Payments, payouts, cross-border transfers, terminal management, settlement execution, provider opportunities, liquidity, corridors, reconciliation, risk queues, API keys, webhooks, and full audit-log views do not yet have complete authenticated backend workflows. The console presents these as empty or unavailable states rather than fabricated records. Administrative sync is deliberately not a public browser control. Operators use an authenticated endpoint or CLI, and deployment policy should restrict run and failure reads.