The merchant home screen for Bitcoin.

Ring up sales. Hide the keys. Keep every server in one app.

CryptoTxn is not a wallet.

It is the control panel for the tools you already run — without handing the company funds to whoever is on the till.

Instance online

A shop should not live in twelve Safari tabs.

BTCPay, the shop, POS, two wallets, mempool, the node. The till should not be a pile of bookmarks.

Too many links

BTCPay, POS, shop, wallets, mempool, node.

Wallet POS leaks power

A simple wallet at the register often means staff can open the money.

No single status

Is the instance online? Is the chain synced?

Employees take payments. They never see the money.

Logs and dashboards stay on the owner side. They do not sit on the till phone.

Simple wallet POS

  • Device holds or opens a wallet
  • Staff can reach balances
  • One app trying to be cash register and vault

CryptoTxn

  • No coins in the app
  • Staff PIN opens the POS keypad only
  • Owner keeps BTCPay admin, Blink, Blue Wallet, logs

You decide which tiles staff can tap. Default is POS only.

Lock the phone to the app with Guided Access. See Support.

Admin PIN and Face ID for admin and wallets.

Staff PIN opens the POS keypad.

Your instance. Your rules.

You choose the stack. Hosted instance or your own server. Your URLs.

Hosted by CryptoTxn

Free

Public instance at cryptotxn.net. Same grid: admin, POS, shop. Plugins are limited to those on your instance, plus the NFC Manager. 

My own server

One-time €9.99

Paste your BTCPay URL. Optional local URL and onion URL. Status comes from /api/v1/health. Extra tiles for Umbrel, mempool, Public Pool, Cloudflare, anything you host.

Bolt cards from the owner’s phone.

Write, read, and format Bolt cards for the backend you already run — LNbits, or the Boltcard Factory on your BTCPay Server.

NFC Manager

Owner only

  • Face ID first, then your 6-digit admin PIN. Never the device passcode.
  • Card keys are stored in the iOS Keychain on that iPhone. They are not in the app’s saved data, backups, or usage log. CryptoTxn has no access to them.
  • The app runs no server and no Lightning backend.

New phone?

Keys do not move automatically

Copy them by hand from the old phone or from your backend. Support →

One place for every server you run.

One app for every server link. Add BTCPay, the shop, mempool, Umbrel, Public Pool, or any custom https service. Stop hunting bookmarks.

BTCPay Server
Blue Wallet
mempool
Public Pool
Website
LNbits
Lightning
Bitcoin Core
Bitcoin Knots
Fulcrum
Ride The Lightning
RoboSats
Bitaxe
Bisq
Monero
Bassin

Add any https service. Marks belong to their owners. CryptoTxn is not affiliated with those projects.

How it works

01

Choose hosted (cryptotxn.net) or your own server.

02

See instance status — online and synced.

03

Set admin PIN and staff PIN.

04

Hand the phone to the till.

Who it’s for

Merchants charging in Bitcoin with BTCPay.

CryptoTxn hosting clients.

Anyone who runs a home server and a shop and is tired of bookmarks.

FAQ

No. CryptoTxn never stores seeds, xpubs, or balances.

No. It holds no seed phrases, xpubs, wallets, or coins. If you use the NFC Manager, Bolt card keys are stored on the owner’s iPhone.

Only if you mark that tile as staff-visible. Out of the box they only get POS.

No. Payments stay on BTCPay (cryptotxn.net or self-hosted).

No. Hosted mode is the easy path. Own-server mode is for people who already run the stack.

One-time App Store purchase, €9.99.

French and English. Switch any time with the flag buttons.

See the Support page, or write to hodl@cryptotxn.io. Company and services: cryptotxn.io.

Run the shop from one screen.

Ring up sales at the till. Keep the keys with the owner.

Available soon on the App Store

CryptoTxn for iPhone is in Apple review. Check back shortly.

Bientôt disponible sur l'App Store

CryptoTxn pour iPhone est en cours de validation chez Apple. Revenez bientôt.

CryptoTxn App
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.