Connection Model
Each participant connects by role and publishes the outputs needed to move the lane from payment result to closeout.
Connection expectations
StableNexus expects each participant role to expose an authenticated connection surface, a stable transaction identity, and a recoverable status path when asynchronous updates are delayed or incomplete.
Each connection needs authenticated exchange, authenticity checks, idempotency, and a reliable recovery path when updates are delayed.
What each role provides
| Role | Responsibility | Boundary |
|---|---|---|
| Acceptance participant | Payment result updates, follow-up status updates, and refund or return signals. | Does not define final merchant funding on its own. |
| Settlement participant | Funding status, settlement timing, and settlement-facing reporting outputs. | Does not own merchant-facing QR acceptance. |
| Reconciliation service | Closeout evidence, exception state, and completion signals for reporting. | Does not originate payment or funding decisions. |
How updates reach StableNexus
Each participant needs a trusted update path and a fallback way to recover the latest state.
Security boundary
Every participant connection must verify authenticity before state changes are published.
Every lane also needs an idempotent recovery path for cases where the first asynchronous update does not settle the state.