NemosGo® DE

Product

Sell and bill

You sell digital goods one at a time or by actual usage, wherever your customers find them.

When NemosGo is worth considering

Single purchaseOne product, one price, one completed transaction. It ends with delivery, and both sides get a receipt.
Usage-basedA price per unit, many separately documented transactions. Billing ends when usage ends.

Examples

Even at €0.00 there is a transaction with a receipt, for recording a consent, for example.

Which industries we have in mind

Where you sell

Your offer sits where your customers already are. What differs is only how the buyer gets to it.

Who buys

People and machines buy through the same checkout, which sits between your offering and the buyer.

Two ways in lead to the same checkout: at the top the person who taps and confirms, with the wallet on their phone; below, applications and AI agents buying on someone’s behalf, with a wallet of their own on the server and a budget. The checkout ties together agreement, payment, billing, delivery and receipt, and on the right the purchase arrives at the provider.People buyconsent at purchasePersontaps and confirmsWalleton the phoneApplications and AI agentsbuy on someone’s behalfApplicationbuys on someone’s behalfWalleton its server, with a budgetCheckoutagreement, payment, billing, delivery, receiptProviderwhere the purchase arrives
Both pay from a wallet: the person from the one on their phone, the application from its own on its server. A budget sets how much an agent may spend from it.

The only difference is when consent is given. If a person buys themselves, even when an assistant shows them the offer, they confirm each purchase in the app. If they send an assistant or agent off with a task, they approve an amount for it beforehand, with a purpose, a period and a maximum per call. Within that the agent buys without asking, privately and at work alike.

How a company gives its agent that approval is covered under Buy and allocate costs.

How payment works

Every purchase runs through the same five steps: agreement, payment, billing, delivery, receipt. Payment takes one of three forms.

Paid up frontYour customer tops up credit, and the purchase is taken from it.
Charged internallyIf you sell a service to departments in your own company, every purchase is charged to their cost centre. No money leaves the company.
Collected afterwardsIf a company buys from you, its staff confirm each purchase in the app, and you collect the amount afterwards, by invoice or direct debit. You decide when and how you collect and which payment terms apply. Because many purchases come together in one collection, the cost of payment processing goes down.

Two examples

The single purchase

Payment and goods are one act. The buyer needs no account with the seller.

An example: two tickets for 30 euros in total.

  1. AgreementTwo tickets, €15.00 each.
  2. PaymentFrom their credit, confirmed in the app.
  3. BillingPurchase and service matched.
  4. DeliveryTwo tickets as PDF, plus a behind-the-scenes video.
  5. ReceiptIn the buyer’s app, with its own number.

The purchase happens where the conversation happens, with no customer account in your ticket shop. Recording of a ticket purchase, unedited

An invoice in the app: theatre tickets, 2 of them, with merchant, provider and the amount of 30.00 euros. Below it the option to personalise the invoice, with the note that the name stays with the buyer, and the buttons to decline or to pay. Invoice Item Theatre tickets, 2 Merchant Provider Amount EUR 30.00 Personalise invoice Name stays with the buyer Decline Pay
The purchase in the app
A receipt from the provider with a receipt number, an issue date and the line stating that the buyer stays pseudonymous. Provider Test receipt Receipt no.: NG-2026-000196 Issue date: 10 Jun 2026 Buyer: pseudonymous (no identification required) DESCRIPTION QTY AMOUNT Theatre tickets 2 €30.00 Performance on 25 Jun 2026, €15.00 each Video behind the scenes1€0.00 Total €30.00 Paid on 10 Jun 2026, 21:40 The same receipt in portrait. Provider Test receipt Receipt no.: NG-2026-000196 Issue date: 10 Jun 2026 Buyer: pseudonymous (no identification required) Theatre tickets €30.00 Qty 2, €15.00 each Video behind the scenes€0.00 Total €30.00 Paid on 10 Jun 2026, 21:40
The receipt both sides receive
The entry in the app history: theatre tickets, 2 items, 30.00 euros, with three green markers.
The same purchase in the app history. The three markers stand for paid, delivered and documented. From here the receipt can be added to Apple Wallet or Google Wallet, where supported.

Usage-based

The same transaction repeats for as long as usage continues. The price per unit or the rule is set beforehand, the amount follows from actual consumption.

An example: you offer an AI model through an interface and charge for computing time, 0.2 cents per second. An answer that takes 2,327 milliseconds to compute costs €0.0047. Your customer’s application pays for every call from its credit, in the same step in which it fetches the answer. For each call you see the amount, a pseudonym and the receipt. When usage stops, billing stops, with nothing to cancel.

Three calls side by side, 0.0047 euros, 0.0031 euros and 0.0052 euros, each one paid, delivered and documented. On the right, usage and billing end together. Request €0.0047 paid · delivered · documented Request €0.0031 paid · delivered · documented Request €0.0052 paid · delivered · documented Usage ends Billing ends

Recording: buying model usage, unedited

Less to steal

Your shop and your interface see only a pseudonym, the amount and the receipt per purchase. No customer accounts, card numbers or passwords end up there, and you get a buyer’s name only with their consent. What payment requires sits separately in the NemosGo installation, and the rest of your system stays free of it.

What you decide

You decide three things yourself:

What it costs

If you use NemosGo yourself, you pay a monthly software fee, tiered by usage. NemosGo takes no share of the sale price.

The payment fee is charged once at top-up or collection, for many purchases. With card payments it is charged on every single purchase. What setup and operation cost, if you hand both over to us, is described under For sellers.

In practice

From July to August 2026 the complete transaction ran at three organisations: a culture magazine, an event organiser and a charitable organisation. Purchases were made on the website, in a messenger and by QR code, and from the end of July in an AI assistant as well. At the culture magazine alone, more than 500 purchases have been made since June.

Payment was made with test credit. Within the system it was real credit; it was simply issued to participants rather than paid in from a bank account. Payment, delivery and receipt ran exactly as they do with euros. The only thing still open is connecting the bank account for paying in and out through the licensed payment service provider. It changes nothing about the purchase itself.

What you need for it is described under For sellers. The full sequence is on the technology page, the integration on the developer page.

If you want to know what the transaction would look like at your end, write to us.