Accept Crypto Payments Without the Custody Burden

You can take crypto payments for your business without running wallets, watching the chain, or holding customer funds. Create an invoice, share a checkout link, get settled, and read it all in one cabinet.

Accept Crypto Payments Without the Custody Burden

You can accept crypto payments for your business without holding wallets, watching the blockchain, or taking custody of customer funds. You create an invoice, share a checkout link, the buyer pays, and you get settled. The balance, the refunds, and the payment events all live in one merchant cabinet. The operational weight that usually makes crypto scary stays off your desk.

That is the whole pitch. Below is what each step actually looks like, and the few places people trip.

What "custody burden" actually means

Most teams who try crypto once end up not running the payment. They end up running an ops job. Someone has to generate an address, watch the chain for the deposit, count confirmations, reconcile what landed against what was owed, handle the buyer who sent the wrong amount, and keep the keys safe forever. That is custody. It is real work, and it does not stop.

The alternative is to treat crypto the way you already treat card payments: you state the price, the customer pays, the money shows up as a balance you can read. You should not have to think about blocks, confirmations, or key storage to sell a thing.

How it works, step by step

  1. Create an invoice. You name the amount and what it is for. You get a checkout link tied to that invoice.
  2. Share the link. Send it in an email, a chat, a button on your site, or a QR code at a counter. The buyer opens it and sees one clear page: what they owe and how to pay it.
  3. The buyer pays. They send the amount shown. The checkout page tells them when it is received. Nobody has to screenshot a transaction to you.
  4. You get settled. The payment lands as a balance in your cabinet. You see the rate before anything moves, and the exchange fee is shown plainly, not buried.
  5. You read it back. Every payment, its status, and your running balance sit in one place. Refunds and payment events are right there too.

That is the full loop. You did not generate an address, you did not count confirmations, and you never held a private key.

What you get

  • A fast start. An invoice and a link are enough to take your first payment. No node, no wallet setup, no chain-watching service to babysit.
  • A clear balance. What you are owed and what you have settled read like a normal ledger, in amounts you can trust, not floating-point guesses.
  • Refunds. When you need to return a payment, you do it from the cabinet with a record of who, what, and when.
  • Webhooks. Your systems can be told the moment a payment changes state, so an order can ship or a license can unlock without anyone refreshing a tab.
  • One place to look. Marketing site, dashboard, and payment history all answer the same question the same way: what happened, and where is my money.

What can go wrong, and how to avoid it

The buyer sends the wrong amount. This is the classic crypto headache. The checkout link states the amount to send. Tell buyers to pay the amount shown rather than rounding it themselves, and most of this disappears.

You promise a fiat price and forget the rate moves. Crypto prices move between "add to cart" and "paid." You see the rate before the payment is taken, so quote from what the checkout shows, not from a number you wrote down an hour ago.

You wire webhooks but skip verification. Webhooks are how your backend learns a payment is done, so it is tempting to trust the first request that arrives. Don't. Verify the request before you act on it, and treat amounts as integer minor units, not decimals, so rounding never costs you money. A short developer guide covers the exact contract.

You treat it like a bank account. This is a payment rail, not a place to store value long term. Settle, read your balance, and move on. The point is to take money cleanly, not to become a custodian by accident.

Who this is for

A small shop that wants one more way to get paid. A SaaS that needs to unlock access the second a payment clears. A freelancer who would rather send a link than chase a bank transfer. If you can write an invoice, you can take a crypto payment. You do not need a crypto team.

See how it fits your checkout on our business page, check the fees before you commit, and reach a real human at support (we answer at @swappsy) if you want a hand getting the first invoice out the door.

Next step

Turn this into action

Use the related SwapSS Pay docs before you build or test an integration.

Explore SwapSS Pay