Terminal Payments (Tap to Phone)
Migo provides an Android SDK to accept card-present payments without POS hardware: it uses the phone's NFC technology to read the card and charge it. You embed the SDK in your mobile app, and an NFC-capable Android phone becomes your payment terminal.
The SDK is Android only (minSdk 29) and the device must have NFC β that's where the card-present read runs. The full integration lives in SDK Install.
The end-to-end journeyβ
1. Migo provisions with you account (tenant/merchant) Β· user Β· business Β· branch
β (set up by your commercial contact, not via API)
βΌ
2. Integrate the SDK add migoSDK to your Android app and initialize it
β migoSDK.initService(merchantId, signature, authUserId, branchId)
βΌ
3. The terminal registers when new, the SDK creates it and requests activation via ticket (Guatemala)
β
βΌ
4. Migo activates the terminal activeTerminal = true βββΊ ready to charge
β
βΌ
5. Charge card present migoSDK.doTransaction(...) βββΊ voucher βββΊ doFinishTransaction(...)
β
βΌ
6. Settlement vehicle defined with commercial: card Β· bank account Β· balance
1. What Migo provisionsβ
Before you integrate, your Migo commercial contact provisions in your account the hierarchy that terminals are registered under:
- A Migo account (tenant / merchant).
- A user β its id is the
authUserIdyou pass to the SDK. - A business (comercio).
- A branch β where terminals are registered; its id is the SDK's
branchId.
You don't register these entities via API: they are part of commercial onboarding. Detail in SDK Install β Prerequisites.
2. The terminal registers itselfβ
The terminal is not provisioned up front: when the SDK initializes on a device and detects that the terminal is new, it creates it automatically under the branch and requests its activation by opening a support ticket (in Guatemala). Once Migo activates it, the terminal is ready to charge. Detail in Terminal registration and activation.
3. Charge card presentβ
With the terminal active, you run the charge from your app with migoSDK.doTransaction(...): the SDK reads the card over NFC, returns the data for you to confirm, and after authorization hands you the voucher; you finalize it to settle. Full flow in Process a Terminal Payment.
4. Settlementβ
Approved charges are settled to the vehicle associated with the business β card, bank account, or balance in the Migo platform β which you define with your commercial contact when the terminal is activated. Detail in Settlement.
Relatedβ
- Overview β hardware model, card scenarios, and PCI scope.
- SDK Install β repository, dependency, permissions, initialization, and activation.
- Process a Terminal Payment β the card-present charge and settlement.
- Cancel an in-progress charge β abort a charge that was never authorized.
- Reverse an authorized charge β undo an already approved charge.
- Payment webhooks β receive a signed notice on your server for every approved or denied payment.
- SDK Reference β every method, callback, enum, and entity.