Skip to main content
Accept USDC and USDT from your customers in minutes, not months. One API call gives a customer their own deposit address. Every payment is attributed automatically, every deposit is reported to you and credited to the balance of the wallet, and you withdraw it through the API whenever you decide.
Two types of wallet. A standard wallet keeps its balance until you withdraw it through the API (every plan, Découverte included). A collect wallet forwards everything it receives to the address of your choice, automatically, and is available on every plan, Découverte included. See Collect wallets.

Live in one call

POST /wallets returns a ready-to-use address. No node, no key, no blockchain code on your side.

Secured by design

Funds are moved to cold storage, keys never leave KemyCard, and your API keys only work from your allowed IP addresses.

Your funds, your call

Withdraw the balance of a wallet to the address of your choice at any time, with one API call.

The problem wallets solve

Collecting crypto with a single shared address means asking every payer for a transaction hash, matching payments by hand and fixing the mistakes. It breaks as soon as you grow. With wallets, the address is the reference. A deposit on the address of customer A can only come from customer A: no memo, no hash, no manual matching, no support ticket.

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

Funds are moved to cold storage

Deposits do not sit on the deposit addresses. They are swept to secured cold storage, and withdrawals are served from separate operating wallets. A deposit address is a way in, not a place where funds are kept: the balance of a wallet is tracked by KemyCard.
Keys are generated and kept by KemyCard, encrypted at rest. They are never returned by the API, never shown in the dashboard and never sent to your servers: there is nothing for you to store, and nothing to leak on your side.
Withdrawals are made through the API, with your API key: anyone who holds it can withdraw. Keep your keys secret, on your servers only. Your keys only work from your allowed IP addresses: we strongly recommend restricting this list to your own servers, so that a leaked key cannot be used from anywhere else.
You only ever see the wallets and the deposits of your own customers. A wallet code that belongs to another account answers 404, exactly as if it did not exist.
Every webhook is signed with HMAC-SHA256 using your endpoint secret, and retried if your server does not answer. You credit a customer only on a message you have verified. See Webhooks.
If a wallet cannot be created, the creation fee is refunded automatically. If you call twice, you get the same wallet and you are charged once.

What you can build

Collect funds from your customers

Top-ups of an account in your app, payment of an order or an invoice, deposits on a trading or savings product: give each customer their address and credit them when their deposit arrives.

On-ramp

A USDC wallet on Solana can receive the deposits of a virtual bank account: your customers pay by bank transfer, and the funds arrive in USDC.

The only limit is your imagination

A wallet is a building block, not a finished product. There is no cap on the number of wallets you create or on the number of customers you serve: one address per customer, as many customers as your business reaches. What you build on top is up to you.

Marketplaces

One address per buyer, or one per order with a reference: you always know which sale a payment belongs to.

Top-ups and credits

Let users fund their balance in your app, game or platform with stablecoins, from anywhere in the world.

Invoices and subscriptions

Give each client a permanent address: every payment they send is matched to their account.

Remittance and payouts

Collect in stablecoins in one country and pay out where your customers need the money.

Savings and investment apps

Accept deposits from each saver on a dedicated address, without ever handling a private key.

One-time payment addresses

A fresh address for every order, invoice or session, replaced after each payment. Each one is still tied to your customer.

Your idea

If money has to come in from many people and be attributed to each of them, wallets do it.

How it works

Your customers never need to do anything other than send funds to their address.

Every deposit is reported, every wallet has its balance

You always know who paid. Each deposit received on the wallet of one of your customers appears in the Wallets section of your partner dashboard, with the customer, the blockchain, the amount and the date. The same deposit is sent to your server by webhook, so you can credit the customer in your own system without anyone opening the dashboard. Each wallet has its own balance. A deposit is credited to the wallet that received it, net of the deposit fee: a customer who sends 100 USDC on Solana adds the net amount to the balance of their Solana wallet. A withdrawal debits it. The balance is returned with the wallet (GET /wallets/{code}, GET /wallets) and in the wallet.deposit_received webhook. You see the totals. GET /wallets/balance adds up the balances of your customers’ wallets per blockchain, with the number of wallets and the withdrawal fees. Your dashboard shows the same balances per blockchain, and a balance column for each wallet. How you consolidate these funds on your side is up to you.

Withdraw from a wallet

You withdraw from the balance of a wallet with POST /wallets/{code}/withdrawals, at any time, to the address of your choice:
  • Same network, same currency. The withdrawal is made on the blockchain and in the currency of the wallet. The destination can be any valid address on that blockchain, except the address of the wallet itself.
  • Fees deducted from the amount. The withdrawal commission of your plan and the network fee of the blockchain are deducted from amount. After these fees, you must receive at least $10.
  • Immediate debit. amount is debited from the balance of the wallet as soon as the request is accepted, and the transfer is sent automatically. The withdrawal is processing, then completed: you receive the wallet.withdrawal_completed webhook when it has been sent on the blockchain. If a withdrawal cannot be sent, it is retried automatically. If our team has to cancel it, the full amount, fees included, is credited back to the wallet and you receive wallet.withdrawal_failed.
  • Safe to retry. Send an idempotency_key (up to 64 characters). Calling again with the same key on the same wallet returns the existing withdrawal with a 200 status, and nothing is debited a second time. A new withdrawal answers 201.
  • Clear errors. 422 for an invalid address, an amount too low after fees, or an insufficient wallet balance (details.available and details.requested). 404 if the wallet is not one of your customers’ wallets.
