Read the spec.
Then call it.

Docs and simulation need no account. A sandbox key follows a verified work email. A live key follows cleared business Know-Your-Business (KYB).

Three steps.

Open docs first, then sandbox, then production after KYB. Default clearing toll: 50 basis points (bps) on the dispatched amount (0.50%), $1.00 minimum per release. The payee receives the dispatched amount. Pricing.

  • Read

    Follow the Quickstart, read the API reference, and run the open simulation. No key. See API Access for which hostname does what.

  • Sandbox

    Submit name, work email, and company on Sandbox. After you verify the inbox, you receive a gsk_sandbox_… key for signed requests. Issuance follows verification. It is not instant.

  • Production

    gsk_live_… requires business KYB at Production. A cleared vendor decision issues the key. A flagged or rejected decision does not. Read Compliance first.

Call once. Listen for every change.

One host for sandbox and production. Bearer keys on initiate; signed webhooks at each transition — or poll status if you miss an event.

  1. Initiate with one key. Send the dispatched amount (or your budget cap) and toll terms on the request with an Idempotency-Key. Retries with the same key return the original settlement.
  2. Track every transition. Signed webhooks fire at each status change. If one is missed, poll GET /v1/settlement/status/{id}. Dispatched amount, clearing toll, and reserve debit stay on the record.
  3. Reconcile the named states. Finance and engineering read the same labels from staged through settled — see Platform for the full map.
  4. Start from the published spec. The OpenAPI JSON and Quickstart cover the settlement and status routes — not every internal route.

View API documentation

Questions? Answers.

  • Read the API Documentation, run the open simulation, and download the OpenAPI JSON. The published spec covers the settlement and status routes. It is not an exhaustive list of every internal route.

  • You should. Sandbox runs the same pipeline with a gsk_sandbox_… key against the same hostnames. Production still requires business KYB and a cleared vendor decision before a gsk_live_… key is issued.

  • On the API. Signed webhooks fire at each transition with the same dispatched amount, clearing toll, and reserve debit as the clearing record. If delivery fails, poll the status route. See the Quickstart for verify-and-retry patterns.

  • api.gutschow.xyz for settlement and status. Docs and the open simulation on docs.gutschow.xyz. Hostname roles are listed on API Access.

  • No. OpenAPI documents the settlement and status routes your integration calls. Operator and internal routes are not part of the public contract.

  • After the work inbox is verified on the Sandbox page. Issuance follows verification-it is not instant and keys are not shown in the browser.

Same rails.
Two doors.

Sandbox

$0 to test.

Simulated clearing.
Work email required.

Production

From $900/month.

Live clearing.
License and toll apply.