Solutions
Six situations where somebody has to ask for money.
The modules are the same in all of them. What changes is who is asking, how the request travels, and which system has to hear about it afterwards.
The same parts, arranged differently
Which modules each situation actually needs.
Nothing here requires the whole stack. A merchant never touches reconciliation exports; a treasury team never touches point of sale routing.
| Situation | Request | Verify | Route | Observe | Reconcile | Connect |
|---|---|---|---|---|---|---|
| B2B invoicing | Request, available | Verify, available | Route, not used | Observe, available | Reconcile, available | Connect, not built yet |
| Merchant and POS | Request, available | Verify, available | Route, available | Observe, not used | Reconcile, not used | Connect, not used |
| Treasury requests | Request, available | Verify, available | Route, not used | Observe, available | Reconcile, not used | Connect, not used |
| Agent payments | Request, available | Verify, available | Route, not used | Observe, available | Reconcile, available | Connect, not used |
| Validator and node services | Request, available | Verify, not used | Route, not used | Observe, available | Reconcile, available | Connect, not used |
| Marketplace payouts | Request, available | Verify, not used | Route, not used | Observe, available | Reconcile, available | Connect, not built yet |
A hollow mark is a module the situation needs and that is not built yet. Every solution page says what its own gap costs, in its own words, rather than leaving you to read it off this table.
What they have in common
Somebody asks. Somebody pays. Somebody has to know which was which.
Every one of these situations breaks in the same place: the moment money arrives and nothing on it says what it was for. The usual answer is a reference typed into a free text field and a person to check it afterwards.
The six
Pick the one that sounds like your week.
B2B invoicing
Send an invoice that matches itself when it is paid
The invoice and the payment arrive already knowing about each other.Merchant and POS
One code on a counter, payable from any wallet
The counter shows a code. Any wallet can read it. Nothing is installed.Treasury requests
Ask an internal counterparty for a transfer, with a record
A request you can send, check and file, without a shared spreadsheet.Agent payments
A request a program can produce, check and pay
A payment request that a program can read as reliably as a person can.Validator and node services
Bill for node operation, and read the settlement yourself
You already run the node. Read your own money arriving on it.Marketplace payouts
Pay many parties, and know which payout was which
Every payout carries the reason it was made, without publishing it.Your situation is probably one of these.
If it is not, the modules still are. Start with the request format and see how far it gets you.