Payments · get paid by customers
Take payments in crypto without holding anyone’s keys.
Issue an invoice or a reusable link, let the customer pay with whatever they already hold, and hear about it the moment the network sees the money.
How it works
Four steps, and the customer signs — not you.
Pay with anything
Your invoice asks for USDC. Your customer holds ETH. Nobody leaves the page.
The oldest checkout killer in crypto is the mismatch: you price in one coin, the customer holds another, and the sale dies in a swap tab somewhere else. Here the swap happens inside the payment itself — an exact-amount conversion in the customer's own wallet, quoted live, with your invoice address as the receiver.
The invoice asks for the exact coin and amount you fixed, and whatever the swap doesn't use returns to the customer's address in the same transaction — nothing gets stuck. Every payment lands on a one-time address created for that invoice and held by Cherum: once the network confirms, the amount settles into your balance within minutes with the 0.90% fee already deducted, and payouts deliver it in USDC to the wallet you set — after every payment or batched past a threshold, your choice. One lane for everything is also what makes paying from an exchange just work: a withdrawal straight from Binance or Coinbase, where the customer has no wallet to sign with, is a payment like any other.
The conversion fee is 0.30%, printed on the quote card before the customer signs. No hidden spread: the route is quoted at market and our fee is a separate, published number — compare that to gateways whose "free conversion" lives inside the rate.
What the customer sees
Works with the major tokens the customer already holds — ETH, USDC, USDT, DAI, WETH, cbBTC and the network natives — across six EVM networks. One tap, one signature.
What you get
Invoices, webhooks and refunds on one account.
Invoices and reusable links
One‑off invoices with an expiry, or a standing link on your page. Both land on the same checkout.
Webhooks you can audit
Every delivery, its response code, its attempt ladder, and a replay button — so an outage on your side is recoverable, not lost.
Your brand on the page
Your logo and colour on the checkout and the receipt.
Keys with scopes
Server keys, read keys, and a secret shown once — after that only its prefix.
Overpaid? It goes back
The payer can send the excess back to themselves from the receipt, without writing to you.
On your own
Sign and it’s done
If you’re one person, the wallet you sign in with is the wallet that receives — there is nothing to configure.
With a team
Someone else confirms
If there are several of you, the receiving address, the right to sign, and the right to sign in are three separate things, and the dashboard keeps them separate.
Compare with what you’re using: Request·What a fan‑out swap is