How do I accept XRP payments from customers?

Accepting XRP works like accepting any coin: the customer sends it to an address, and you watch it arrive. Three things set XRP apart:

• A locked minimum. The receiving wallet has to keep at least 1 XRP that you can never spend.
• Destination tags. Many payments carry a number that says whose payment it is, and a customer can forget to enter it.
• A near-zero fee. A payment costs a tiny fraction of a cent and settles in seconds.

To begin, you choose one of two paths:

• Your own wallet. Customers send XRP straight to an address you control, and you match payments to orders yourself.
• An XRP payment gateway. A service takes the payments for you and marks each order paid.

Below we go through what makes XRP different, then both paths step by step.

A word on names first. People say "Ripple" for the coin and for the network, but the three names mean different things:

• Ripple is a company.
• The XRP Ledger is the network.
• XRP is the coin.

Checkouts and exchanges use all three, so a payment window that says "Ripple" means XRP on the XRP Ledger.

What makes accepting XRP different from other coins

XRP lives on its own network, the XRP Ledger: a shared record of who owns how much XRP, kept in step by independent servers around the world. If that sentence is where crypto stops making sense, start with what cryptocurrency is and how a blockchain keeps its records.

The XRP Ledger has its own rules, and four of them matter to a business taking payments:

• A wallet keeps a locked minimum. Every XRP address has to hold 1 XRP in reserve, and a brand-new address does not exist on the network until someone sends it at least that much.
• One address often serves many people. An exchange can serve thousands of customers from a single XRP address and tell them apart by destination tags, so your customers will meet tags, and you may too.
• The network fee is tiny and paid by the sender. A standard payment costs 0.00001 XRP, and the network destroys that fee instead of paying it to anyone.
• Payments are final in seconds. The XRP Ledger confirms a new batch of transactions every 3–5 seconds, and a confirmed payment cannot be reversed.

The reserve is the reason tags exist. On Ethereum a new address costs nothing to create, so a payment service can give every customer their own. You can see that model in how the Ethereum network works and how businesses accept ETH.

On the XRP Ledger the same model is expensive. A service with 10,000 customers would lock 10,000 XRP by giving each one an address. One address plus a tag per customer locks a single reserve.

What a destination tag is, and what happens when a customer leaves it out

A destination tag is a number of up to ten digits attached to an XRP payment. It tells the receiver whose money this is. Think of the address as a building and the tag as the flat number.

A business runs into tags in two situations:

• You receive on one address and give each order its own tag. The customer must type that number when sending. If they leave it out, the XRP still reaches you, but nothing says which order it pays, so you match it by amount and time or write to the customer.
• You receive XRP into your account at an exchange. The exchange gives you its shared address and your personal tag. A payment without your tag lands in the exchange's common pool, and getting it credited means writing to the exchange's support and waiting. We don't recommend taking customer payments this way.

If you receive on your own address, you can switch on a setting called "require destination tag". The network then rejects any payment without a tag, and the XRP stays with the customer, who can send it again with the right number. A bounced payment is easier to sort out than money you cannot place.

Some wallets accept an X-address, a single string that packs the address and the tag together. Not every wallet and exchange reads it, so showing the address and the tag as two separate lines is the safer default.

How much XRP has to stay in the wallet that receives payments

The minimum XRP in the wallet is 1 XRP. This base reserve has stood at 1 XRP since December 2024, when the network's validators lowered it from 10. On top of it, the address sets aside 0.2 XRP for most extra things it keeps on the ledger, such as an open order on the ledger's built-in exchange or an escrow. A wallet that only receives XRP needs just the 1 XRP.

The reserve stays locked for as long as the address exists. If your wallet has received 250 XRP, you can send out at most 249, minus the network fee. Wallet apps usually show that 1 XRP as reserved or unavailable.

Two consequences for a business:

