Skip to main content
Oynk is designed as a coordination layer, not a single liquidity marketplace, bank, or wallet. It gives payment applications one lifecycle while allowing different qualified providers and rails to perform route-specific work.

The five layers

1

Experience layer

A payment application, checkout, terminal, or operations user initiates and observes work.
2

Control plane

Oynk authenticates the actor, validates exact amounts and destinations, evaluates policy, requests quotes, assigns providers, and owns lifecycle state.
3

Provider network

Qualified providers commit liquidity, collect origin funds, exchange value, or execute destination payouts under corridor and capacity constraints.
4

Settlement layer

In the target architecture, Stellar assets and Soroban contracts create an auditable, reference-driven boundary for funding, commitments, claims, refunds, and disputes.
5

Visibility plane

Indexers normalize chain events into PostgreSQL; APIs and dashboards expose operational movement, synchronization health, and reconciliation context.

Separation of responsibilities

This separation prevents a common failure mode: treating a token transfer as proof of a complete cross-border payment.