Release v0.3.1, 21-Nov-2026 · all releases
Building a terminal
From a sandbox key to terminals that take payments for real merchants, in order. Each step names the page and section that hold its detail. The terminal contract is the WebSocket a terminal builds against, and walks each of its frames; the API reference for a terminal holds its HTTP routes.
| # | Step | Where it is |
|---|---|---|
| 1 | Take a sandbox key, and read your world: its store, its terminals, and how each answers. | The sandbox: 1. A key and a world, 5. The terminal journey |
| 2 | Connect and hold the WebSocket; reconnect after a cut. | Terminal contract: Connect, Hold, Reconnect |
| 3 | Take an instruction, send its outcome, one payment at a time, within its deadline. | Instruction, Outcome, Which TransactionStatus to send |
| 4 | Refund, status request and abort. | A refund, StatusRequest, Abort |
| 5 | Show the link word when a register asks to link. | Linking to a register; 3. Each terminal shows its word |
| 6 | Sign a person in, if your terminal declares SASQ. | Signing in |
| 7 | What a terminal sends back: the references by kind, and the allow-list a value passes. | References by kind, A value that fails is dropped alone |
| 8 | Prove it: run the terminal conformance scenarios and keep the signed report. | 6. Conformance |
| 9 | Enrol a device, from its code to its certificate and renewal. | Onboarding a device |
| 10 | From the sandbox to a live middleware. | From the sandbox to staging, A terminal’s app |
Your guide
Integrating your terminals with FUNDiMO is the same path as one document. It is also a PDF.