• A fresh address needs funding before customers use it. Until it holds 1 XRP, the address does not exist, and a customer's payment of less than 1 XRP to it fails. Send it one or two XRP yourself before you publish it.
• The figure can change. Validators vote on the reserve, and it has been lowered before. Your wallet shows the current number.

What an XRP payment costs, and how fast it arrives

The transaction fee for a standard XRP payment is 0.00001 XRP. The sender pays it, and it rises only when the network is congested. At any price XRP has traded at, that is far below a cent.

So the network fee is not the cost to watch. Two others are:

• The exchange's withdrawal fee. A customer paying from an exchange pays that exchange's own charge for sending XRP out, and it is far larger than the network fee. Some exchanges take it out of the amount sent, so an order for 50 XRP can arrive a little short.
• The gateway's fee. If an XRP payment gateway takes the payment for you, it charges its own percentage of each payment.

Those layers work the same way on every network, and how crypto payment fees work, from network fees to gateway charges shows how they add up.

The transaction time is 3–5 seconds. One confirmation is final, so there is no waiting for several confirmations the way there is with bitcoin. When a customer does wait, the delay is usually on their side: some exchanges hold a withdrawal for a security check before sending it.

How to begin: your own wallet or an XRP payment gateway

Accepting XRP comes down to the same two paths as accepting any coin. The general comparison, with what each costs, is in how to accept bitcoin and other crypto on a website. Here is what each path looks like with XRP.

Path 1: customers send XRP to your own wallet

This path needs no payment processing and no contract. Setting it up takes five steps:

1. Choose a wallet that supports the XRP Ledger and that you control. You hold the recovery phrase: nobody can freeze the wallet, and nobody can restore it if you lose the phrase.
2. Fund the new address with at least 1 XRP. Until the reserve is in, the address does not exist, and customer payments to it fail.
3. Decide how to tell payments apart. Give each order or regular customer its own destination tag, for example the order number 10452, and switch on "require destination tag" if the wallet offers it.
4. Send the customer the address, the tag and the exact amount in XRP. Warn them that on some exchanges the tag field is labelled "Memo" or "Tag/Memo", and that it still has to be filled in.
5. Check each payment on an XRP Ledger explorer and mark the order paid yourself. An explorer is a public website where anyone can look up an address and see every payment it received.

The price of this path is your time. The work that stays with you:

• Pricing. You work out how many XRP a $40 order costs at today's rate.
• Matching. You tie every incoming payment to its order.
• Chasing. You write to the customers who forgot the tag.

The coin's price also moves while you hold it. A business that prices in dollars either converts XRP soon after it arrives or accepts the swing. A common way out is a dollar stablecoin; what USDT is and how businesses accept Tether explains that coin.

Nobody checks who sent the money, either. Screening incoming funds is its own job, covered in securing crypto payments with AML checks and wallet screening.

Path 2: an XRP payment gateway

An XRP payment gateway is a service that takes the payment on your behalf, and the reserve and the tags become its problem. A payment through a gateway goes like this:

1. The gateway prices the order in XRP. It converts your dollar total at the current rate.
2. The gateway shows the customer where to send the XRP. The customer sees an address, and a tag if the gateway uses one.
3. The gateway watches the XRP Ledger. It spots the incoming XRP payment within seconds.
4. The gateway tells your system the order is paid. Your shop or your inbox gets the confirmation.

Gateways give the customer a destination in one of two ways:

• A shared address plus a tag for this payment. It works, but the customer can still skip the tag.
• An address for this payment alone. The customer has no tag to forget.

You can use a gateway in three ways, and all three are the same gateway underneath:

• Payment links. You create a link for an amount and send it in a chat or an email, with no website needed.
• A button on your site. The customer either enters an amount themselves, or your server passes in the exact order total.
• The API. Your developer connects the gateway to your own checkout, so invoices are created and marked paid automatically.

If XRP is going into an online store, it is worth knowing what actually changes when an online store accepts crypto.

