Payment Link processors
Each Payment Link is processed by an acquirer or gateway enabled for your merchant account. The catalog below filters the active processors available for a Payment Link integration based on the country selected in the sidebar.
Availability per merchant. A merchant only sees the subset of processors enabled for its account. The list returned at transaction creation is the source of truth for what your frontend can render. If a processor below is missing for your account, contact Migo Operations to enable it.
How to read this catalog
| Column | Meaning |
|---|---|
| Processor | Acquirer or gateway that authorizes the charge created by the Payment Link. |
| Coverage | Countries where the processor is currently enabled. |
| Model | Settlement model — Gateway (the merchant settles directly), PayFac (Migo settles to the merchant). |
| Payment methods | Instruments accepted by the processor on the hosted webview. |
| Capabilities | Features supported on top of the basic charge: 3DS, reversals, refunds, installments, tokenization, captures, and anti-fraud. |
Showing Payment Link processors available in Guatemala. Use the country selector in the sidebar to switch markets.Active in Guatemala
Processor Coverage Model Payment methods Capabilities Cybersource Costa Rica, El Salvador, Guatemala, México, Panamá Gateway, PayFac Card FAC 3DS 2.0 Costa Rica, El Salvador, Guatemala, Panamá Gateway Card Visa Epay (SOAP) Guatemala Gateway, PayFac Card Visa Epay (REST) Guatemala Gateway, PayFac Card PusPayment Gateway Guatemala Gateway Card
Test cards
Sandbox test cards by processor live on a single page to avoid duplication: see Testing Your Integration, which lists the sandbox numbers filtered by the same country selected in the sidebar.
Apple Pay and country coverage
México has no alternative-payments /payments rails wired today. Card payments — including Apple Pay — are processed through the hosted webview via Payment Links, routed to t1pagos or visa-cybersource depending on the BIN. The webview presents Apple Pay where the device and merchant support it.
Apple Pay is not a processor key on the alternative-payments dispatch map: applePayT1 / applePayCyber exist only as revert/refund/capture aliases of the underlying Visa Cybersource processor, not as /payments rails. For Apple Pay charges, those aliases resolve to the Visa Cybersource void/refund.
Next steps
- Payment Link Quick Start — end-to-end walkthrough.
- Create a Payment Link — request shape and response fields.
- Customize the hosted checkout — UI behaviour of the webview the customer sees.
- Merchant callback (webhook) — how the result of the charge is delivered back to your backend.