Skip to main content
Migo Docs

Integration recipes

Per-country recipes for the alternative-payment rails Migo exposes. Each one is self-contained: pre-requisites, the exact curl, the expected response, sandbox data and common errors.

Country × rail matrix​

The table covers the alternative-payment rails that have a recipe and that return a payload on POST /api/v1/integrations/.../payments. It is not an exhaustive processor list: additional keys (zigiQR, bbvaQR, push-payment-gateway) exist for specific clients and are resolved at runtime from each merchant's clientConfig.processors.

CountryWallets / pushBank transferQRHosted buttonCash
Guatemalazigi—akisiQR, bancoIndustrial, quickPayQRbamPaymentButtonpronet
El Salvador, Honduras, Costa Rica——quickPayQR——
ColombianequiglobalPay-PSE———
Dominican Republic—Payment link card flow → azul—bancoPopular—

Mexico has no alternative-payment rails wired: card charges run through payment links, which route to the configured card processor.

All recipes use the sandbox — https://sb-mw.migopayments.com for the Middleware. Switch to https://mw.migopayments.com when promoting to production.

How a recipe is structured​

Every page follows the same skeleton:

  1. Setup — the environment variables and the call that creates the transaction.
  2. Process the payment — the per-rail curl and its response shape.
  3. Status delivery — the merchant callback.
  4. Errors — the middleware error codes and how to react.

For a machine-readable index of this catalog, without prose, see /llms.txt.