# Migo Payments — Developer Portal

Migo is a payments infrastructure platform for Latin America. The portal documents three REST APIs:

- Wallet Gateway — `https://api.ali.app/rest` — issue cards, manage wallets, charge cardholders, run subscriptions.
- Migo Middleware — `https://mw.migopayments.com` — alternative payment methods, payment links, webhook router.
- CMS Backoffice — `https://api.ali.app/cms/rest` — partners, CMS users, permissions, bulk uploads.

QA / sandbox replaces the host with `mw.dev.migopayments.com` (Middleware) and `ali-qa.ali.app` (Wallet Gateway).

## Per-country recipes (start here when integrating)

- /recipes — country × rail matrix.
- /recipes/guatemala — bamPaymentButton, zigi, akisi/akisiQR, bancoIndustrial, quickPayQR, tigo, pronet, oky, applePayFac.
- /recipes/el-salvador — tigo, mo, quickPayQR, oky, applePayFac.
- /recipes/honduras — tigo, quickPayQR, oky, applePayFac.
- /recipes/costa-rica — quickPayQR, oky, applePayFac.
- /recipes/colombia — nequi, globalPay-PSE, wompi-pse, wompi-nequi, wompi-bancolombia, applePayFac.
- /recipes/mexico — applePayT1, applePayCyber.
- /recipes/dominican-republic — Payment Links only; card processing routed to azul.

Each recipe is self-contained: pre-requisites, exact `curl`, expected response, webhook payload, sandbox data, common errors, done checklist.

## Foundations

- /introduction/overview — what Migo is, what you can build.
- /introduction/authentication — Ed25519-signed login, JWT lifecycle, refresh.
- /introduction/environments — base URLs and environment matrix.
- /introduction/quickstart — first authenticated request in 5 minutes.
- /introduction/testing — sandbox limits, test cards, idempotency keys.
- /support/error-catalog — `MigoNameErrors` / `MigoCodeErrors` reference (range 7000–8099).

## Alternative payments

- /alternative-payments/overview — what APMs are and how they differ from cards.
- /alternative-payments/methods — country-filtered catalog of every rail.
- /alternative-payments/create-transaction — `POST /transactions`.
- /alternative-payments/payment-intents — when and how to fetch dynamic metadata.
- /alternative-payments/process-payment — unified body shape for `/payments`.
- /alternative-payments/dismiss-transaction — releasing unpaid transactions.
- /alternative-payments/processors — technical processor-key catalog.

## Payment Links

- /getting-started/create-payment-link — `POST /transactions` and `POST /transactions-hook`.
- /getting-started/payment-link-quickstart — copy-paste flow.
- /getting-started/payment-link-processors — card/wallet processors the hosted webview routes to.
- /card-payments/hosted-webview — branding, custom keys, template overrides.

## Webhooks

- /webhooks/overview — event taxonomy and delivery semantics.
- /webhooks/signature-verification — Node, Python, Go validators.
- /webhooks/retry-policy — back-off schedule and dedupe.
- /webhooks/event-catalog — every event Migo emits.
- /webhooks/merchant-generic-callback — Payment Link callback shape.

## Live API specs (Scalar)

- /api-reference/ali-api-gw-rest — Wallet Gateway.
- /api-reference/migo-api — Migo Middleware (alternative payments + Payment Links).
- /api-reference/ali-api-cms-rest — CMS Backoffice.

## Conventions

- All amounts are in minor units (e.g. 1000 = 10.00).
- All POST endpoints accept `Idempotency-Key`; retrying with the same key returns the original response.
- Every successful response is `{ "statusCode": 200, "message": "ok", "data": <T> }`.
- Errors are `{ "statusCode": <int>, "error": { "code": <number>, "name": "<MigoNameErrors>", "detail": "<string>" } }`.