Terminal Payments Overview
Topology
┌────────────┐ EMV ┌──────────────┐ HTTPS ┌──────────────┐
│ Cardholder│──────►│ POS terminal │────────►│ Migo platform│
│ │ │ │ │ │
└────────────┘ └──────────────┘ └──────┬───────┘
│
card network / issuer
│
settled by Migo
Terminology
- Device — The Android phone running the Tap to Phone app, identified by
deviceId(the device's unique identifier, e.g.device-abc123). It is provisioned automatically when the owner registers for the branch — see Terminal Payments. - Terminal — A device that has been provisioned for a branch. Card-present charging is enabled after information verification and onboarding with the acquiring processor; a terminal can accept card payments and the alternative payment methods available in its country.
- Affiliation — The merchant identifier issued by the acquirer. Each terminal is associated with one affiliation.
Relationship with online card payments
| Dimension | Terminal payment | Online card payment |
|---|---|---|
| PAN source | Chip / contactless / swipe | Tokenized (cardId) |
| PCI scope | SAQ-P2PE | SAQ-A / SAQ-A-EP |
| 3DS | Not applicable | Supported |
| Settlement | Settled by Migo | Settled by Migo |
Supported card-present scenarios
- Chip + PIN (EMV) — default for GTQ issuers
- Chip + Signature — American Express
- Contactless (NFC) — Visa payWave, Mastercard PayPass, Amex ExpressPay
- Magstripe fallback — only when chip fails (issuer-configurable)
Apple Pay / Google Pay at the POS work via the contactless path if the terminal hardware supports NFC.
What's not in scope
- Remote (cloud-managed) terminals — no Migo equivalent today.
- An iOS Tap to Phone app — the app is Android only; an iOS version is not yet available.
- Direct-to-acquirer flows that skip Migo — if you need those, you'd work with the acquirer directly.