Check the destination address and the blockchain before you call. A blockchain transfer cannot be cancelled or reversed. If the address is wrong, or if it is not an address on the blockchain of the wallet, the funds are permanently lost and KemyCard cannot recover them.
Withdrawals are made with your API key. API calls are only accepted from your allowed IP addresses, which are required: keep this list limited to your own servers, and keep your keys secret, on those servers only. A key used from any other address is refused.
Your customers have no direct access to KemyCard. When a user of your application asks for a withdrawal, you process the request in your application, then you call the endpoint.

Collect wallets

A collect wallet is made for partners who want the money of their customers sent straight to their own address, with a single fee. Your customer pays on their own deposit address; KemyCard attributes the payment, then forwards it to your destination_address.

Every plan

Available on Découverte too. Creation fee: $0.50.

Free deposits

No deposit fee: every deposit is added to the balance of the wallet.

One fee per forward

The commission of your plan and the network fee, taken once from the amount forwarded.

How a collect wallet works

  • Networks: USDC on Solana and USDC on Base only.
  • **Threshold of $3.** As soon as the balance of the wallet reaches $3, the whole balance is forwarded in a single transfer. A deposit below $3 stays in the balance and adds up with the next ones.
  • Destination. destination_address is required, on the same blockchain as the wallet. It cannot be the address of the wallet itself, nor the address of a KemyCard collect wallet.
  • Always attached to a customer, like every wallet: you know who paid.

Fees and example

Amount sent = balance forwarded − commission of your plan − network fee. Example on Découverte: your customer sends 100 USDC on Solana. The commission is $1 + 1% = $2, the network fee $0.50: **$97.50** are sent to your address. On Premium, the same 100 USDC give $0.25 + 0.35% = $0.60 of commission and $98.90 sent. If the fees would be equal to or higher than the balance (for example after a fee change), nothing is forwarded: the balance keeps adding up until the forward is worth it.

Create a collect wallet

balance is the amount received and not forwarded yet. Calling again with the same customer, blockchain, reference and destination_address returns the same wallet (200), at no cost.

Follow the forwards

A forward is processing, then completed. On Base it is completed when the transaction is sent on the blockchain; on Solana, when the blockchain has confirmed it. If a forward cannot be completed automatically, you receive wallet.forward_failed and our team handles it: a forward is never sent twice. GET /wallets/balance includes the pending balances of your collect wallets.

Change the destination address

The new address applies to every forward created from now on; a forward already created keeps its address. Each change sends the wallet.destination_updated webhook (previous and new address) and an email to the email address of your account. Like every call, it requires your API key and one of your allowed IP addresses: a stolen key alone is not enough.

What a collect wallet does not do

  • No manual withdrawal. POST /wallets/{code}/withdrawals answers 422 on a collect wallet: its balance is always forwarded automatically.
  • No virtual account. A collect wallet cannot be the destination of a virtual account, as a wallet or as an external address.
  • No other currency. Only USDC on the blockchain of the wallet is credited.
Wrong currency or wrong network: the funds are considered lost. A token other than USDC, or USDC sent on another blockchain, is not credited and not forwarded. Tell your customers clearly which network to use. You can write to hi@kemycard.com: our technical team will try to recover the funds when it is possible, with no guarantee.
Check destination_address before you send it. A forward is a blockchain transfer: it cannot be cancelled or reversed. Funds sent to a wrong address are permanently lost.

Supported networks

Create a wallet

Display address to your customer, together with the blockchain and the currency. The wallet is created during the call: the address in the response is ready to receive funds. KemyCard sends no email when a wallet is created, neither to you nor to your customer: you stay in control of how the address is presented.

Rules to know

  • Every plan. Standard and collect wallets are available on every plan, Découverte included. The fees below depend on your plan: see Plans and Pricing.
  • 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 ($1 for a standard wallet, $0.50 for a collect wallet) 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. On a standard wallet, a fee is taken from each deposit before it is credited to the balance of the wallet (no deposit fee on a collect wallet). The wallet.deposit_received webhook gives the amount sent, the fee and the net amount credited.
  • Withdrawal fees. A withdrawal from a wallet carries the commission of your plan, plus a fixed network fee that depends on the blockchain. After these fees, a withdrawal must leave you at least $10. Both are 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.
A wallet only accepts its own currency on its own blockchain. Tell your customers clearly which network to use: funds sent on another network or in another token are not credited.

One-time addresses

A permanent address is ideal when a customer pays you again and again. Sometimes you want the opposite: a fresh address for each payment, used once and then replaced. Add a reference of your choice and you get a new address for the same customer, on the same blockchain:
  • 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 the balance of that wallet and attributed to the same customer.
The creation fee applies to each new address.

Retrieve wallets

The same list is available in the Wallets section of your partner dashboard, with a filter per blockchain.

Follow deposits and your balance

Use the webhook to react in real time, and GET /wallets/deposits to reconcile: every deposit carries its tx_id, the amount sent, the fee and the net amount credited to the wallet.

Test it first

With a sk_test_ key, POST /wallets returns a demo wallet with a fake address (for a collect wallet, the network and the destination_address are checked as in live mode), POST /wallets/{code}/withdrawals returns a demo withdrawal, GET /wallets/forwards a demo forward and PATCH /wallets/{code}/destination the wallet with its new address: nothing is created, debited, sent or charged. Never send funds to an address returned in test mode.

Next steps

Create a Wallet

Full reference of the endpoint

Withdraw from a Wallet

Full reference of the withdrawal endpoint

Change a Destination Address

Where the forwards of a collect wallet go

Webhooks

Wallet events sent to your server