A payment gateway usually charges a percentage of each successful payment. The rate often falls as your volume grows, and some gateways let you pass the fee on to the customer. What crypto payment processing costs a business goes through what to compare.

CryptumPay is one such gateway, and it offers all three ways: payment links from its console, a checkout widget button and an API. When a customer picks XRP, the CryptumPay checkout labels the network "Ripple" and shows an address issued for this payment, with no separate tag field. Whatever coin the customer pays in is converted to USDT on arrival, so the merchant's balance is always in USDT; the fee is 1% per successful payment, down to 0.5% at higher volumes, and it can be passed on to the customer.

Where customers go wrong when paying in XRP

An XRP payment cannot be recalled, so a mistake on the customer's side becomes a conversation with you. The usual slips are these:

• Wrong network. Some exchanges and wallets hold versions of XRP on other networks. An XRP Ledger address starts with "r"; if the customer's wallet asks for an address starting with "0x", they are on the wrong network.
• Missing tag. The customer skipped the tag field, often because the exchange called it "Memo". With your own wallet you then have a payment without an order.
• Short amount. The exchange took its withdrawal fee out of the sum, and 49.8 XRP arrived instead of 50.
• Late payment. A gateway invoice usually lives for a limited time, and XRP sent after it closes lands on an expired invoice.

A refund in any of these cases is a new transfer from you to the customer, not a reversal.

Which path fits your business

The choice follows from how many payments you expect:

• Your own wallet suits a handful of XRP payments a month, where matching each one by hand takes minutes and nobody minds the price swing.
• An XRP payment gateway suits regular orders, a website checkout or anyone who wants dollar-stable money on the balance, at the cost of a percentage per payment.

Whether XRP belongs in your checkout at all, next to USDT or bitcoin, is a separate decision; the top coins for accepting crypto payments and how to pick them helps with that.

What it comes down to

The XRP network itself is cheap and settles in seconds. Accepting XRP means minding three things other coins don't ask of you:

• The reserve. 1 XRP stays locked in the receiving wallet.
• Destination tags. Shared addresses need a tag, and a payment without it has no owner.
• Exchange forms. Customers pay from exchanges that name the tag field their own way.

Take XRP into your own wallet if payments are few and you are ready to match them by hand. Take it through an XRP payment gateway if you want orders marked paid automatically and the reserve and tags handled for you.

Frequently asked questions

What is the difference between a destination tag and a memo on XRP?

A destination tag is a single number that the XRP Ledger itself knows about, and an address can require it. A memo is free-form data attached to a payment, such as a note or a reference, and the ledger never checks it. Exchanges route deposits by the tag, even when their withdrawal form calls that field "Memo".

What is the smallest amount of XRP a customer can send?

The XRP Ledger counts XRP down to 0.000001 XRP, so technically that is the floor. A payment to an address that does not exist yet must be at least 1 XRP, because it has to cover the reserve. In practice, exchanges and gateways set their own minimums, which are much higher.

Can a customer pay in XRP from MetaMask?

Not out of the box: MetaMask is built for Ethereum-style networks, and the XRP Ledger is not one of them. With the XRP Ledger Snap, an add-on installed inside MetaMask, the wallet can hold and send real XRP. Without it, any "XRP" the customer sees in MetaMask is a token on another network and will not reach an XRP Ledger address.

What are XRP payment channels?

A payment channel is XRP set aside by the payer, against which they sign small claims that the receiver can check instantly without touching the ledger. The receiver later cashes all the claims in one transaction. Channels suit streams of tiny payments, such as paying per second of video; a shop taking ordinary orders does not need them.

Which payment gateways support XRP?

Many crypto payment processors take XRP, but not all, so check the list of coins before signing up. Then ask any of them three questions:

• Own address or shared? Does the checkout give each payment its own address, or a shared one with a tag?
• What about a missing tag? What happens to a payment that arrives without it?
• Converted or kept? Is the XRP converted on arrival, or does it stay XRP on your balance?