monero.loveA little love for the network.
← All news

Monero / Payments / Merchant Adoption

Monero Point of Sale in 2026: Adoption, Software, and Real-World Usage

Explore Monero point-of-sale adoption in 2026, available merchant software, payment infrastructure, real-world usage, and remaining challenges.

A Monero checkout tablet with a payment code, receipt printer, shopping bag and coffee cup.

Monero point-of-sale software in 2026 includes Android tills and self-hosted checkout servers. Public evidence tells us much less about how often customers use them in shops.

A business advertising XMR acceptance, an application detecting a payment, and a customer completing a purchase are different kinds of evidence. Merchant directories help with the first. Project documentation explains the second. Neither supplies a reliable global count of everyday retail sales.

This review checks public documentation and repository activity as of November 20, 2026 UTC. It does not include hands-on software or printer testing. The practical question is which parts of checkout each project handles, and what a merchant still needs to arrange.

How many businesses accept Monero?

The XMRList Monero Merchant Index's November 19 snapshot supports the following figures:

Metric Reported figure
Active directory listings 1,820
Listings with XMR acceptance confirmed on their websites 1,074
Countries represented 103
Direct-to-wallet share 70.9% of 436 listings with a recorded processor

Credit: XMRList Monero Merchant Index, November 19, 2026, CC BY 4.0. Its November 20 API snapshot reports the same four figures.

These are directory statistics. Entries include exchanges, nonprofits, hosting providers and software services. They are not a count of physical shops. The index distinguishes website-confirmed acceptance from its separate verification field, and reports zero hands-on tests. A listed payment option does not establish regular purchases.

The direct-to-wallet percentage describes 309 of the 436 classified listings. That denominator excludes unclassified listings and says nothing about the share of payments or money spent. Country coverage uses operators' stated locations, which may differ from their customers' locations. These limits make the index useful for finding services, but unsuitable for estimating retail transaction volume.

Monero POS software compared

The table summarizes documented roles and observable maintenance signals. Recent commits show development activity, not a security audit or proof of dependable operation.

Project Documented role Maintenance evidence
Kasisto Mobile web checkout Last default-branch commit March 6, 2019
XMRpos Original Android till Archived November 6, 2025
Monero Merchant Android till and backend Default-branch update November 15, 2026
MoneroPay Payment API GitHub mirror update November 23, 2025
BTCPay plugin XMR checkout integration Version 1.5.0 listed November 20, 2026
XMR Checkout Online checkout and terminal links Default-branch update November 20, 2026

Kasisto's historical role

Kasisto's documentation describes a progressive web app for phones and tablets, connected to a server running a Monero daemon, view-only wallet and HTTPS proxy. Its design accepts unconfirmed transactions to shorten checkout waits.

The commit history ends in 2019, leaving current compatibility untested here. A new merchant should not read its accessible demo or documentation as proof of current compatibility. Its public installation count remains unknown.

Monero Merchant succeeds XMRpos

The original XMRpos repository explicitly says the project was renamed and relocated. Its successor's README advertises Android support, Bluetooth ESC/POS receipt printing, local-currency entry and additional reference currencies. It describes a backend API connected to monerod and MoneroPay, with wallet keys kept off client devices.

The documented checkout advances to a receipt screen at a selected threshold of 0, 1 or 10 confirmations. The README also claims zero-confirmation detection within five to ten seconds. That timing and the broad Android compatibility statement are project claims, not results from our testing.

The November commit history establishes work beyond the archived predecessor. Merchants still need to test their device, printer, network connection and refund process before relying on it at a counter.

MoneroPay supplies the backend

MoneroPay documents receiving, sending and tracking XMR through an HTTP API, with optional callbacks for payment updates. It uses Monero Wallet RPC with PostgreSQL or SQLite. Its receiving endpoint supplies a subaddress for a payment request.

Its zero-confirmation option, introduced in version 2.6.0, sends callbacks at zero confirmations, one confirmation and unlock, normally ten confirmations. Those stages let an application distinguish detection from later availability to spend.

MoneroPay is a backend service. Its documentation lists shops and ticketing as possible applications, without identifying deployed installations. A merchant still needs order handling, a customer interface and records connecting payments to sales.

BTCPay and newer checkout tools

The official plugin catalogue lists version 1.4.0 in its release history. A fresh check on November 20 found version 1.5.0 published that day, requiring BTCPay Server 2.3.7 or later. The plugin README warns that every store on an instance shares one Monero wallet and advises against sharing that instance. This matters for anyone considering hosting it for unrelated merchants.

