socket.help

Payment API sandbox

Simulate payment events, states, and failure cases.

Expires after 1 hour

Checking this session…

Import / export configuration
Request conditions & response templates

Templates accept {{path.id}}, {{query.name}} and {{body.name}} inside JSON strings or plain text. Missing values become empty strings. No code runs. Test credentials are stored in the configuration; use fake tokens only.

Up to 20 routes, 80 KiB total configuration, and 120 requests per minute. Paths support parameters such as /users/:id. Matching routes are checked in order.

Open an existing mock API
Guide & examples

About Payment API sandbox

Test success, decline, pending and refund client states against a disposable fake payment API.

When to use it

Test success, decline, pending and refund client states against a disposable fake payment API.

Payment API sandbox example
POST /payments/decline → HTTP 402 and a simulated decline

How to use it

  1. Configure the endpoint and choose private or public access.
  2. Create it and send requests from your client.
  3. Inspect test output, update or delete the resource when finished.

Limits & privacy

Uses an expiring mock resource, private by default, with separate management and access credentials. Public access is optional. Standard resource quotas, ownership, renewal and deletion apply. Private access tokens are sent in headers, never in share URLs. No money moves and no payment provider is contacted. Responses are independent static fixtures; no ledger, payment processing, provider signature verification or persistent payment state.

Use this tool from the API reference or connect through the SDK, CLI, SSH, or MCP. Hosted calls share your plan allowances.