# Accept crypto payments

> Let buyers pay in USDC or USDT from their own wallet, beside card. It's off until you turn it on, and the money goes to your payout wallet.

Source: https://railbed.com/docs/user-guide/crypto-payments/ · Updated: 2026-10-05 · Railbed by DeepWork user guide

For AI assistants: the index of every docs page, with the rules for an integration, is https://railbed.com/docs/llms.txt

## How it works

Card stays the main way to pay. When you turn crypto payments on, your checkout pages, payment links and store checkouts show a **Card | Crypto wallet** switch, with Card selected. A buyer who picks **Crypto wallet** enters their email, chooses a coin and network, and sends the exact amount to a one-time address shown with a QR code. The page updates when the money arrives, and the payment settles to your payout wallet like a card payment.

Buyers can send:

| Coin | Networks |
|---|---|
| USDC | Polygon, Base, Arbitrum, Optimism, BNB Chain, Ethereum |
| USDT | Polygon, Base, Arbitrum, Optimism, BNB Chain, Ethereum |

One coin counts as one US dollar. An order only offers the networks it can use: each network has a minimum, and networks that cost more to forward (Ethereum and Base) only appear on larger orders, so the network cost never takes much of your payment.

## Before you turn it on

Crypto payments arrive at your payout wallet on whichever network the buyer used. Your wallet must be a **self-custody wallet** (one where you hold the recovery phrase, such as MetaMask, Rabby, Trust Wallet or a hardware wallet). The same address then works on every network above.

> [!WARNING]
> Don't turn crypto payments on if your payout wallet is an exchange deposit address. An exchange may not credit money sent on a network it doesn't support for that address, and it can be lost.

## Turn it on

1. Open **Settings** and find **Crypto payments**.
2. Turn it on, and confirm your payout wallet is a self-custody wallet that works on every network.
3. Your checkout pages, payment links and store checkouts now offer **Crypto wallet**.

If you change your payout wallet later, you confirm the new one the same way.

To keep one checkout card only, open it, and turn off **Accept crypto**.

## Fees

Crypto payments have their own Railbed fee, shown in **Settings**, usually lower than the card fee. It's taken from what arrives, the same way as for card payments, together with the network cost of forwarding the money to your wallet.

## Short and late payments

The buyer must send the full amount. A payment that arrives at least 99% complete counts as paid. Less is marked **Underpaid**, and you decide what to do from the payment, as for any [held payment](https://railbed.com/docs/user-guide/held-payments.md). A second, separate transfer isn't added to the first.

Money that arrives after the checkout closed still settles, as with card.

## Test mode

In Test mode the address is an example: never send real funds to it. Use **Simulate payment** or **Simulate underpayment** on the page to see what your buyers and your dashboard show.

## In the dashboard and integrations

A crypto payment reads like **Crypto · USDC on Base** in Payments, Orders and alerts, with links to that network's block explorer. Webhooks and the API say `method: crypto` and name the `network` ([payment fields](https://railbed.com/docs/api/payments.md), [webhook fields](https://railbed.com/docs/webhooks/events.md)). Crypto addresses can't be created through the API yet: an API checkout session offers crypto on its hosted payment page.