The White Label SDK puts CPAY's payment rails behind your brand, your UX and your pricing. You build the gateway — merchants, checkouts, wallets, payouts run on the same infrastructure CPAY runs.
One SDK, three tiers. You operate the platform, your merchants accept crypto, their customers pay. CPAY stays invisible.
That's you. You own the brand, UX, onboarding, KYC and pricing. The SDK gives you merchant lifecycle, wallets, checkouts and payouts as typed API calls.
Your client. Each merchant gets isolated accounts and wallets, their own fee settings and their own settlement — provisioned programmatically.
Your merchant's end user. Pays through checkouts you host — cards on your domain, wallets under the hood, on 8 networks and 100+ assets.
| Merchant | Volume 30d | Your fee | Status |
|---|---|---|---|
| Acme Store | 64,120 USDT | 0.7% | ACTIVE |
| NovaShop | 41,800 USDT | 0.7% | ACTIVE |
| BetZone | 58,900 USDT | 1.0% | ACTIVE |
| Kiosk24 | — | 0.5% | ONBOARDING |
A three-tier fee waterfall runs on every payment. Your Platform Fee is yours to set, per merchant — collected automatically, settled to your wallet.
The infrastructure fee — flat and predictable, on the gross amount. It's the only thing CPAY takes.
Your margin. Set it per merchant, change it any time, cap it as you like. Collected on every transaction and settled to your Operator wallet.
Merchants can run their own fee on top — their tooling for their customers, same engine.
CPAY runs both. If you want a gateway live in weeks with CPAY doing the hosting — take the turnkey white label. If the gateway is your product, take the SDK.
| Turnkey White Label | White Label SDK | |
|---|---|---|
| Who builds the product | CPAY — hosted & supported | You — on your stack, your roadmap |
| UX, onboarding, KYC | CPAY's flows, your brand | Fully yours |
| Pricing control | Standard tiers | Your own Platform Fee, per merchant |
| Time to launch | Weeks | Your build — rails are ready |
| Best for | Fast market entry | PSPs, fintechs & platforms making payments their product |
Both models run on the same SDK. Pick per your licensing, risk posture and product.
Every merchant is an isolated account with its own keys and wallets. You operate the platform without ever holding client funds.
One master account under your control; merchants are logical entities in your system. Full embedded-finance control.
Provision accounts, wallets and credentials in one composite call. Update fees, suspend, close.
Hosted, iFrame and API checkouts — one-off, cart, token sale and recurring billing.
Merchant and customer wallets, on-chain and internal withdrawals, multi-send payouts.
Decrypt-and-verify helpers built in (AES-256 + JWT) — a signed event is one function call away.
TypeScript-first client, typed error taxonomy, full fee breakdown on every transaction object.
Idempotency keys, retry with backoff and audit hooks — the boring parts, done properly.
The SDK is in early access with design partners. Here's exactly where it stands — no asterisks.
Design-partner slots are limited while the SDK is in early access. Tell us what you're building — we'll map your licensing, custody model and integration path on a 30-minute call.