Two administrative operations manage the terminal itself rather than transactions.
Activation
POST /activation performs the terminal's first-run provisioning — binding it to its configuration. You will typically use it once per device during deployment, or after a factory reset. It follows the standard request/response model; a failed activation is a deployment issue to raise with Market Pay support, not something to retry in a loop.
Update
POST /update triggers the terminal to contact the Market Pay Terminal Management System (NTMS) to fetch its latest configuration and application versions, and to upload logs. Use it to pull scheduled updates on demand — for example, applying a configuration change during a maintenance window instead of waiting for the terminal's own schedule.
While the update runs, the terminal notifies progress to the POS via cyclic DisplayRequests — your integration should render or at least tolerate these intermediate messages rather than treating them as errors. After an update that restarts the payment application, expect the session to be gone: the standard recovery applies (Diagnosis until healthy, then re-Login — see Session and login lifecycle).
Warning
Do not trigger updates during trading hours on a live lane. The terminal may restart and the session will drop mid-shift.
Related
- Session and login lifecycle — post-update re-login and serial-number verification.