Dispatched,
toll, and debit.
Every state
is named.

Your API request and the clearing record carry the same numbers.

Know where every payout stands.

From staged through settled, each label tells finance and engineering what is done and what is still in flight.

StatusWhat it guarantees
stagedAccepted and waiting for checks.
processingScreening and reservation are in progress.
initiatedOutbound movement has been requested on the partner rail.
confirmedThe partner rail's receipt. It is not a deposit Gutschow holds.
settledThe clearing book. Dispatched amount, clearing toll, and payee receipt are final there.
failed / rolled_backThe settlement stopped, or the reserve was released.

A signed webhook fires at each transition. If you miss one, poll GET /v1/settlement/status/{id}.

View API documentation

Five rules. Every settlement.

Same controls on every USDC and EURC payout: reserve, clearing toll, screening, and idempotency-before anything moves on the partner rail.

  1. Reserve first. Funds lock before anything moves on the partner rail. Release on settle or rollback.
  2. Fee once, at ingress. clearing_toll = max(round(dispatched_amount × fee_rate, 4), 1.0000); default 50 basis points (bps) on the dispatched amount (0.50%), $1.00 minimum per release. The payee receives the dispatched amount; the sender is debited the total reserve debit (dispatched plus toll on the default). Request and ledger match. Pricing.
  3. Screen before release. Sanctions on the destination, velocity limits, and Travel Rule metadata when the amount requires it. A vendor timeout stops the payout.
  4. One Idempotency-Key, one settlement. Retry with the same key and terms and you get the original back. Change the terms and the key is rejected.
  5. Less data at ingress. Blind Ingress Privacy limits what we store. It is not zero-knowledge cryptography.

Compliance

Three records. Three audiences.

Treasury reconciles events, engineering traces status, and operators record who decided what.

  1. Financial event ledger. Reserve, settle, and release with dispatched amount, clearing toll, and payee receipt on separate lines — built for reconciliation.
  2. Status trail. Every transition logged — idempotency key included.
  3. Operator trail. Approve, reject, or escalate — with actor, reason, and timestamp.

One API. Signed requests.

One host for sandbox and production, bearer keys, signed requests, and the public OpenAPI spec.

ItemValue
APIhttps://api.gutschow.xyz
AuthBearer API key (gsk_sandbox_… or gsk_live_…) and signed requests
AssetsUSDC, EURC
FeeDefault clearing toll: 0.50% (50 bps) on the dispatched amount, $1.00 minimum per release. Pricing.
SpecOpenAPI JSON
StatusHealth

Questions? Answers.

  • The clearing book closes in one operational cycle: reserve, toll, settled. confirmed is the partner rail receipt — not a Gutschow deposit, and not a promise that fiat lands everywhere same day.

  • Send the same Idempotency-Key with the same terms and you get the original settlement. A reused key with different terms is rejected.

  • No. It is not zero-knowledge. See the API contract and documentation for ingress privacy on your integration.

  • Licensed partner infrastructure. Gutschow does not take deposits.

  • It releases the reserve. Failed is different: the settlement stopped.

  • No. Gutschow settles in USDC and EURC, in one country or across borders. It is not a domestic USD Automated Clearing House (ACH) or wire product.

Same rails.
Two doors.

Sandbox

$0 to test.

Simulated clearing.
Work email required.

Production

From $900/month.

Live clearing.
License and toll apply.