Crypto Wallets

​

The problem wallets solve

​

Why partners choose it

• No friction for your team — a single endpoint, a clear JSON response, and a call that is safe to repeat. Most integrations are done in an afternoon.
• No friction for your customers — they see an address, they send, it is done. The address never changes, so they can save it and pay again.
• No infrastructure to run — you do not generate keys, run nodes, watch blocks or move funds between addresses. We do it.
• No volatility — USDC and USDT only: what your customer sends is what you receive, in dollars.
• Four networks — Solana, Base, Ethereum and Tron: each customer pays on the network that is cheapest for them.
• Open from KYC Level 1 — a customer can receive a wallet as soon as it is created. See KYC levels.
• Predictable cost — you pay for a wallet when you create one, not for every customer on every network.

​

Security you can show your own customers

​

What you can build

​

The only limit is your imagination

​

How it works

Step 1: Create the customer              → KYC Level 1 (basic)
Step 2: Create a wallet                  → You get a deposit address
Step 3: Show the address to the customer
Step 4: The customer sends USDC / USDT   → The deposit is attributed to this customer
Step 5: The deposit is reported          → In your dashboard and by webhook: credit the customer in your own system
Step 6: You withdraw the collected funds → At any time, to your own external address

​

Every deposit is reported, every dollar is yours

​

How to withdraw

1. Open the Wallets section of your dashboard and click Withdraw on the blockchain you want to withdraw from.
2. Enter the amount and the destination address. The commission, the network fee and the amount you will receive are shown before you confirm.
3. Confirm with your account password. The amount is debited from your collected balance and the transfer is processed automatically.
4. Follow it under Your Withdrawals, and receive the wallet.withdrawal_completed webhook when it has been sent.

​

Supported networks

​

Create a wallet

curl -X POST https://api.kemycard.com/v1/wallets \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "customer_code": "bf75d143-e2ff-4872-8c93-cc6157f834aa",
    "blockchain": "solana"
  }'

{
  "success": true,
  "data": {
    "code": "01a11628-4600-7e59-bd4a-01604c588373",
    "customer_code": "bf75d143-e2ff-4872-8c93-cc6157f834aa",
    "blockchain": "solana",
    "currency": "USDC",
    "address": "CUSTOMER_DEPOSIT_ADDRESS",
    "status": "active",
    "created_at": "2026-10-07T11:38:19+00:00"
  }
}

​

Rules to know

• One permanent wallet per customer and per blockchain. Without a reference, a customer has one address on each network, and it never changes.
• As many additional addresses as you need. Add a reference to open another address for the same customer on the same blockchain. See One-time addresses.
• Safe to call again. Calling POST /wallets a second time for the same customer and blockchain returns the existing wallet with a 200 status. Nothing is created and nothing is charged, so you can call it every time you need the address.
• Creation fee. A fee is debited from your others ops balance each time a new wallet is created (201). It is refunded if the wallet cannot be created. Create a wallet when a customer actually needs one rather than for every customer on every network.
• Deposit fee. A fee is taken from each deposit before it is credited to your collection account. The wallet.deposit_received webhook gives the amount sent, the fee and the net amount credited.
• Withdrawal fees. A withdrawal of your collected funds carries a commission, plus a fixed network fee that depends on the blockchain. After these fees, a withdrawal must leave you at least $10. Both are shown in your dashboard and returned by GET /wallets/balance (withdrawal_commission and withdrawal_network_fee).
• The address does not change. It stays the same for the whole life of the wallet: your customer can save it and reuse it.

​

One-time addresses

curl -X POST https://api.kemycard.com/v1/wallets \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "customer_code": "bf75d143-e2ff-4872-8c93-cc6157f834aa",
    "blockchain": "solana",
    "reference": "order-1001"
  }'

• A new reference, a new address. order-1001, order-1002, order-1003: three different addresses for the same customer. There is no cap on the number of addresses.
• Rotate after each payment. When a deposit arrives, create the next address with a new reference and show that one to your customer.
• Safe to retry. The same reference always returns the same address, and nothing is charged again.
• You know what was paid. The reference comes back as wallet_reference in the deposit list and in the wallet.deposit_received webhook: you match the payment to your order without any lookup.
• Old addresses keep working. A deposit sent later to a previous address is still credited to you and attributed to the same customer.

​

Retrieve wallets

# All the wallets of your customers
curl "https://api.kemycard.com/v1/wallets?page=1&limit=20" \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

# The wallets of one customer
curl "https://api.kemycard.com/v1/wallets?customer_code=bf75d143-e2ff-4872-8c93-cc6157f834aa" \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

# One wallet
curl https://api.kemycard.com/v1/wallets/01a11628-4600-7e59-bd4a-01604c588373 \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

​

Follow deposits and your balance

# Deposits received, most recent first (filters: customer_code, wallet_code)
curl "https://api.kemycard.com/v1/wallets/deposits?customer_code=bf75d143-e2ff-4872-8c93-cc6157f834aa" \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

# Your withdrawals (read-only: a withdrawal is requested from your dashboard)
curl https://api.kemycard.com/v1/wallets/withdrawals \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

# Your collected balance, per blockchain
curl https://api.kemycard.com/v1/wallets/balance \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

​

Test it first

​

Next steps