XMR — · · 24h Vol — · Cap — Trade XMR
XMRPOS Review 2026: Point-of-Sale App for Monero Merchants

XMRPOS Review 2026: Point-of-Sale App for Monero Merchants

Compare the two main open-source XMR point-of-sale Android apps in 2026, their setup requirements, privacy features, and which merchants should choose each.

Two XMRPOS Apps in 2026

Merchants searching for an XMRPOS solution in 2026 quickly run into two similarly named Android apps that both target XMR payments. The first is the felipebrunet/xmr_pos project, published on Google Play by icripto. It is a non-custodial client that keeps the Monero node URL, base address and secret view key on the device only. The app supports multiple subaddresses to avoid reuse and includes a 4-digit PIN for shared use in shops. Its Google Play listing shows 100+ downloads while Chrome-Stats recorded 230 installs as of 2026-10-02.

The second project originated as MoneroKon/XMRpos on GitHub, where it reached 46 stars before the original repository was archived on 6 November 2025. Development moved to the Monero-Merchant/monero-merchant fork. This FOSS client connects to a self-hosted backend running MoneroPay and adds features such as multi-client support and optional Bluetooth printer output. Its releases (v1.0 in late October 2025, v1.2 and v1.3 shortly after) explain why merchants still encounter both names when looking for XMR POS tools.

icripto XMR POS App Walkthrough

The felipebrunet/xmr_pos client, published by icripto on Google Play, operates as a non-custodial Android app for Monero merchants. Setup begins with three required credentials: a Monero node URL, a base address, and the secret view key. These values remain on the device at all times and are used only for the app to connect directly to the user-specified node.

Once configured, the app supports multiple accounts and subaddresses. Merchants can generate fresh subaddresses for each transaction, which reduces address reuse and improves privacy compared with static addresses. The interface displays incoming payments in real time by scanning the connected node for matching outputs.

A 4-digit PIN protects the settings menu. This feature allows shop staff to process payments without access to sensitive keys or node details, making the app suitable for environments with multiple employees.

The November 2, 2025 update added support for additional currencies and languages along with minor stability fixes. The project remains under the MIT license and requires no app-level fees or custodial accounts.

MoneroKon and Monero-Merchant XMRpos Stack

The MoneroKon/XMRpos client works with a self-hosted backend that integrates MoneroPay for transaction handling. Merchants install the server locally so the Android app connects directly without third-party custody.

One backend instance supports multiple POS clients, letting several devices share the same payment queue. Optional Bluetooth ESC/POS printer output sends receipts to compatible hardware. Confirmation thresholds are set to zero, one, or ten blocks, balancing speed against finality. Real-time status shows on the client as transactions confirm.

Version 1.0 appeared around late October 2025, with v1.2 and v1.3 following in early November 2025. The original MoneroKon repository was archived on November 6, 2025; active work continued under the Monero-Merchant/monero-merchant fork licensed GPL-3.0.

The stack relies on view-only keys and subaddresses for privacy. Operators must run their own node and server, but the code remains fully open and carries no app-level fees or mandatory identity verification.

Feature Comparison Table

The two apps differ sharply in architecture and deployment. icripto runs as a standalone non-custodial Android client that connects directly to any user-specified Monero node. The MoneroKon-derived project requires a self-hosted backend that integrates MoneroPay and supports multiple connected POS clients.

Featureicripto XMR POSMoneroKon / Monero-Merchant XMRpos
ArchitectureStandalone non-custodial clientClient plus self-hosted MoneroPay backend
Node NeedsUser supplies node URL; credentials stay on deviceBackend handles node connectivity; clients connect to backend
Confirmation SettingsNot configurable in listed featuresConfigurable thresholds: 0 / 1 / 10
Hardware OptionsStandard Android device onlyOptional Bluetooth ESC/POS printer output
LicensingMITGPL-3.0
Maintenance StatusUpdated 2 November 2025; 3 GitHub starsOriginal repo archived 6 November 2025; fork active under Monero-Merchant; 46 GitHub stars pre-archival

Both projects remain open-source with no app-level fees. Merchants choosing the icripto route gain simpler setup at the cost of fewer multi-client and printer features. Those running the Monero-Merchant stack gain configurability and printer support but must maintain the backend server.

Privacy and OPSEC Considerations

Both XMRPOS apps require merchants to supply a secret view key and base address so the client can scan the blockchain without spending access. If the Android device is compromised or the view key is logged elsewhere, an attacker gains read-only visibility into every incoming payment, undermining the privacy model.

Connecting to a clearnet Monero node exposes the merchant’s IP address to that node operator. Even when the app stores credentials locally, traffic to a public node can still correlate transaction timing with network identity unless the connection is routed through Tor or a self-hosted node on the local network.

Subaddress support reduces address reuse, yet repeated use of the same subaddress across multiple customers or over long periods still shrinks the anonymity set. Merchants should generate fresh subaddresses per transaction or customer batch.

The 4-digit PIN that guards settings on the icripto app is convenient for staff but offers limited brute-force resistance; shops with multiple employees should treat the PIN as a basic control rather than strong authentication.

The remaining link in the chain occurs at KYC on-ramps: any XMR that enters the merchant’s wallet from an exchange account tied to verified identity can still associate later outgoing or received amounts with that identity, regardless of the point-of-sale app’s protections.

FAQ

How do I configure the icripto XMR POS app for merchant use?

Enter a Monero node URL, base address, and secret view key into the app settings. These values remain on the device and the app connects only to the chosen node. A 4-digit PIN protects the settings section.

What fees do merchants pay with either XMRPOS app?

Neither app charges platform fees. The only cost is the Monero network fee, which showed a median of 0.0000445 XMR across more than 5,000 transactions sampled in late October 2026.

Is the MoneroKon XMRpos project still active after the repository archive?

The original MoneroKon repository was archived on November 6, 2025. Active development continued under the Monero-Merchant fork, which maintains the self-hosted backend and MoneroPay integration.

Can multiple staff members or devices share one setup?

The icripto app supports a PIN-protected settings area suitable for employee use. The MoneroKon-derived stack allows multiple POS clients to connect to a single self-hosted backend.

What confirmation thresholds can merchants select?

The MoneroKon and Monero-Merchant apps let users choose 0, 1, or 10 confirmations before marking a payment complete. Real-time status updates are shown on the client.

Where is the icripto app available and how widely used is it?

It is listed on Google Play with 100+ downloads noted on the store page and 230 downloads reported by Chrome-Stats as of October 2026.