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

Column	Meaning
Method	Value to send in body.processor of POST /api/v1/integrations/transactions/{transactionId}/payments.
How the customer pays	The 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 returned	The 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 pays	Pre-call /payment-intents?	data.type returned
zigi	Wallet redirect — the customer authorizes inside the Zigi app	No	url
akisiQR	Akisi wallet — scannable QR image	No	base64
pronet	Cash references payable at Pronet convenience stores	No	json
bancoIndustrial	Banco Industrial push QR	No	base64
quickPayQR	Interbank QR aggregator that resolves to the customer’s bank app	No	json
bamPaymentButton	BAM hosted page — the customer completes payment on BAM’s domain	No	url
fri	Push-payment fixture used to simulate a wallet authorization (test/sandbox)	Optional	json

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.

Next steps

• Create transaction — see how data.paymentMethods is returned.
• Process payment — the unified body and the data.type payload to render.
• Browse the live spec under Alternative Payments.