Platform

Gross, fee, and net. 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.

Status	What it guarantees
`staged`	Accepted and waiting for checks.
`processing`	Screening and reservation are in progress.
`initiated`	Outbound movement has been requested on the partner rail.
`confirmed`	The partner rail's receipt. It is not a deposit Gutschow holds.
`settled`	The clearing book. Gross, fee, and net are final there.
`failed` / `rolled_back`	The 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, fee, screening, and idempotency—before anything moves on the partner rail.

Reserve first. Funds lock before anything moves on the partner rail. Release on settle or rollback.
Fee once, at ingress. platform_fee = max(round(gross × 0.005, 4), 1.0000); default 0.50% (50 bps) of gross, $1.00 minimum per release; net to four decimals. Request and ledger match. Pricing.
Screen before release. Sanctions on the destination, velocity limits, and Travel Rule metadata when the amount requires it. A vendor timeout stops the payout.
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.
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.

Financial event ledger
Reserve, settle, and release with gross, fee, and net — built for reconciliation.
Status trail
Every transition logged — idempotency key included.
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.

Item	Value
API	`https://api.gutschow.xyz`
Auth	Bearer API key (gsk_sandbox_… or gsk_live_…) and signed requests
Assets	USDC, EURC
Fee	0.5% of gross, at ingress
Spec	OpenAPI JSON
Status	Health

Questions? Answers.

What does same-cycle mean?

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

What happens if we retry a request?

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

Is Blind Ingress Privacy zero-knowledge?

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

Who holds the stablecoin?

Licensed partner infrastructure. Gutschow does not take deposits.

What does rolled back do?

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

Can we send a domestic USD wire through this?

No. Gutschow settles in USDC and EURC, in one country or across borders. It is not a domestic USD ACH or wire product.

Prove it in the sandbox.

Run one USDC or EURC settlement. Keys after work-email verification.

Get sandbox access