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.

Use this section to understand the merchant-facing flow before jumping into request and response details. The API Reference remains the source of truth for schemas, fields, status codes, and live endpoint definitions.

How the flow works — at a glance

1. Create a transaction          POST .../transactions            ──►  transactionId
        │
        ▼
2. Start the payment             POST .../transactions/{id}/payments
        │
        ▼
3. Customer pays                 bank app · wallet redirect · QR · cash reference
        │
        ▼
4. Async confirmation            Migo confirms the payment out-of-band
        │
        ▼
5. Fulfillment                   merchant releases the order once confirmed

What you can build

• A checkout that offers local rails alongside card payments.
• A QR or wallet-based payment flow for mobile users.
• A cash-reference flow for customers who prefer paying at a physical location.
• A merchant order flow that waits for asynchronous confirmation before fulfillment.

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.