Bitcoin was the first checkout asset and still the one customers ask for by name. On U.CASH Pay, accepting it means adding BTC to your checkout assets and deciding two things: whether to take it on-chain or over Lightning, and whether to keep it as BTC or auto-convert receipts into a stablecoin. This guide sets up both.
Every step, in order.
In your Pay settings, add Bitcoin to the accepted assets. Customers paying by crypto see it alongside whatever else you accept.
On-chain BTC settles with normal confirmations; Lightning settles near-instantly for smaller tickets. You can enable both and let the customer's wallet pick.
Hold receipts as BTC, or set an auto-conversion rule into a stablecoin pegged to your invoicing currency. The conversion executes at checkout rate.
Checkout quotes the BTC amount live from the customer's side. Your prices stay in your local currency; the crypto amount is derived at payment time.
The dashboard lists each payment with its transaction reference and settlement state. Reconciliation data flows to your accounting export either way.
Swap BTC to a local rail through the payout flow, or hold. Settlement is non-custodial: the bitcoin is in your wallet from confirmation.
The hold-vs-convert decision is the real one. Holding BTC means your revenue carries bitcoin's price volatility between receipt and spend. Auto-converting into the stablecoin matching your invoicing currency removes that exposure at the cost of the conversion fee and the forgone upside. Merchants with fiat costs mostly convert; merchants who already transact in crypto mostly hold. Both are first-class settings, changeable at any time: nothing is locked in.
Accept Bitcoin, Ethereum, stablecoins and 53 more assets at checkout in minutes: connect…
Swap any asset for any other across 35 networks: connect a wallet, pick the pair, review…
Three ways to get UCASH, the U.CASH network token: card or bank through the partner ramp,…
Six guides, one platform, every rail non-custodial.