Cloud API POS ecr-api v1.1.11

Operations · one panel per API endpoint

⚙ Connection settings

The single place to see & edit the connection. Saved to config.json server-side and applied live — the mTLS cert/key stay on the server and are never exposed. Note: the connection is global (one certificate) — these values are shared by everyone; only each person's transaction list & log are private.

This tool targets pre-production only — production is intentionally not selectable.

When a transaction returns 202 (async), staging POSTs the final result to this URL (correlated back to your session over SSE). It's publicBaseUrl + an unguessable token, and must be publicly reachable over HTTPS.

POST /process-transaction/{terminal-id}

ecrParams

ecrId and notificationUrl are injected by the server.

POST /cancel-transaction/{terminal-id}

POST /abort-transaction/{terminal-id}

ecrParams (optional)
GET /last-transaction/{terminal-id}

POST /update-terminal/{terminal-id}

⏱ A terminal update can take 2–3 minutes — the request stays open until the terminal finishes; don't close the tab.

ecrParams (optional)
GET /terminals

Lists every terminal registered to the current storeCode, with its live connection state. The ↻ Refresh terminals button in the bar above runs the same call and fills the selector.

Dummy-server BRC amount cheat-sheet (reference only)

Reference for the staging dummy server — read only, type the amount yourself.

amount (€)Behaviour
11.16Insufficient funds (declined)
16.00 – 17.99Partial authorisation
18.xxSignature required
19.07~30 s issuer delay
19.09Offline / forced-offline
Market Pay terminal IDLE
—
—
Waiting for an operation…

Live messages · newest first

No transactions yet. Refresh terminals, then send a transaction.

Developer console integration reference

Connection & identity

The tool authenticates to the Cloud API with a client certificate over mutual TLS (mTLS) — this is required; it's how staging verifies the caller (there's no API key or login). The certificate + private key live on the server and are never sent to the browser. The rows below are read-only diagnostics of the live connection.

loading…

Change the editable values (storeCode, ecrId, terminal, environment…) in Connection settings at the top-left. Cert/key are not editable from the browser.

Outbound — every call to the Cloud API (secrets redacted)

0 calls
No API calls yet.

Inbound — received on your notificationUrl

The Cloud API POSTs a Notification to ecrParams.notificationUrl for progress updates and, after a 202, for the final result. These are the exact bodies your own webhook endpoint has to handle. Delivery is one-shot and never retried.

0 received
Nothing received yet.