Release v0.3.1, 21-Nov-2026 · all releases
Building a POS
From a sandbox key to registers that take payments for real merchants, in order. Each step names the page and section that hold its detail. The API reference for a POS holds every route a POS calls, each field and each answer.
| # | Step | Where it is |
|---|---|---|
| 1 | Take a sandbox key. It needs no credential, and it opens your own world: a store, a register and simulated terminals that approve, decline or never answer. | The sandbox: 1. A key and a world, 2. Your world |
| 2 | Send your first sale, POST /v1/sales, to a simulated terminal. A new IdempotencyKey for each sale; the same key again never makes a second sale. | 4. The POS journey, step 6. Reference: createSale |
| 3 | Read its outcome, GET /v1/sales/{TransactionReference}, holding the read for a change, until it settles: ACSP, RJCT, or UNKN when no one knows yet. | 4. The POS journey. Reference: readSale |
| 4 | Cancel a sale or a refund still running, POST /v1/sales/{TransactionReference}/abort. | 2. Your world, on Abort. Reference: abortSale |
| 5 | Refund a sale, the whole amount or a part: a POST /v1/sales of its own, TransactionType RFND. | 4. The POS journey, A refund |
| 6 | Link a register to a terminal at the counter, by the word the terminal shows and the staff member types. | Linking a register to a terminal, and what the POS shows at each answer |
| 7 | Managing your registers: your own admin server lists a register for each till, and each call for a till names its register in Mw-Register. | Onboarding a server: 6. Name the register, 7. List a server’s register. Reference: the registers routes |
| 8 | The refusals a POS meets, and what to do after each. | Each route’s answers in the reference; 7. Codes the sandbox adds; mw://refusals on the MCP server |
| 9 | Prove it: enrol your POS as your world’s server, then run the POS conformance scenarios and keep the signed report. | 4. The POS journey, step 8; 6. Conformance |
| 10 | From the sandbox to a live middleware. A new key and a certificate in place of the sandbox key, then registers and links at real stores. | From the sandbox to staging; Onboarding a server; a POS app on a device: Onboarding a device |
Your guide
Integrating your POS with FUNDiMO is the same path as one document, from a sandbox key to registers that take payments for real merchants. It is also a PDF.
For your AI coding assistant
The sandbox serves these pages at /llms.txt, and through its MCP server at POST /mcp:
3. The MCP server.