A payment system starting from a closed loop of essential needs
This ecosystem is designed as a single payment system, not a collection of separate products.
It begins with a closed-loop necessity and expands outward — without changing how money behaves inside the system.
What Exists in the System
The ecosystem is composed of a small number of system-level elements.
Each element exists to support payment, without requiring users or merchants to understand internal operations.
Value Sources
External services that introduce funds into the system.
These sources differ in origin, but not in how value is treated once inside.
Merchant Acceptance
Points where payments are completed.
Merchants receive payment results and settlement records, without exposure to internal asset or processing details.
Internal Processing
System-level mechanisms that handle conversion, routing, and reconciliation.
These processes are not visible to users or merchants.
Wallet
The system’s value container.
Wallets hold balances and represent user ownership.
They do not define payment methods or merchant interactions.
Payment Interfaces
Tools that allow value to be used.
Cards, apps, and devices provide access to the same underlying balance.
They introduce no independent value or logic.
By keeping composition simple and logic internal, the system remains extensible without changing how people pay.
How Value Is Handled Inside the System
1
Where Value Enters the System
Value enters through remittance, loans, and service top-ups.
At entry, funds are recorded into the user’s wallet balance and become available for internal circulation.
2
How Value Moves Inside the System
A payment starts as a wallet balance request.
The settlement layer routes, reconciles, and resolves the instruction internally, then produces a settlement result for the merchant.
3
How Stablecoin Is Used in Settlement
Users may choose stablecoin as the payment asset.
Stablecoin participates in internal settlement and is resolved into fiat-denominated settlement results at completion.
System Boundaries
Clear boundaries allow the system to scale across regions while introducing internal changes without altering merchant behavior or user responsibilities.
1
What the System Does
-
Processes payments and internal settlement
-
Maintains wallet balances and payment availability
-
Executes routing, conversion, and reconciliation internally
-
Produces clear settlement results for merchants
3
Asset Responsibility Boundary
-
Users choose funding assets at payment initiation
-
Asset handling occurs only within the settlement layer
-
No asset persists as a merchant-facing holding
2
What the System Does Not Do
-
It does not require merchants to hold, manage, or custody stablecoins
-
It does not expose internal asset logic to merchants
-
It does not ask merchants to participate in cross-border settlement
-
It does not act as a user-facing investment or trading platform
4
Operational Responsibility Scope
-
Merchants operate in a fiat-ledger view
-
Users interact with balances and payments, not settlement mechanics
-
Internal failures, retries, or routing adjustments remain system-managed