Skip to main content
Migo Docs

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 Cheat Sheet.

Test cards​

The applicable card processor depends on the merchant's country and processor configuration. For Guatemala, the card processor is Cybersource. Use the table that matches your assigned processor.

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).

Cybersource​

TypeCard NumberComments
MC2222420000001113Valid
MC5200000000001013Invalid
VISA4111111111111111Valid
VISA4456530000001096Valid (with 3DS)
VISA4000000000001018Invalid
VISA4000000000000002Decline transaction

FAC 2​

TypeCard NumberComments
AMEX341111000000009Fluid
AMEX341112000000001Manual
VISA4012010000020070Fluid
VISA4012010000020088Fluid 2
VISA4012000000020006Manual
VISA4012000000020121Invalid
MC5100271000000120Fluid
MC5100270000000031Manual
MC5100270000000098Invalid

Visa Epay Soap​

TypeCard NumberComments
VISA4000000000000416Valid
VISA4000000000001111Invalid
MC2223000010025549Valid
MC2223000010021111Invalid

Visa Epay Rest​

TypeCard NumberComments
VISA4012000000020006Valid 01
MC5100270000000031Valid 01
VISA4456530000001005Step 3
VISA4456530000000007Step 5
MC5200000000001005Step 3
MC5200000000000007Step 5

PusPayment Gateway​

TypeCard NumberComments
MC2222480060123454Debit
MC5471910058177097Debit
VISA4000000000000416Debit
MC5471510010000007Credit
MC5471910010000015Credit
MC5471910140000000Credit
MC5471910140000018Credit
VISA4000000000005944Credit

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.
ScenarioWhy
Happy-path charge + webhookBaseline integration
Declined chargeEnsure you surface the error to the user
3-D Secure decline (test card)Retry flow
Network timeout + retryYour client handles transient failures safely and idempotently
Webhook signature mismatchYour verification rejects forged events
Webhook replay of duplicate eventYour handler is idempotent