Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

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.

#StepWhere it is
1Take 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
2Connect and hold the WebSocket; reconnect after a cut.Terminal contract: Connect, Hold, Reconnect
3Take an instruction, send its outcome, one payment at a time, within its deadline.Instruction, Outcome, Which TransactionStatus to send
4Refund, status request and abort.A refund, StatusRequest, Abort
5Show the link word when a register asks to link.Linking to a register; 3. Each terminal shows its word
6Sign a person in, if your terminal declares SASQ.Signing in
7What 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
8Prove it: run the terminal conformance scenarios and keep the signed report.6. Conformance
9Enrol a device, from its code to its certificate and renewal.Onboarding a device
10From 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.