Platform Architecture
From an integrator's perspective, Migo exposes four public REST APIs over HTTPS. You authenticate, call an endpoint, and receive a standardized JSON response. Everything behind those endpoints is Migo's responsibility and is not part of the contract you integrate against.
Public surfaceβ
Your application (web, mobile, or backend)
β
β HTTPS + JWT
βΌ
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β Wallet Gateway api.ali.app/rest β
β Middleware API mw.migopayments.com β
β Migo Payments Gateway api.migopayments.com β
β Credits API v2 api.migopayments.com/v2/credits β
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Each API speaks plain HTTPS + JSON. You never connect to anything else β there is no direct database access, no message bus, and no private endpoint you call.
Responsibilitiesβ
| API | What you use it for | What it does NOT do |
|---|---|---|
| Wallet Gateway | Users, cards, wallets, terminals, settlements β the building blocks of a card/wallet program | Recurring billing (use the Middleware) |
| Middleware | Hosted Payment Links, the subscription engine, BIN verifications, fraud suspensions | Card issuance (use the Wallet Gateway) |
| Migo Payments Gateway | Transaction search and health probes during the MigoβALI transition | Everything else: it is an early-access migration gateway |
| Credits API v2 | Bank affiliation, account lookup and the credit transaction lifecycle (Credit Core) | Card or wallet payments |
The Migo Payments Gateway is early access: integrators are onboarded to it explicitly by Migo. If you have not been given its base URL, you do not need it.
Pick the surface by the resource you need. A given business object (a card, a transaction, a settlement) is owned by exactly one surface; the API reference tells you which.
Request flow β example: transfer between cardsβ
- Your app calls
POST /cards/transferon the Wallet Gateway to move funds between two cards in the same ecosystem. - Migo validates your JWT and your application/user permissions, validates both cards and balances, and performs the movement.
- The Gateway returns the standardized
CustomResponse<T>envelope with the result (approved / denied).
You only ever see the request you send and the response you receive. Migo handles routing, balance validation, and processor coordination internally.
POST /cards/{cardId}/statements is not a charge β it asks Migo to generate a monthly card statement (a PDF, produced asynchronously) and takes { month, year }. Other money-movement endpoints include PUT /cards/{cardId}/funds (load/unload card balance) and the POS / terminal-payment flow.
Long-running operationsβ
Some operations don't finish within a single request:
- Statement generation returns
201 Createdwith a job reference; the PDF is produced asynchronously.
Treat any response that hands you a job/batch id as asynchronous and poll for the result rather than blocking.
Observabilityβ
Each request is correlated to an internal trace. When you open a support ticket, provide the request timestamp and the full request/response details (with the Bearer token and any PAN/CVV redacted) so Migo can correlate it to the trace.