Testing Your Integration
Migo's QA / Sandbox environments accept test cards so you can cover the happy path, authentication errors, and rejection scenarios before going to production. For base URLs and credentials, see Environments & Base URLs and the Sandbox Quickstart.
Test cardsβ
The applicable card processor depends on the merchant's country and processor configuration. The table below is the portal's single source of sandbox test cards: it shows only the processors active in the country selected in the sidebar β switch markets to see the cards for another set of processors.
Declines and other outcomes come directly from each processor, with the processor's own response codes. Use any future expiry and any valid CVV (4 digits for Amex, 3 digits otherwise), unless a specific card row says otherwise.
Showing test cards for the Payment Link processors active in Guatemala. Use the country selector in the sidebar to switch markets. Test cards only authorize transactions in sandbox environments.Active processors in Guatemala
Cybersource
Type Card Number Comments MC 2222420000001113Valid MC 5200000000001013Invalid VISA 4111111111111111Valid VISA 4456530000001096Valid (with 3DS) VISA 4000000000001018Invalid VISA 4000000000000002Decline transaction FAC 3DS 2.0
Type Card Number Comments AMEX 341111000000009Frictionless AMEX 341112000000001Manual VISA 4012010000020070Frictionless VISA 4012010000020088Attempted 3DS (A): declined unless the merchant accepts attempted authentication VISA 4012000000020006Manual VISA 4012000000020121Invalid MC 5100271000000120Frictionless MC 5100270000000031Manual MC 5100270000000098Invalid Visa Epay (SOAP)
Type Card Number Comments VISA 4000000000000416Valid VISA 4000000000001111Invalid MC 2223000010025549Valid MC 2223000010021111Invalid Visa Epay (REST)
Type Card Number Comments VISA 4012000000020006Valid 01 MC 5100270000000031Valid 01 VISA 4456530000001005Step 3 VISA 4456530000000007Step 5 MC 5200000000001005Step 3 MC 5200000000000007Step 5 PusPayment Gateway
Type Card Number Comments MC 2222480060123454Debit MC 5471910058177097Debit VISA 4000000000000416Debit MC 5471510010000007Credit MC 5471910010000015Credit MC 5471910140000000Credit MC 5471910140000018Credit VISA 4000000000005944Credit
3-D Secure test flowβ
3DS-enrolled test cards (for example, Cybersource VISA 4456530000001096) drive the challenge and approval/decline outcome. Behavior is determined by the test card rather than a request field.
Webhook testingβ
- Local development: use a tunnel (ngrok, cloudflared) and register your tunnel URL in the Migo dashboard.
Recommended test matrixβ
| Scenario | Why |
|---|---|
| Happy-path charge + webhook | Baseline integration |
| Declined charge | Ensure you surface the error to the user |
| 3-D Secure decline (test card) | Retry flow |
| Network timeout + retry | Your client handles transient failures safely and idempotently |
| Webhook signature mismatch | Your verification rejects forged events |
| Webhook replay of duplicate event | Your handler is idempotent |