merchant guides/ 8 min read

how to accept xrp payments

~4-second deterministic finality for fractions of a cent — how XRP compares, destination tags explained, and a worked exporter example.

How to Accept XRP Payments
share whatsapp post

The XRP Ledger was built for payments before 'crypto payments' was a category: transactions reach deterministic finality in about four seconds and cost fractions of a cent, with no mining and no fee auctions. For a merchant, that means the money either arrived, finally, or it didn't — there is no probabilistic waiting game.

This guide covers what deterministic finality actually buys you, the one XRP-specific concept every merchant must understand (destination tags), a worked cross-border example, and a non-custodial setup where every payment lands in a wallet only you control.

why XRP for payments

Most chains give you probabilistic finality — a payment becomes less reversible with each block, and you choose how long to wait. The XRP Ledger closes a ledger every few seconds by validator consensus, and once a transaction is in a validated ledger, it is final. Full stop. For merchant operations this is delightfully boring: no confirmation policy debates, no 'wait longer for larger amounts' tables.

Add fees of fractions of a cent and you get a rail that suits invoices of any size — the network cost is identical whether the payment is $5 or $50,000.

finality compared

What 'the money is yours now' looks like across rails:

railfinal inhow finality worksnetwork fee
XRP Ledger~4 secondsdeterministic — validated ledger is finalfractions of a cent
Solana~1–2 secondsfast probabilistic, quickly rootedfractions of a cent
Bitcoin~10 min – 1 hourprobabilistic, deepens per blockoften under $1
card paymentmonthsauth is instant, chargebacks reverse it later1.5–3.5% to the merchant

wallet setup — and destination tags, explained

Use a self-custody wallet that supports the XRP Ledger (Xaman — formerly Xumm — is the ecosystem standard; Trust Wallet and major hardware wallets also support XRP). Two XRPL-specific things to know:

First, destination tags. Exchanges receive all customers' XRP at one shared address and use a numeric tag to route deposits internally. As a merchant receiving into your own wallet, you don't need tags — which is exactly the point: your address is yours alone. But if you ever pay suppliers at an exchange, omitting their tag can strand the funds in support tickets.

Second, the base reserve: the ledger requires a small XRP balance (currently 1 XRP) to keep an account active. Fund your receiving wallet once and forget about it.

a worked example: the exporter

An exporter invoices an overseas buyer $12,000. By SWIFT wire: $30–60 in bank charges, a 1–3% FX spread hidden in the rate, and 2–5 business days — during which the goods wait and the deal can wobble. Intermediary banks sometimes take their own cut en route.

The same invoice in XRP: the buyer pays from their wallet, the network fee is a fraction of a cent, and the funds are final in the exporter's own wallet about four seconds later — with an on-chain receipt both sides can verify. On a non-custodial page the platform fee is 0%; the exporter converts to stablecoins or fiat on their own schedule, not a processor's.

pricing and volatility

XRP is a volatile asset, so price the sale in your currency and let the payment page convert at payment time with a short locked quote — the customer pays an exact XRP amount and drift never becomes a dispute. What you do after settlement (hold, convert a portion, sweep to cold storage) stays your decision on a non-custodial rail.

confirmation policy

This is the easiest section of any coin guide: there is nothing to configure. A validated XRPL transaction is final, so a good gateway marks the order paid the moment the ledger containing it validates — about four seconds after the customer hits send. crypt.pe watches the ledger and matches the exact amount to the invoice automatically.

mistakes to avoid

  • Receiving into an exchange address. You'd inherit the destination-tag problem for every single customer payment — receive into your own wallet and tags become irrelevant.
  • Confusing XRP with wrapped or exchange-listed lookalikes on other chains. Real XRP settles on the XRP Ledger; your payment page should be watching the XRPL, nothing else.
  • Forgetting the base reserve. A brand-new wallet needs its small activation balance (currently 1 XRP) before it can receive.
  • Quoting XRP amounts by hand. Always quote fiat and let the page lock the conversion at payment time.
  • Skipping the test payment. One small test validates address, ledger detection and the receipt in four seconds flat.

go-live checklist

  • 1. Create a self-custody XRPL wallet (Xaman or hardware); back up the seed on paper.
  • 2. Fund it with the small base reserve so the account is active.
  • 3. Paste the public r… address into your payment page and enable XRP.
  • 4. Send yourself a small test payment and check the receipt.
  • 5. Put the link on invoices, your site and the printable QR standee.

frequently asked

How do I accept XRP payments as a business?

Add your public XRPL wallet address to a non-custodial payment page, share the link or QR, and payments settle directly to your wallet with ~4-second finality. With crypt.pe there's no KYC to start and 0% platform fees.

What is a destination tag and do I need one?

Destination tags are numeric routing codes exchanges use because all their customers share one deposit address. Receiving into your own self-custody wallet, you don't need one — your address is exclusively yours. Only worry about tags when sending to an exchange.

How fast do XRP payments confirm?

About four seconds to deterministic finality — once the ledger containing the transaction validates, the payment is final, whatever the amount. Network fees are fractions of a cent.

Is accepting XRP safe for merchants?

Validated XRPL transactions are final — no chargebacks. Keep it non-custodial (funds go straight to your own wallet), protect your seed phrase, and enable 2FA on your account.

ready to accept crypto?
free page, 0% fees, live in 60 seconds — non-custodial by design.
create your free page
about crypt.pe

Non-custodial by design. Payments settle wallet-to-wallet on-chain, straight from the payer to your own wallet. crypt.pe never holds, freezes or forwards funds — there is no platform balance and no withdrawal step, and every payment gets a verifiable on-chain receipt.

0% transaction fees. Plans are flat subscriptions with a free tier — compare that with the 1–2% charged by custodial processors. One page accepts Bitcoin, USDT, Ethereum, Solana and 20+ coins across 13 chains, with simple pricing and no payout schedule.

Tools merchants actually use. Exact-amount invoices with live tracking, product links, printable QR standees, HMAC-signed webhooks, CSV exports and a Stripe-style API — see the merchant guides or create your free page in about a minute.

How a payment works. You add wallet addresses you already own, share your crypt.pe link or QR code, and the customer pays from their own wallet. crypt.pe locks the amount at invoice time, watches the chain, matches the transaction and issues a receipt both sides can verify on a block explorer — software around the payment, never in the money flow.

Works everywhere by default. Because settlement is on-chain to your own wallet, there is no country list, no bank partnership gating access and no account that can be closed over geography. Merchants use crypt.pe across India, the UAE, Nigeria, the Philippines, Brazil and 100+ other markets — see the country guides.

Stablecoin-first, volatility optional. Accept USDT or USDC and a $100 invoice is still worth $100 when it is paid — no price risk in between. Prefer BTC, ETH or SOL? Amounts are locked at invoice time either way, and your dashboard records the USD value of every payment for clean bookkeeping. Questions? Start with the FAQ or payment help.