Inspector

Payments

Change a payment's status or send its callback to see what your integration receives.

payments

pending

success

not paid

Provider

Method

Status

Invoice	Provider	Method	Amount	Status	Callbacks	Created	Actions
Loading payments…

Loading…

Requests and responses

Type

TTL: 7 days

Time	Type	Invoice	Method	Path	Status	Duration	Actions
Loading logs…

Loading…

Settings

These apply to every API request the sandbox receives.

Delay on every response

Milliseconds added to every API response.

Force an error (2C2P)

Every 2C2P request answers with this code.

Force an error (Omise)

Every Omise request answers with this code.

Failure rate

The share of requests that fail at random, in percent.

Duplicate callbacks

Send callbacks twice To test that your system acts on a repeated callback once.

Refresh the list by itself

Check for new payments every 60 seconds Each open dashboard asks once a minute, 60 requests an hour. With several people watching, that adds up against your hosting plan's monthly usage.

Change status

Invoice:

New status

Response code The response code the payment will carry, and its callback with it.

Send a callback after the change

Send callback

Invoice:

Custom fields

Merged into the callback payload alongside the provider's own fields. Presets are set with customFieldPresets through POST /api/admin/config; there is no form for them yet.

Send one callback or several in a row, each with its own status and wait.

Tip: Add multiple callbacks to test idempotency, status changes, or retry patterns.

Edit the payload before it is sent, to see how your system handles a wrong amount or a broken field.

Payload (JSON)

Tip: Edit fields like amount, invoiceNo, or respCode to test how your system handles invalid payloads or mismatches.

Log details

Clear all payments?

Every payment is deleted, with its status history and callback history.

This cannot be undone.

Clear all logs?

Every request and response in the log is deleted.

This cannot be undone.