XRP settles in three to five seconds and costs a fraction of a cent. This makes it one of the few coins that is actually built for moving money around, rather than holding it. Two things have changed recently that matter to a business. The legal case between the SEC and Ripple finished in August 2025. This means that the legal problem that stopped XRP being used on some platforms for five years is now over. Ripple also launched RLUSD, a dollar stablecoin on the same ledger. This means you can combine a stable asset and a fast bridge currency.
One operational warning before anything else, because it costs merchants real money: XRP sent to a shared address without a destination tag doesn't just get delayed. It gets lost. Permanently. There's a section on this below, and it's the single most important thing on this page.
What is XRP, and how does the XRP Ledger work?
XRP is the native asset of the XRP Ledger, a blockchain that launched in 2012 and never used mining. Instead of proof-of-work, it uses a consensus protocol where a set of validators agree on the order of transactions every few seconds. There are no miners, no gas auctions and no need to wait for block confirmations to stack up.
Here are some practical numbers: transactions settle in 3 to 5 seconds and cost about 0.00001 XRP, a fraction of a cent, well under $0.001. Those figures barely move under network load, which is unusual, since most chains get expensive just when everyone wants to use them.
Ripple built the necessary infrastructure for cross-border payments, and that's where XRP comes in. It acts as a bridge between currencies, so you can settle a cross-border payment without pre-funding accounts in each destination currency. Ripple's payments network connects financial institutions across dozens of countries, some using XRP for on-demand liquidity in cross-border corridors. (Ripple has since consolidated this under the Ripple Payments brand.)
Is XRP legal now? What the SEC case settled
For five years, this question stopped businesses from dealing with XRP. It's settled.
In December 2020, the SEC took legal action against Ripple, claiming that XRP sales were not registered with the relevant authorities. In July 2023, Judge Analisa Torres decided the case. XRP sold on public exchanges to retail buyers is not a security, but some sales to institutions were. The case went on for a long time until both sides decided to withdraw, and it was officially closed in August 2025. Ripple had to pay a $125 million penalty.
What that means for you as a merchant. XRP traded and received on secondary markets carries no securities classification in the US, which is more legal certainty than most tokens have. Exchanges that had delisted or restricted XRP relisted it. Spot XRP ETFs were approved and launched. Institutional money that sat out the litigation started allocating.
It's a nuanced outcome rather than a blanket win, since the ruling turned on how XRP was sold rather than declaring it categorically one thing or another. But for a business receiving XRP as payment, the relevant part is clear: you're accepting an asset whose retail status a federal court has already ruled on.
The regulatory picture firmed up further in 2026: Ripple secured MiCA authorisation to operate as a regulated crypto-asset service provider across the European Economic Area, adding EU clarity on top of the US ruling. The court did find certain direct institutional sales violated securities law, and an injunction on those specific sales stood.
Destination tags: how not to lose an incoming XRP payment
This is where merchants lose money, and most guides skip it entirely.
The XRP Ledger has a design feature that trips people up. Exchanges and custodial services use one shared XRP address for thousands of customers, and they tell those customers apart using a destination tag, a number attached to the transaction. Send XRP to such an address without the tag, and the receiving service has no way to know whose money it is.
Sometimes support can recover it. Often they can't, and the funds are gone permanently.
What this means when you're accepting XRP
Use a unique address per customer if you can
A gateway typically generates a new receiving address for each invoice, which sidesteps tags entirely. Cleanest solution.
If you must use a shared address, display the tag prominently
Not in small print. The tag should be as visible as the amount and the address, ideally in its own copy-to-clipboard field.
Validate before you accept
Your checkout should refuse to proceed if a required tag is missing, rather than letting a customer send funds into a void.
Explain it in your payment instructions
A single line, "you must include the destination tag or your payment will not arrive," prevents most incidents.
Reserve requirements
One more XRPL quirk worth knowing. Every account on the ledger must have a base reserve of XRP to exist. At the moment, this is 1 XRP, plus a small additional reserve per object like a trust line. It's not a fee; it's collateral that can be recovered if you delete the account. But it means a brand-new XRP address can't be emptied to exactly zero, and your accounting should expect that.
X-address: the format that prevents tag mistakes
An X-address is a newer XRP address format that bundles the classic address and the destination tag into a single string (it starts with an "X"). Instead of asking a customer to copy an address and a separate tag, and hoping they don't skip the tag, you give them one string that already contains both. The wallet reads the embedded tag automatically. For a merchant, this is the cleanest way to eliminate the missing-tag problem: if your processor or wallet supports X-addresses, use them, and the single most common way to lose an XRP payment simply goes away. Most modern XRP wallets and processors, including major custodial services, support the format.
RLUSD: Ripple's stablecoin on the same ledger
Launched in December 2024, RLUSD is Ripple's dollar-backed stablecoin, and it grew past $1 billion within a year, reaching roughly $1.6 billion by mid-2026. It runs on both the XRP Ledger and Ethereum.
Why it matters to a merchant: you can accept a stable dollar asset on the same fast, cheap ledger as XRP, through one integration. RLUSD carries a New York Department of Financial Services trust charter, which puts it among the more strictly supervised US stablecoins, and a pilot announced in late 2025 with Mastercard and WebBank is set to enable card settlement with RLUSD, subject to regulatory approvals.
The sensible pairing is simple. Use RLUSD if you want the value to stay the same. This includes invoicing and subscriptions, and any other situations where the price paid at checkout should be the same as the price agreed. Use XRP when speed and cross-border bridging are important, or just because the customer has it. Ripple positions the two exactly like this: RLUSD is used as settlement value, XRP is used as a bridge asset and to provide liquidity.
How can a business accept XRP payments?
Six routes, differing in setup effort.
Payment gateway
A processor generates the invoice, watches the ledger, confirms the payment, and credits your balance. It handles destination tags, AML screening, and conversion. For anything past occasional payments, this is the route.
API
A REST call creates the payment request, and a webhook confirms settlement. Full control over checkout logic, which custom and headless builds need.
Payment button
One snippet at checkout, customer picks XRP, pays. Works on most platforms that support HTML embeds.
Payment link
A link with the amount preset, sent by email or chat. No website required, useful for invoicing and social selling.
Invoice
A branded invoice with the XRP amount, address, destination tag if needed, and a reference ID. Standard for B2B.
CMS plugin
Shopify, WooCommerce, and others have plugins from various processors. Install, add keys, choose coins.
Ready to accept XRP payments? 0xProcessing is an XRP payment gateway built for business: it handles destination tags, supports X-addresses, converts to stablecoins automatically, and settles to crypto or fiat. Get started →
Setting up XRP payment processing
About a week, mostly verification rather than development.
1. Pick a provider
It's worth checking if they support XRP and RLUSD, if they handle destination tags properly, if they convert automatically if you want that, and if they settle to the fiat you need.
2. Clear KYB
Submit your company documents and ownership details and ensure they're in order. The processor then conducts AML screening on incoming payments rather than subjecting your customers to checks.
3. Set up the payment system
Decide what to do with the incoming XRP. You can keep it as XRP, auto-convert it to a stablecoin, or transfer it to your bank account.
4. Integrate the plugin or API
Create payment, catch webhook, mark order paid. Make sure those destination tags are rendering correctly in your checkout.
5. Test with a live payment
Send a small test payment, including one with a destination tag if your set-up uses them. Just make sure it's all set before opening it up to traffic.
Why accept XRP? The business case
Speed
Three to five seconds to final settlement. A card takes two days to clear, a SWIFT wire takes three, and Bitcoin needs ten minutes per confirmation.
Cost
A fraction of a cent per transaction (the standard fee is 0.00001 XRP), and it stays there under load. Against 2.9% plus 30 cents on cards, plus another 1–3% crossing a border.
No chargebacks
Ledger transactions are final. Nobody reverses a payment months after delivery, which is the biggest saving for digital goods and high-risk sellers.
Built for cross-border
XRP exists to bridge currencies without pre-funded accounts in every corridor. For a business paying suppliers or collecting internationally, that's the design intent, not a side effect.
Regulatory clarity
Post-2025, XRP has a court ruling behind its retail status. Few tokens can say that.
XRP or stablecoins for B2B cross-border?
Both work, and they solve different problems. Here is a quick comparison:
|
XRP |
Stablecoin (RLUSD, USDC, USDT) | |
|
Value stability |
Volatile |
Pegged to the dollar |
|
Speed |
3–5 sec |
Seconds, chain-dependent |
|
Cost |
~0.00001 XRP (fraction of a cent) |
Cents, chain-dependent |
|
Best role |
Bridge asset, liquidity, FX corridors |
Invoicing, settlement, holding value |
|
Counterparty risk |
None (no issuer) |
Issuer risk (Circle, Tether, Ripple) |
|
Regulatory status |
Court-ruled non-security at retail |
Regulated as payment stablecoins |
The way most treasury teams use them: stablecoins for the amount, since your invoice is denominated in dollars and you want dollars at the end. XRP for the movement, where converting through a bridge asset beats maintaining nostro accounts in six currencies.
For a merchant simply taking payment, the answer is usually to take both and convert on arrival, which brings us to volatility.
XRP is volatile, and how to handle it
XRP traded near $1.05–1.10 in late July 2026, down from its July 2025 cycle high of about $3.66, having spent 2026 in a broad downtrend. The direction isn't the point. The point is that a payment held unconverted is a position you didn't choose to open.
Say a customer pays you $200 in XRP. The whole process takes five seconds, but if you leave the coin on your balance for a week, what you actually receive depends on the market rather than the sale. Across hundreds of payments, your revenue starts drifting from what you actually sold.
Auto-conversion closes the gap. With 0xProcessing, incoming XRP converts to a stablecoin the moment it confirms, locking the dollar value. You quote $200, you receive $200, and whatever XRP does afterwards isn't your problem. Accepting RLUSD alongside XRP solves the same problem from the other end, since the payment arrives stable to begin with.
Is accepting XRP compliant? MiCA, licensing, and what to check
Accepting XRP is legal across the US, EU, UK, and most major markets. The regulatory weight sits with your payment processor, not with you for taking the payment, which is exactly why the processor's licensing matters more than most merchants realise.
Want to accept crypto payments on your website?
MiCA and the EU picture
MiCA is now in full force across the bloc, and it regulates the crypto-asset service providers who process payments rather than restricting which coins a business may accept. For an EU-facing merchant, that turns into one practical question: is your processor authorised as a CASP (crypto-asset service provider) in an EU member state? A licensed CASP passports across the European Economic Area under a single authorisation, so a compliant processor covers all of the EEA at once. XRP itself sits outside MiCA's stablecoin rules, since it isn't an e-money or asset-referenced token, so it carries none of the issuer obligations that apply to RLUSD or USDC.
Why a licensed processor does the heavy lifting
The compliance load on XRP payments is real: sanctions screening, AML checks, and the record-keeping that tax authorities expect. A licensed custodial processor absorbs most of it. 0xProcessing screens every incoming payment in real time against blacklist and sanctions data, verifies the business rather than the customer (KYB, not customer KYC at checkout), and keeps the transaction logging that clean books depend on. That's the difference between accepting XRP through infrastructure built for compliance and doing it from a bare wallet where the entire burden is yours.
What to confirm before you sign
- Licensing. Which authorisations does the processor hold, and in which jurisdictions? EU sellers want a MiCA-authorised CASP.
- Screening. Real-time AML/KYT on incoming payments, not a periodic review.
- Verification model. KYB on the business, so your customers aren't dragged through identity checks at the point of sale.
Your own obligations come down to tax reporting and record-keeping, which vary by country, so confirm the specifics with an advisor where you operate.
Which industries use XRP?
Cross-border B2B and remittances
The main use case. Businesses that pay suppliers or contractors in other countries skip the correspondent banking chain.
E-commerce with international buyers
Fast settlement and near-zero fees on orders that cards decline or overcharge for being foreign.
Financial services and fintech
RippleNet's 300+ institutional partners mean a payments company handling XRP fits into existing rails rather than inventing new ones.
Marketplaces
Paying out to multiple parties is quick and cheap, which is useful when you're making lots of small payments.
iGaming and high-risk verticals
Deposits and payouts are fast, and you won't have to worry about chargebacks.
When it comes to places accepting it, XRP is used by various travel bookers, digital goods sellers, and retailers that are happy to accept cryptocurrency. However, most transactions are made by large companies rather than by people buying small amounts. That's not a weakness. It's what the asset was designed for.
Conclusion
XRP is really good at moving money between currencies quickly and without much cost, and it does this consistently, not just when the network is busy. The SEC case closed in August 2025, removing the reason many businesses had avoided XRP. RLUSD gives you a stable asset on the same ledger, so a single integration covers both the fast bridge and the steady dollar.
Get the destination tag handling right and you won't lose payments. Convert on arrival, and you won't carry price risk you didn't choose. If you do these two things, Ripple's ledger will become what it was built for: a way to make payments that is cheaper and faster than the alternatives.
Want to accept XRP and RLUSD? 0xProcessing is a Ripple payment gateway that handles destination tags and X-addresses, screens incoming payments in real time, auto-converts to stablecoins at no extra fee, and settles via SWIFT or SEPA. Get started →
How do I accept XRP payments for my business?
Choose a processor that supports XRP. Clear KYB. Set up settlement. Connect via API or plugin. Then run a test payment. Make sure the destination tags are displayed correctly when you check out. Most businesses are live within a week.
What is a destination tag, and why does it matter?
It's a number identifying which customer account a payment belongs to when funds arrive at a shared address. Send XRP without a required tag and the payment can be permanently lost. If you send XRP without a required tag, the payment can be permanently lost. Using a system that gives each invoice a different address solves the problem.
Is XRP a security?
Not in retail secondary market transactions. In 2023, a US court ruled that XRP sold on public exchanges isn't a security. The SEC case closed in August 2025 with that ruling intact. Some direct institutional sales were treated differently.
How fast and cheap are XRP payments?
It takes three to five seconds to settle, costs a fraction of a cent per transaction (0.00001 XRP), and those figures stay the same when the network is busy.
Can I accept RLUSD instead of XRP?
Yes, and lots of shops take both. RLUSD is Ripple's dollar stablecoin on the XRP Ledger. This means you get stable value at the same speed and cost. Use RLUSD for invoicing and XRP for bridging or customer preference.
How do I deal with XRP's price changes?
The system will automatically convert at the time of payment. As soon as the transaction is confirmed, incoming XRP becomes a stablecoin. This means the dollar value is locked in, no matter what happens to the price later.
Do I need to keep XRP in the account?
Yes, there is a small base reserve. At the moment, this is 1 XRP. There is a little more for each additional ledger object. It's locked collateral, not a fee, and can be recovered if the account is closed.
