The Centiiv Protocol is a decentralized liquidity aggregation layer designed for seamless fiat-to-crypto (Onramp) and crypto-to-fiat (Offramp) conversions. This API allows aggregators, liquidity providers, and developers to integrate directly with the protocol to facilitate global value exchange.
⚠️ Important: Protocol vs. Payments
It is common to confuse our two distinct service layers. Please ensure you are using the correct endpoints for your use case:
| Service | Endpoint | Purpose |
|---|---|---|
| Centiiv Protocol | api.centiiv.io | Liquidity & Settlement: Manages nodes, liquidity pools, and the orchestration of crypto-fiat swaps. |
| Centiiv Payments | api.centiiv.com | Payment Processing (PSP): Manages multi-currency accounts, dispute resolution and our payment gateway (escrow, invoice and payment link checkouts). |
Environments
The Centiiv Protocol provides two distinct environments. The protocol determines which environment to route your request to based on the prefix of your API key.
| Environment | API Key Prefix | Use Case | Base URL |
|---|---|---|---|
| Sandbox | sandbox_* | Testing, integration, and development. | https://api.centiiv.io |
| Live | live_* | Production transactions and real value movement. | https://api.centiiv.io |
Pro Tip: You can explicitly override the environment by passing the
X-Environmentheader (values:sandboxorlive).
Authentication
All requests to the Protocol API must be authenticated. We use a header-based authentication system:
Header: X-API-Key: <your_api_key>
Key Security & Scope
- Public Keys (
pk_*): Certain client-facing endpoints accept your Public Key. These are safe to use in frontend applications (browsers or mobile apps). - Secret Keys (
sk_*): These are extremely sensitive. Secret keys grant full access to your account and liquidity. Never expose these in client-side code. They must only be used in secure, server-side environments. - Permissions: Endpoints requiring a Secret Key are explicitly labeled with a padlock (🔒) in these docs.
Transaction Types
The protocol handles two primary directions of value flow:
1. Offramp (Crypto → Fiat)
- Action: User sends cryptocurrency (e.g., USDC, USDT).
- Result: User receives the equivalent value in fiat (e.g., NGN) directly into their local bank account.
- Ideal for: Crypto wallets, payroll systems, and remittance apps.
2. Onramp (Fiat → Crypto)
- Action: User deposits fiat via a bank transfer or virtual account.
- Result: User receives the equivalent value in cryptocurrency (e.g., USDC) delivered to their specified blockchain wallet.
- Ideal for: Investment platforms and Web3 onboarding.
Support
Need a custom integration or a PSP we don't currently support? Reach out to our team at [email protected].