M-Pay
M-Pay is the payment and transaction technology beneath NemosGo. It links a payment service with a merchandise management system and brings agreement, payment, billing, delivery and receipt together into a single transaction.
What M-Pay does
- Three roles. The issuer puts the credit into circulation, that is the company under whose brand NemosGo runs. Buyers and sellers are everyone who buys and sells with it. The issuer is always a company and never a private person, because someone has to stand behind the credit that has been issued.
- Paying like cash. A banknote can be checked. Spending it does not show who you are, and the shop cannot look up afterwards who paid. Yet nobody doubts the note. That is exactly what M-Pay does digitally, at every provider connected to the same installation. One of the techniques behind it is the blind signature, a cryptographic method published by David Chaum in the 1980s.
- Cryptographically linked. The invoice is signed, the buyer signs the payment with their own key, and the delivery is tied to exactly that invoice. That way every step can be checked, after the fact as well.
- Disclosing, if you want to. The default is a purchase without any personal details. Anyone who wants to disclose something does so explicitly, for example a name and address for an invoice or for a donation receipt. Both sides get the receipt, the buyer and the provider.
- Cancelling. If the provider has marked an offer as cancellable, the buyer can cancel in the app. If the provider agrees, the credit is refunded and the delivery disappears from the app.
- Offline, too. When paying at the till, which is planned, the buyer needs no connection, in a dead spot, on a plane or at sea. M-Pay keeps the tokens intact and guards against the same credit being spent twice.
- QR instead of NFC. A QR code runs on any phone with a camera, without special hardware and without activation, and it works without a connection. Above all, one code reaches many readers, while NFC only ever reaches one reader at a time.
- Signing in from the phone. The buyer signs in with the identity already on their phone. The eID of the identity card and further methods are planned for later.
- On the SEPA rails. M-Pay uses European payment transfers, not the card rails. The balance is topped up from the buyer’s bank account. For the seller that means no terminal and no card fee per purchase. The payment fee is charged at top-up, or for business customers at collection.
- Person or machine. Whether a person buys in the app or an agent with the SDK, the transaction is the same.
The building blocks. The checkout in front of the provider’s interface, the payment backend, the wallet as an app or as a service of its own, and the dashboard. The details are on For developers.
What is open source. The SDK and the protocol definitions are on Codeberg under the MIT licence, the wallet as a ready-built program for Linux. Not all of M-Pay is open source.
Factory 42
Factory 42 is the Private AI framework we use to develop, run and organise parts of NemosGo. It also powers offerings we build for customers.
At its centre is the knowledge space: an area where people and a language model work together on documents, data and conversations, sealed off even within a company. What is in it stays in it.
Factory 42 runs on your own hardware. Once the models are in place, it works without internet access as well. It keeps a record of what happens, and it supports fine-tuning a model on your own subject area. A smaller model fine-tuned on a subject often delivers better results than the largest general one.
The building blocks: an API server in Go, a gateway to the models, a web interface, a relational database and a vector database for similarity search.
What we use it for ourselves
- Development. We build prototypes quickly with it, set up test environments and run tests. Alongside it, we work a great deal with large general-purpose models in development.
- Operations. Factory 42 runs on our own server and manages users and access rights.
- Organisation. Autonomous agents automate processes within the company.
What it creates for customers
- Making content findable. An assistant finds the piece that fits through similarity search in the knowledge space, and it is paid for through M-Pay.
- Selling models per call. Anyone who runs their models with Factory 42 can sell their use through NemosGo per call, via Factory 42’s gateway and API server. That is how it ran in the field test, where an application paid per request. Factory 42 is not required for this: any model that can be called through an interface can be sold the same way.
- Descriptions that write themselves. When a publisher uploads a document, the checkout fetches the summary from Factory 42 and publishes it in the catalogue. The publisher can edit it afterwards.
- Private AI in-house. A knowledge space and models fine-tuned on your subject, on your own hardware, set up by us.
Want to build rather than read? The protocol, the developer kit and example code are on For developers.
Let’s talk
Questions about the technology, or about running Factory 42 in-house? Write to us.