Their phone, not a shared password
A charge is confirmed on the device of the person making it. A password can be passed around a counter; a fingerprint cannot.
AgPOS
Take crypto
Take crypto
without dictating
an address.
A panel for a shop that already takes crypto, or would like to. You enter the amount, your customer scans, and the payment turns up next to the sale it belongs to. The money goes to your wallet — never to ours.
IN DEVELOPMENT
Being built. There is no sign-up, no waiting list and no price yet.
01The counter today
Taking crypto still means reading out a number and hoping.
A shop that accepts crypto today does it with what it has: a long address read out loud, a code taped next to the till, or a screenshot sent over WhatsApp. It works, more or less. What it costs is that three decisions land on your customer, standing at your counter with people waiting behind them — and two more problems stay with you, after they have gone.
None of that is the customer's fault, and none of it is fixed by teaching them more. It is fixed by not asking them in the first place.
01 · The address
Read out, copied, or stuck to the wall
A long string nobody can check by eye. If a character is wrong the money is gone, and there is no bank to call about it.
02 · The amount
Typed by the person paying
One digit out and you are either short or refunding by hand. You find out after they have left.
03 · The network
Chosen by the person paying
The same money can travel by several routes, and the wrong one does not bounce back the way a bank transfer would. This is the part people are genuinely afraid of, and they are right to be.
04 · The sale
Nothing says which payment was which
At the end of the day you have a list of payments and a list of sales, and matching them up is a job you do by hand, from memory.
05 · The printed code
A picture anyone can cover with their own
A code taped to a counter is just an image. Nobody comes and swaps your card terminal; swapping a sticker takes a second, and it has happened elsewhere.
02How a sale goes
You make the charge.
Your customer only scans.
The amount, the destination and the route are decided on your side, where the sale is, and travel inside the code. Your customer's wallet reads all three. There is nothing for them to type and nothing for them to choose.
01
You enter the amount
On the panel, in the currency you price in, with a note if you want one. It makes a code for that sale and shows it on the screen you already have.
02
They scan it and pay
Their wallet fills in the amount and the route from the code. The code is for that one sale — not printed, not taped up, not reusable by anyone.
03
It lands next to the sale
The payment arrives carrying your reference, so the panel puts it against the right sale on its own. Nothing to reconcile later, and nothing to remember.
A customer can still pay you the old way, by plain transfer, and that money arrives perfectly well — it just arrives with nothing attached to say what it was for. The panel shows those separately and says so, rather than guessing at a match and quietly getting it wrong. Guessing is worse than admitting.
03Who charged what
The person at the counter
is usually not the owner.
So the panel is not built around one login that everybody shares. You add the people who work with you, and each one confirms a charge with their own phone's fingerprint or face — from the browser, with nothing to install. Every charge records who made it.
Switching someone off takes effect at once and does not erase what they already did, so last month's numbers stay true. And it answers a question you already had before any of this: how much did each person take in today.
A name on every charge
Who generated it is part of the record and part of the export, not something reconstructed afterwards.
Access ends when you say
You add people and remove them yourself. Removing one does not disturb anyone else, and nothing is deleted from the history.
04Your money
The money goes
to your wallet.
Argentum never touches it.
Payments go from your customer's wallet to yours. They do not pass through Argentum on the way, are not held by Argentum for any length of time, and are not converted by Argentum. This is not a policy we could change quietly later: the panel has no key of yours. It reads what has arrived at the addresses you give it and shows it to you. It cannot sign anything, so it cannot send anything.
Turning some of it into local currency is a different activity, and a regulated one. It is done by a partner licensed to do it — not by Argentum. You send that partner what you want to convert, signing it yourself from your own wallet, and they credit your bank account. You choose when, and you choose how much.
Only you can move it
Every transfer out is signed by you, on your side. There is no arrangement in which the panel moves your funds on your behalf, automatically or otherwise.
Convert what you need
Most shops want local currency for what they have to pay out this week and are content to leave the rest alone. Converting small amounts one at a time costs more in fees than it is worth, so the panel shows you the numbers and lets you decide.
Licensed, and not us
Receiving a merchant's money and passing it on is licensed activity, jurisdiction by jurisdiction. Argentum does not hold those licences and does not intend to. We supply software.
Said plainly, because it decides everything above
Argentum does not receive, hold, move or convert a shop's money, and is not built to. What we make is the panel, the charge code and the reports.
This is the same commitment Argentum Wallet is built on. It is written here now, while there is no revenue to lose by writing it, so that it cannot later be presented as a constraint we discovered along the way. It describes our own position and is not legal advice to anyone.
05What exists, and what does not
A working panel,
and a list of what
is still missing.
This is a development build, not a service anyone is running for a shop today. Here is the state of each piece, so that nothing on this page has to be taken on trust.
BUILT
Seeing what arrived
You give the panel your own receiving addresses and it watches them, showing each payment with its amount, what was paid in, which route it took, who sent it and when. It only ever reads.
If one route stops answering, the panel says so beside the list. It never shows an incomplete list as though it were the whole day.
BUILT
Making a charge
Amount, reference and a note, turned into a code on screen for that one sale, with a customer-facing view and a countdown. Nothing is printed and nothing stays on the counter.
BUILT
People, and the paperwork
Adding and removing the people who work with you, a fingerprint on each charge, takings per person, and spreadsheets your accountant can open without being taught anything.
IN PROGRESS
Payments that arrive already matched
What lets a payment carry your sale's reference inside it is an open standard called x402 — not something of ours, and not something a shop ever has to understand. It is written and it works, and it is not yet running anywhere a shop could reach.
The research behind that standard is written up separately, including the part where software pays for things on its own. That is why this is worth building on now rather than later — but a shop gets the benefit from the first payment, whether or not anybody's software is doing the paying.
NOT BUILT
Accounts that outlive the browser
Today what the panel has learned lives in the browser you opened it in. Shops need an account, on more than one device, that survives closing a tab. That is next, and until it exists this is a demonstration rather than a till.
NOT OURS TO BUILD
Turning it into local currency
A licensed partner does this, and how quickly they settle and at what spread is the number that decides whether any of this is worth a shop's while. We are not going to publish a promise about someone else's settlement times before we have measured them. See section 04.
06Status
In development.
This page exists so the direction is legible, and so the line about whose money this is gets written down before anybody's money is involved. It is not here to open a queue.
What this page is not
It is not a product announcement. AgPOS cannot be bought, piloted, reserved or scheduled, there is no price, and there is no date attached to any of it.
There is deliberately no sign-up and no contact address on this page for this work, and no form. If a shop asked for it today there would be nothing to hand over — so the honest thing is not to invite the request and leave someone waiting.
The next thing that happens is not code. It is a handful of conversations with shops that already take crypto, about what actually goes wrong at their counter. What they say will change this page, and it should.
When there is something a shop can use, it will be said here, on this page, in the same plain terms this one uses to say there is not.