API reference
Five interfaces, one platform. Which one you need depends on where the payment starts — a web checkout, a terminal at the counter, or a system of yours that drives both.
E-comm API →
Websites, hosted checkout, embed checkout, payment links and the shop plugins. Token auth, payment creation, status queries, Request-to-Pay push, signed merchant callback, public-key retrieval.
POS API →
What hardware terminals and SoftPOS apps speak: activation, seller auth, the working day, QR transactions, refunds, settings. Interactive Redoc reference and a Postman collection alongside.
External Integration API →
For back-office and ERP systems that drive miaPOS from the outside — endpoints, schemas, examples, error codes.
Webhooks →
How miaPOS notifies your backend when a payment changes state. Signed, idempotent, retried with backoff.
Signature verification →
The authoritative algorithm for the RSA signature on every E-comm callback, with reference implementations in Java, Python, PHP and Node.js. Verify before you fulfil the order.
Before you start
Every API here shares the same ground rules — environments and base URLs, how credentials are issued, and how errors come back. Read those once and the rest is per-surface detail: Sandbox & environments · Authentication · Errors.
Not writing code against the raw API? For an online shop, a ready plugin is usually the shorter road — WooCommerce, OpenCart, CS-Cart or the PHP SDK.
Developer-facing documentation is published in English only.