XRP is the native currency of the XRP Ledger (XRPL), a public blockchain designed for fast settlement. It has a large base of holders, and payments complete in seconds for a tiny fee, which makes it a comfortable fit for checkout. It also has one quirk every merchant must understand: the destination tag.
What is an XRP destination tag, and why does Payfim use one?
On the XRP Ledger, a destination tag is a number attached to a payment that tells the recipient what the payment is for. Exchanges use it to know which customer to credit. Payfim uses it to know which invoice a payment belongs to.
When a customer chooses XRP at checkout, Payfim shows three things: your r-address, the amount, and a destination tag that belongs to that invoice alone. Because the tag identifies the invoice, the amount does not need to carry a unique fraction the way it does for Bitcoin or Litecoin. It also means that if a customer pays in two parts with the correct tag, Payfim adds them together.
If the customer leaves out the tag, the payment still reaches your wallet, but Payfim cannot tell which order it belongs to and will not mark anything paid. You can check it in your wallet and use Mark as paid manually on the invoice.
To prevent tagless payments entirely, you can turn on the XRPL account setting RequireDest in a wallet that supports it. The ledger will then reject payments to your address that have no destination tag, so the customer's wallet shows an error instead of sending.
Why do merchants accept XRP?
- Speed. The XRPL documentation says new ledger versions usually close about every 3 to 5 seconds.
- Cost. The minimum transaction cost for a standard payment is 10 drops, or 0.00001 XRP. It rises only when the network is under unusual load.
- A distinct audience. XRP holders are a community of their own, and many of them do not also hold Bitcoin or stablecoins.
As with any non-stable coin, the value of what you receive moves with the market.
The 1 XRP reserve: activate your wallet first
An XRP Ledger account only exists once it holds at least the base reserve, currently 1 XRP on mainnet. Until then, a payment smaller than the reserve cannot create the account. In practice:
- Create your wallet and note its r-address.
- Send it a little more than 1 XRP from somewhere you already hold XRP.
- Only then publish it as your receiving address.
That reserve stays locked in the account. Each object the account owns (for example a trust line) adds an owner reserve of 0.2 XRP.
Setting up XRP in Payfim
- In Wallets & coins, paste your address into the XRP row. It starts with
rand is 25 to 35 characters long, for examplerN7n…. - Leave confirmations empty. Payfim only counts transactions in validated ledgers with a successful result, which are final.
- Switch XRP on, click Save wallets, then Test.
No API key is required. Payfim queries a public XRPL server by default; you can set your own under Blockchain APIs → XRPL server.
Payfim reads the amount the ledger actually delivered (the delivered_amount field), not the nominal amount written in the transaction. That closes the "partial payment" trick, where a payment claims a large amount but delivers only a fraction of it.
At checkout, the destination tag appears under your address, labeled "Destination tag (required)", with its own copy button. The QR code contains the address only, so the customer must enter the tag and the amount in their wallet themselves.
Which wallet should I use?
A self-custody XRP wallet, or a hardware wallet with an XRP app, where you control the secret. Payfim needs only the public r-address.
Exchange deposit addresses are a particularly bad fit for XRP. An exchange gives thousands of customers the same r-address and tells them apart by its own destination tag. Payfim puts its invoice tag on each payment, so the exchange has no way to match the deposit to your exchange account.
Common XRP mistakes
- Missing tag from customers paying through an exchange withdrawal form. Ask them to fill in the "tag" or "memo" field. Tip: mention it in your payment instructions.
- Wrong tag copied from an older invoice. Every invoice has its own, so reusing one will not pay a new order.
- Tokens instead of XRP. The XRPL also carries issued tokens. Payfim's XRP option counts XRP only.
- Unfunded receiving address. See the reserve section above.
A final check before launch: send a small test payment with the tag from a second wallet, then one without it, so you see both outcomes in the invoice list and know what a missing-tag case looks like.
Keep going
Hosting providers using the WHMCS module or Blesta gateway often add XRP for international clients. For underpaid or split payments, see handling underpayments and refunds. Security practices for your gateway are on the security page.
Sources
Third-party facts were checked on the date shown above. Prices and features of other services change - always confirm on their official pages.

