Guide · Merchants, creators, platforms

How to accept crypto payments

Accepting crypto payments used to mean a custodial processor, a payout schedule, and fees nobody could predict. The non-custodial model replaces all three: your checkout watches the chain, your wallet receives every payment directly, and the platform in the middle never holds a cent.

This guide walks the whole path: account to first payment to the webhook that tells your systems an order is good. Twenty minutes, no custody, no processor account required.

You needA U.CASH Pay accountA wallet you control (EVM address, Bitcoin xpub, or Solana key)Optionally: a card-processor account for cards

Start now → All guides

Step by step

Every step, in order.

Step 01

Create your account and store

Sign up at pay.u.cash and create a store: name, branding, and the currency you price in. The store is the container for checkouts, orders, and settings.

Step 02

Connect your wallet

Add the addresses you want paid: an EVM address covers every Ethereum-network asset, a Bitcoin xpub generates fresh addresses per invoice, a Solana key covers Solana assets. You hold the keys; U.CASH only watches.

Step 03

Set your confirmation policy

Decide what counts as paid per asset: one confirmation for small tickets on fast chains, full finality for large ones. Defaults are sensible per chain; the checkout shows buyers exactly what to expect.

Step 04

Pick your assets and rails

Enable any of the 56 crypto assets, add custom tokens on 23 token networks by contract, and optionally turn on cards through your own Stripe, Verifone, or PayPal account and the local bank rails.

Step 05

Share the checkout

Publish a Pay-Now link, embed the universal checkout in your page with a snippet, or create checkouts server-side through the API. QR codes render from any link for in-person sales.

Step 06

Receive and confirm

Buyers pay from any wallet; the checkout watches the chain against your policy and flips to paid the moment it is met. Funds settle straight to your wallet, never to the platform.

Step 07

Wire the webhook

Register a signed webhook endpoint and your inventory, fulfillment, and ledger update themselves: no polling, no manual reconciliation, cryptographic proof on every event.

The part that matters

The two decisions that shape everything downstream are the wallet and the confirmation policy. The wallet decides custody: an xpub on Bitcoin means every invoice gets a fresh address (better privacy, no address reuse), while a single EVM address means one reusable destination across every EVM asset. The policy decides risk: the gap between one confirmation and full finality is the window where a sophisticated attacker could theoretically double-spend, so price it against your ticket size the way you would price any fraud exposure.

Go deeper

FAQ

Do I need a bank account or processor to start?

No. Crypto-only checkouts need just a wallet. Cards and bank rails are optional additions: cards run through your own processor account, and the manual bank rails publish your existing coordinates.

What happens if a buyer underpays?

The checkout detects the shortfall, shows the remaining amount, and holds the order open. The buyer tops up the difference or the order expires on your terms: nothing is lost or silently mismatched.

Can I price in dollars and receive crypto?

Yes: price the invoice in your currency and accept any enabled asset; the checkout handles the conversion at payment time, and the pegged stablecoins let dollar-priced invoices settle with no FX step at all.

Keep going