Test by Design
← All work

Payment gateway sandbox

Standalone. Your backend talks to it in the provider’s own request and response shapes, the callback comes back to your backend, and you drive what that callback says from the side.

Paygate sandbox Under test Your backend calls the gateway Its webhook the URL it registered Provider API 2C2P · Omise shapes Admin API drives the outcome Inspector captures callbacks POST /token with backendReturnUrl the provider's shape sets the result the callback you asked for settled · declined 4051 · duplicate · late or point the URL here and read what arrived

Scroll sideways to see the whole diagram.

The second door is where a test decides what comes back. One limit: this sandbox speaks plain JSON, not 2C2P’s JWT/JWE, so point an integration at it with encryption turned off.

The repository

Live

Paygate Sandbox

A sandbox that emulates the 2C2P and Omise payment APIs, so an integration can be tested against responses a real staging environment will not produce on demand.

Settle a transaction, decline it with a specific issuer code, make an inquiry time out, or deliver the same webhook twice out of order. A built-in callback inspector captures what the webhook would have received. Unofficial, and not affiliated with either provider.

Signing in with demo gives you ten sample payments of your own for a day, with callbacks delivered to your own inspector. The owner’s settings are read-only to you and the logs stay private, because both apply to everyone using the sandbox.

Open the sandbox Source API reference

Node, Vercel, Vercel KV

← All work
Test by Design