Welcome to Nami
Integrate Nami payment terminals with your POS, ERP, SaaS platform, or unattended machine. Start from your use case and get to a working transaction fast.
Integrate Nami payment terminals with whatever you're building — a cashier app, an ERP, a cloud platform, or an unattended machine. Start from the use case that matches you, then run your first transaction with the Quickstart.
Start from your use case
🧾
App on the terminal
A cashier or POS app running on the Nami Android device itself,including field sales. Use App-to-App.
📱
Mobile / Tablet / Kiosk
A phone or tablet or kiosk POS app driving a separate terminal. Use a Mobile SDK (Android, iOS, Flutter, React Native).
🖥️
Windows POS / on-prem ERP
A desktop cashier or on-prem ERP with USB or TCP/IP connectivity to the terminal. Use the .Net / C /Java SDK
☁️
For local REST API, SaaS / cloud / multi-site
A on-prem/private cloud/SaaS application connecting to terminals across many locations, with reachability to terminals via the end users PC. Use the Local Middleware with HTTP/HTTPS REST API calls.
☁️
SaaS / cloud / multi-site
A web or SaaS platform driving terminals across many locations, server-to-server. Use the Cloud Middleware with webhooks.
⚡
Just show me the quickstart
Connect, register, start a session, and run your first purchase in about 15 minutes.
Or pick by integration type
| If you want to… | Use | Language |
|---|---|---|
| Embed a library in your app | Native SDK — Android, iOS, Flutter, React Native, .Net, C/C++ | Platform language |
| Call a local HTTP API on a Windows POS | Local API Middleware (REST) | Any |
| Call a hosted API with nothing installed locally | Cloud Middleware (REST) | Any |
| Hand off from your Android app on the device | App-to-App (part of the Android SDK) | Android |
References
- Transaction Types — Canonical transaction type codes.
- Transaction Response Codes — mada scheme and Nami ECR codes.
- Test Cards — Cards for testing in the UAT environment.
Updated about 1 month ago
Did this page help you?