Skip to main content
Migo Docs

Available payment methods

These are the alternative payment methods that return a live /payments response, filtered by the country selected in the sidebar. The value in the first column is what you send in body.processor when you process a payment.

The runtime source of truth is per transaction

A merchant only sees the subset of methods enabled for its account. The authoritative list for a given transaction is the data.paymentMethods array returned by POST .../transactions — read it from your own response rather than hard-coding the table below. If a method you expect is missing, contact Migo Operations to enable it.

How to read this table​

ColumnMeaning
MethodValue to send in body.processor of POST /api/v1/integrations/transactions/{transactionId}/payments.
How the customer paysThe experience the customer completes (wallet app, QR scan, bank button, cash voucher).
Pre-call?Whether you must call /payment-intents first to fetch dynamic metadata. Most Guatemala rails do not.
data.type returnedThe shape returned in data.type so your frontend knows how to render it — url, base64, or json.

Showing the alternative payment rails that return a /payments response in Guatemala. Use the country selector in the sidebar to switch markets.

Processor (body.processor)How the customer paysPre-call /payment-intents?data.type returned
zigiWallet redirect — the customer authorizes inside the Zigi appNourl
akisiQRAkisi wallet — scannable QR imageNobase64
okyQROKY wallet — scannable QR imageNobase64
pronetCash references payable at Pronet convenience storesNojson
bancoIndustrialBanco Industrial push QRNobase64
yoloQRYOLO wallet (Bantrab) — scannable QR imageNobase64
quickPayQRInterbank QR aggregator that resolves to the customer’s bank appNojson
bamPaymentButtonBAM hosted page — the customer completes payment on BAM’s domainNourl
friPush-payment fixture used to simulate a wallet authorization (test/sandbox)Optionaljson
akisiQR returns base64, not json

For akisiQR the response returns data.type: "base64" and data.data as a complete data:image/png;base64,… URI ready to drop into <img src=...>. See Process payment → Response shape by data.type.

okyQR supports neither revert nor refund

The provider does not expose those operations, so okyQR has no entry in the revert or refund paths. Like the other Guatemalan QR rails it operates in GTQ, requires no pre-call, and returns data.type: "base64" carrying a data:image/png;base64,… URI ready for <img src=...>.