Skip to main content
Migo Docs

Webhooks and notifications

The cr-webhooks service receives asynchronous callbacks from the bank, the collector and EventBridge. None of these endpoints go through Migo's TOKEN Authorizer.

Available webhooks​

EventMethodPathEmitter
Affiliation responsePOST/webhooks/merchants/{merchant}/users/{user}/banks/{bank}/affiliationsBank
Account updatePOST/webhooks/banks/{bank}/accounts/updatesBank
Collector paymentPOST/webhooks/collectors/{collector}/paymentExternal collector
Unbanked authorizationPOST/webhooks/unbanked/credits/authorizeMO (processor)
Automatic cancellationPOST/webhooks/transactions/cancellationMigo (automatic)

The affiliation response is documented in Bank affiliation and OTP, the account update in Account lookup and the automatic cancellation in Transaction lifecycle.

Collector payment webhook​

POST v2/credits/webhooks/collectors/{collector}/payment
Content-Type: application/json
Body (collector → Migo)
{
"transactionId": "txn-abc123",
"amount": 500.00,
"currency": "GTQ",
"status": "paid",
"date": "2026-02-01T10:00:00Z",
"reference": "PAY-001",
"fee": 5.00,
"externalEntityId": "ENT-1",
"externalTransactionId": "EXT-1"
}

Required: transactionId, amount, currency, status, date. Optional: reference, fee, externalEntityId, externalTransactionId.

Internal notifications​

Migo also handles internal notifications (notices to channels and merchants) that are not HTTP endpoints and are not part of your integration: they happen on Migo's side. You don't need to implement or consume them; they're mentioned only so you know they exist.

The error codes that may appear in a webhook's error object are in the Error catalog.