Integration recipes

Per-country, copy-paste recipes for accepting every payment rail Migo exposes. Each recipe is self-contained — pre-requisites, exact curl, expected response, webhook payload, sandbox data, common errors, and a final checklist — so an integrator (or an agent like Claude Code) can finish the integration without leaving the page.

Country × rail matrix

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

Country	Wallets / push	Bank transfer	QR	Hosted button	Cash
Guatemala	zigi	—	akisiQR, bancoIndustrial, quickPayQR	bamPaymentButton	pronet
El Salvador	—	—	quickPayQR	—	—
Honduras	—	—	quickPayQR	—	—
Costa Rica	—	—	quickPayQR	—	—
Colombia	nequi	globalPay-PSE	—	—	—
México	—	—	—	—	—
República Dominicana	—	Payment Link card flow → azul	—	—	—

All recipes use the QA / sandbox environment — 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 — see the agent-friendly template for the full breakdown:

1. Pre-requisites — credentials, env, clientConfig flags expected.
2. Step 1 — Set the merchant token (Authorization: Bearer <token>) — no login round-trip; see Authentication → Merchant token.
3. Step 2 — Create the transaction and capture paymentMethods.
4. Step 3 — Run the rail-specific flow (with payment-intents first if required).
5. Step 4 — Listen for the webhook and verify its signature.
6. Sandbox data for that rail (test phones, test coupons, fixture QR).
7. Common errors (MigoCodeErrors) and how to react.
8. Done checklist — the precise outcomes the agent must confirm.

Quick links

• Authentication — the long-lived merchant token used by the Alternative Payments and Payment Link surfaces.
• Available payment methods — country-filtered rail catalog.
• Error catalog — MigoCodeErrors reference.
• Live API spec — Migo Middleware (Scalar).

For agents (Claude Code, Cursor, etc.)

The recipes are deliberately atomic. To integrate QuickPay QR in El Salvador you only need /recipes/el-salvador#quickpay-qr-quickpayqr. To integrate every Colombia rail you only need /recipes/colombia. The matrix above maps every (country, rail) pair to its recipe.

For machine-readable indexes that summarize this catalog without prose, see /llms.txt and /llms-full.txt.