v2026-04-09·Latest version

Commerce API reference.

A POS-facing API for certified EMV L2 payment terminals. Drive transactions through three connectivity models — local network, cloud relay, or embedded SDK — with orchestrated or granular acquirer flows.

Quickstart→API reference Test cards →

CONNECTIVITY

Three paths into the terminal

Every endpoint in this reference works against both Local and Cloud base URLs with identical schemas, status codes, and semantics.

Local Connected

~8ms

POS talks to the terminal over the LAN. Lowest latency, offline-capable.

http://terminal:8443

Cloud

~90ms

POS routes through Atlas to the terminal over a persistent tunnel.

https://api.atlas-softpos.com

Local Embedded

~2ms

Direct Kotlin SDK integration inside the merchant app.

sdk · kotlin

See full topology diagrams →

TRANSACTION MODES

Orchestrated or granular

Orchestrated

The terminal owns the full lifecycle. You make a single call to /v1/transaction/sale and wait for the result. The simplest path when you don't need to touch the acquirer yourself.

Granular

The terminal returns raw EMV chip data. Your POS routes the authorization, then calls /v1/transaction/complete. Enables multi-acquirer routing and store-and-forward.

See the side-by-side flow diagrams →

REFERENCE