XMR Checkout offers another recently updated approach. Its documentation describes view-key payment detection, invoices, webhooks and terminal links for phones or tablets. Terminal sales default to a zero-confirmation target. Its README warns that once an invoice reaches its target, checking stops: a later failure or chain reorganization does not reverse the confirmed status. Operators need to understand that behavior before releasing goods.

These tools offer different starting points. A merchant choosing between them should first decide whether they need a standalone till, an online checkout or an API for an existing system.

Where is Monero used?

Mullvad's payment terms list Monero. This establishes an offered payment method, without telling us how many customers select it.

Digilol's Cake Labs case study says it integrated MoneroPay into a backend for Cake Labs. That is a supplier report, without an independently audited transaction total or evidence of physical checkout installations.

XMRList includes online-service categories, but its taxonomy cannot produce a dependable physical-versus-online sales split. A hosting provider may serve worldwide customers from one listed country. A shop may advertise XMR but rarely receive it. The sources we reviewed leave both the sales split and the global number of active retail terminals unknown.

Gift-card spending needs similar care. Buying a gift card with XMR and redeeming it elsewhere is indirect spending. It does not show that the final retailer installed Monero payment software.

Physical checkout also places different demands on the operator. An online store can hold an order while payment confirms. At a counter, staff must explain the wait, identify the correct payment and decide when to hand over goods. That workflow deserves testing alongside the software itself.

Zero-confirmation payments trade waiting time for risk

Monero's block documentation give a two-minute block target. A customer can wait longer because block arrival varies and inclusion is not guaranteed.

A transaction detected before inclusion in a block has zero confirmations. Handing over goods at that point exposes the merchant to a payment that may never confirm, including a conflicting spend. Later confirmations reduce uncertainty, but a chain reorganization can still change which transactions remain in the accepted chain.

The official GUI guide explains how Merchant Mode displays both confirmed and unconfirmed payments. Our coverage of proposed merchant warnings explains why a detection alert is not a settlement guarantee.

A useful policy specifies when staff may release goods and how to handle a delayed or disputed payment. A low-value purchase may justify a different policy from an expensive item handed over immediately. Software should expose that decision, including any point at which it stops monitoring an invoice.

Accounting, settlement and integration

Receipts from a shop and an online checkout connect to a merchant ledger.

For a trial deployment, keep a record connecting each order to its XMR amount, pricing currency, exchange-rate source, payment status and any refund. The subaddress model helps distinguish incoming payments, but it does not replace the store's order records.

Local-currency pricing also differs from local-currency settlement. Displaying a price in euros and calculating an XMR amount does not itself convert the received Monero into euros. A merchant needing that conversion must arrange it separately and account for rate changes and fees.

Before launch, test underpayments, duplicate notifications, late payments and interrupted connectivity. Check what staff see when an invoice expires and how they match a refund to the original order. Test any required inventory and accounting connections separately from receipt printing.

Self-hosting adds responsibility for updates, backups and access controls. A view-only setup separates detection from spending authority, but the view key still reveals incoming-payment information. Treat checkout credentials and wallet backups according to their actual access, as explained in our offline wallet guide.

What would establish broader adoption?

Monero conceals transaction amounts and recipient information from public observers. That prevents an outsider from reliably classifying blockchain transactions as retail sales. Merchants can publish voluntary totals without exposing individual payments.

Useful reporting would distinguish installed software from active merchants, and attempted checkouts from completed purchases. It could include monthly completed sales, checkout times, failed payments and merchant retention. In-person and online totals should remain separate, with collection methods and reporting periods disclosed.

Developers can help by making payment states understandable and supporting upgrades, refunds and existing shop records. A small documented trial lets merchants check whether staff can complete a sale, reconcile it and resolve a problem.

Monero has software for accepting XMR and identifiable businesses offering it. The evidence reviewed here supports that narrower conclusion. It does not establish widespread physical retail use, a global installation total or growing checkout volume. Those claims need measured merchant activity.

Support Monero Love

Help keep the public nodes and packages running. Send any amount of XMR.

Scan with a Monero wallet to donate to Monero Love.89hGTKxRVA3AUeKAbCRBt5TMSzq3MQZooNNsezCpNFjp2oeJPRx8AJeGKA8ziHZNqab78f4Vr1ntxhPDxX5298nnGZjHkhm