Alternative Payment Methods
Alternative payment methods let a merchant accept non-card payments without building a separate integration for every local rail. A customer can pay through a banking app, wallet redirect, QR code, or cash reference while Migo coordinates the transaction lifecycle through the Migo API.
The API Reference remains the source of truth for schemas, fields, status codes, and live endpoint definitions.
At a glance​
POST .../transactions ──► transactionId + enabled methods
│
â–¼
POST .../transactions/{id}/payments ──► rail instruction (URL · QR · reference)
│
â–¼
Customer pays outside your app ──► Migo confirms the result
The full step-by-step lifecycle is in How it works.
Integration path​
- Overview — how the flow differs from card payments
- How it works — end-to-end lifecycle from checkout to confirmation
- Available payment methods — rails available per country
- Create transaction — open a transaction
- Process payment — start the payment on a transaction
- Payment intents — create a payment intent on a transaction
- Dismiss transaction — cancel an open transaction
- Become a payment provider — integrate your wallet/rail into Migo
For technical detail, browse the live Alternative Payments tag in the Migo API reference.