Terminal Payments Overview
Topologyβ
ββββββββββββββ EMV ββββββββββββββββ HTTPS ββββββββββββββββ
β CardholderββββββββΊβ POS terminal ββββββββββΊβ Migo platformβ
β β β β β β
ββββββββββββββ ββββββββββββββββ ββββββββ¬ββββββββ
β
card network / issuer
β
settled by Migo
Terminologyβ
- Device β The Android phone that embeds the Tap to Phone SDK, identified by its
deviceId(delivered by the SDK inonDeviceIdResponse). Each device is its own terminal. - Terminal β The terminal the SDK registers automatically under the branch (
branchId) the first time it initializes on a new device, and which requests activation via a ticket (Guatemala). Once active, it accepts card-present charges. See Terminal registration and activation. - 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.