Zynk’s Continuum enables instant wallet creation, unified liquidity access, and real-time balance visibility—bridging traditional finance with reliability, compliance, and speed.The Continuum APIs are designed for partners who want to provider their end users global financial rails without friction. It abstracts complexity, ensuring that moving value between fiat and stablecoins, or between jurisdictions, is as fluid as moving data.Continuum provides endpoints for managing non-custodial wallets and performing secure wallet operations using a two-step challenge–response pattern for sensitive flows. It covers wallet provisioning, account setup, passkey management, sessions, balances, and transaction utilities—organized into Two-Step Process APIs and Single-Step APIs.Supported Chains#
SOLANA ✅
ETHEREUM — Coming soon
ARBITRUM — Coming soon
POLYGON — Coming soonKey features of Continuum#
Unified Wallets
Manage user balances across currencies, chains, and partners with a single API layer.Instant Value Access
Real-time creation, top-up, and withdrawal operations across the Zynk ecosystem.Secure Identity Layer
Each wallet is mapped to a KYC-verified entity, ensuring traceability and compliance.Programmable Liquidity
APIs can be automated to allocate, replenish, or transfer liquidity dynamically based on real-time transaction flow.Key Concepts#
| Concept | Description |
|---|
| Entity | Represents a verified individual or business onboarded through KYC/KYB. |
| Wallet | The account layer for storing value, tied to an Entity. Each wallet supports multiple currencies or chains. |
| Balance | Real-time view of funds available, blocked, or pending within the wallet. |
| Transfer | The act of moving funds — internally or externally |
API Design Principles#
Predictable Structure: Every endpoint follows a consistent RESTful format.
Event Transparency: Each action triggers webhook updates, ensuring state synchronization across systems.
Security First: Endpoints require either the partner-level x-api-token or end-user wallet authentication (detailed in the Auth section).
Security model at a glance#
Two-step pattern for sensitive actions1.
Prepare — the server returns an unsigned challenge payload
2.
Submit — the client signs the challenge and submits it
This ensures client-side signing and minimizes key exposure.
Sessioned operations for OAuth / Email / SMS auth methods (temporary signing credentials).
Passkey (WebAuthn) support as a secondary method for strong, device-bound authentication.
