Payment gateway simulator

Test the payment paths
you can't trigger in staging.

A self-hosted sandbox that speaks the 2C2P and Omise APIs. Point your integration at it and reproduce a declined card, a duplicate webhook, a timeout, or a callback that arrives twice out of order — on demand, in seconds.

Open the dashboard

No sign-up. The demo creates a real transaction, delivers its callback, and shows you exactly what the merchant received.

What it does

Speaks the real API shapes

Token requests, inquiries, charges and webhooks follow the providers' published schemas, down to the response codes. Your integration needs no sandbox-specific branches.

Drives the failure cases

Set a payment to declined with code 4010, make an inquiry time out, force a duplicate callback, or add latency — the paths that are painful to reproduce against a real gateway.

Callback sequences

Build an ordered sequence with delays between steps: pending, then success, then a duplicate. This is how you prove your webhook handler is actually idempotent.

Built-in callback inspector

A callback endpoint inside the sandbox captures what was delivered, headers and all. No external request-bin, no tunnel to your laptop.

How it fits your stack

Your backend Unchanged integration code
Paygate Sandbox Stands in for the gateway
Your webhook Receives the callback

Swap one base URL in your configuration. Everything else stays as it is in production.

Try it from your terminal

Create a payment exactly as your backend would, then watch the callback arrive.