CPAY / Wallet Developers · API

Crypto Wallet API.

Embeddable crypto wallets your users never have to leave your app for — created, funded and moved through one API.

Spin up non-custodial or custodial wallets, read balances, send, receive, swap and reconcile — across 8 networks and 100+ assets, behind a single integration. Wallet-as-a-Service, embedded in your product.

Read the API docs → Get API keys
01 / 06What it is

Wallets your users never leave your app for.

CPAY handles key generation, signing, gas and multi-chain routing behind one API and SDK — so you embed real crypto wallets directly inside your product.

It's what the market calls Wallet-as-a-Service or embedded wallets: the wallet infrastructure stays with us, the experience stays in your app, and you choose whether keys sit with your users or with your platform.

cpay / wallet api
02 / 06The model

Embedded, and non-custodial by default.

Two ideas define this API — where the wallet lives, and who holds the keys.

cpay / model
Embedded wallets · WaaS
Wallets that live inside your app

Your users get a real crypto wallet without ever leaving your product or juggling a separate wallet app. CPAY handles keys, signing, gas and multi-chain routing behind the API — you ship the experience under your own brand and UI. That's what the market calls embedded wallets, or Wallet-as-a-Service.

  • In-app — no redirects, no external wallet
  • Your branding, your UX, your users
  • Optional email / social sign-in
  • One SDK across web and mobile
Non-custodial infrastructure
You hold the keys — not CPAY

Non-custodial means you and your users control the private keys — never CPAY. We give you the wallet infrastructure and watch the chain, but we never take custody of the keys or the funds. So there's nothing for CPAY to touch, freeze or seize — we can't move money we never hold. Need custody for a specific product? The same API runs custodial too — your choice, and provable.

  • Private keys stay with you — never CPAY
  • CPAY can't touch, freeze or seize funds
  • No customer balances on our books
  • Custodial option from the same API, when you choose
03 / 06Capabilities

One API. The whole wallet lifecycle.

Create, fund, move, and reconcile — every wallet operation your product needs, behind a single integration.

cpay / capabilities
Create & manage wallets
Spin up a wallet per user or per account with one call — POST /v1/wallets. Address, metadata and lifecycle handled for you.
You control the keys
Non-custodial by default — private keys stay with you and your users, never CPAY. We can't touch or freeze funds we never hold. Switch to custodial from the same API when your product needs to hold balances.
Move value
Send, receive, swap and batch payouts across chains — with stablecoin auto-swap and unified addresses built in.
Read & reconcile
Balances, transaction history and signed webhooks that don't duplicate or drop — reconcile against on-chain data cleanly.
Multi-chain, one integration
100+ assets across 8 live networks. Add a chain without touching your integration — you maintain it once.
Secure by design
Encrypted keys, multi-layer 2FA, and signature/policy controls — with per-wallet limits and approval flows for higher-risk actions.
04 / 06How it works

Four calls to a working wallet.

From zero to a funded, reconciled wallet — no nodes, no key management, no chain-by-chain glue code.

cpay / integrate
  1. 1
    Create a wallet
    One call returns an address and wallet id — per user or per account.
  2. 2
    Fund & move
    Receive deposits, send, swap or batch payouts across supported chains.
  3. 3
    Listen on webhooks
    Get signed events for deposits, confirmations and transfers in real time.
  4. 4
    Read & reconcile
    Query balances and history; reconcile against on-chain data cleanly.
# 1 — create POST /v1/wallets → { "id": "wlt_9F2a…", "address": "0x8A3f…" } # 2 — send POST /v1/wallets/wlt_9F2a…/transfers { "to": "0x…", "asset": "USDC", "amount": "100" } # 3 — webhook event: wallet.deposit.confirmed # 4 — reconcile GET /v1/wallets/wlt_9F2a…/transactions
05 / 06Why CPAY

Wallet infrastructure that's already in production.

The same rails processing real payments for 50+ businesses — not a lab SDK.

cpay / trust
Production-grade
One stack behind payments, wallets and KYC/AML — serving 50+ global clients.
You hold the keys
Non-custodial by default — keys stay with you, never CPAY, so we can't touch or freeze funds. Custodial available from the same API when you need it.
Multi-chain
100+ assets, 8 networks, unified addresses and stablecoin auto-swap out of the box.
White-label ready
Ship branded wallets under your own name; the infrastructure stays with us.
06 / 06Who it's for

Built into products like yours.

Anywhere users need to hold and move crypto without leaving your app.

cpay / audiences
A
Exchanges & trading platforms
Per-user deposit, withdrawal and balance wallets without running key infrastructure.
B
Fintech & neobank apps
Add crypto balances, transfers and swaps inside an existing app in days.
C
iGaming & forex platforms
Player and trader wallets for fast deposits and instant, low-fee payouts.
D
Payroll & payout platforms
Programmatic wallets for mass payouts, rewards and contractor payments.
0.5%& lower
flat transaction fee
No setup fee. No monthly minimum.

You pay a flat 0.5% per transaction — nothing to start, nothing to maintain. No setup fee, no monthly minimum, no per-wallet charge. High-volume products earn a custom rate below 0.5%.

See full pricing →
FAQCommon questions

Questions, answered.

What developers ask before they integrate.

cpay / faq
Is the wallet API custodial or non-custodial?
Both — your choice. Non-custodial by default: the private keys stay with you and your users, never with CPAY, so we can't touch or freeze funds we never hold. Switch the same API to custodial when your product needs to hold balances.
Is this "Wallet-as-a-Service" or "embedded wallets"?
Both terms describe the same thing. CPAY handles key generation, signing, gas and multi-chain routing behind one API and SDK, so you can embed wallets directly inside your app — that's Wallet-as-a-Service (WaaS) / embedded wallets.
Which chains and assets are supported?
100+ assets across 8 live networks, with unified addresses and stablecoin auto-swap — behind a single integration you maintain once.
Can I white-label the wallets?
Yes. The wallet API works with CPAY's white-label setup, so you can ship branded wallets under your own name while the wallet infrastructure stays with us.
How are keys and funds secured?
Encrypted private keys, multi-layer 2FA, and signature/policy controls — with per-wallet limits and approval flows available for higher-risk actions.
— / —Get started

Ship wallets this week.

Read the reference, grab your keys, and create your first wallet in a few calls — or talk to us about custody and white-label options.

cpay / contact

One API. Every
wallet you'll need.

Non-custodial or custodial, multi-chain, embedded in your product — go live in days, not quarters.

Read the API docs → Talk to the team
general: support@cpay.world business: bd@cpay.world response: < 24h