Screened
before it ships.
Both books can
match.

A payout is held and screened before it can leave. Release or rollback is a named outcome.

What this page covers.

Most send products move first and explain later. Gutschow does the reverse. We hold, screen, then release or roll back — leaving a record that finance and external reviewers can recompute from the same source.

This page is the trust index. It is built for the teams who stand behind a payout: engineering, security, finance, and vendor risk. You will find the order of a live release, our three audit roles, how status is delivered, and where data lives.

You can test screening in the Sandbox. Live keys follow business Know-Your-Business (KYB) at Production.

Cleared before release.

Production KYB.

Live keys require business KYB verification of the legal entity and beneficial owners. A cleared vendor decision issues the key; a flagged or rejected decision does not. Payees are not onboarded as separate Gutschow customers; they appear as counterparties on the settlement.

At ingress.

Every live settlement is evaluated before funds move on the partner rail. Sanctions and velocity apply on that payout. Travel Rule data applies when the amount requires it. The table at Compliance. A failed check or a screening timeout blocks release. There is no fallback path to send anyway and screen later.

Reserve.

While checks run, funds are reserved. Outcomes are explicit: release (the payout may leave), rollback, or fail (the reserve is not dispatched). Same-cycle means the clearing state — not a guaranteed same-day bank credit in every destination country.

Sandbox vs. Production.

  • Sandbox. Exercises screening where it applies. It does not verify business identity or issue live keys. Start at Sandbox.
  • Production. Requires business KYB before keys are issued. Start at Production.

States and numbers.

Status labels are part of the contract. Sandbox and production use the exact same names, so engineering and finance argue from a single object rather than a dashboard screenshot and a bank export.

Two labels matter most:

  • Confirmed. The partner rail’s receipt.
  • Settled. Gutschow’s clearing book. A rail receipt is not a deposit held by Gutschow.

The record carries the dispatched amount, the clearing toll assessed at ingress, and the payee receipt. Request and ledger are designed to tie out. Full formulas and state maps live at Platform; pricing schedules live at Pricing.

Three audit roles.

A vendor review should not hunt through a single mixed log. Gutschow publishes three distinct roles so each audience gets an object tailored to their question:

  • Financial event ledger. Snapshots of reserve, settle, and release (dispatched amount, toll, and payee receipt). Built to be reconcilable.
  • Status-transition trail. Each state change paired with an idempotency key, preserving the pipeline history in exact order for disputes.
  • Operator action trail. Human approvals, rejections, or escalations attributed to a specific actor with a timestamp and reason. Machines never hide behind anonymous admin rows.

High-level role definitions are public. Storage internals and hash algorithms are not public.

Partner-facing contracts.

  • Delivery. Status is pushed via signed webhooks. If a delivery is missed, poll the same labels.
  • Idempotency. Retrying with the same key and terms returns the original settlement. Reusing a key with changed terms results in a rejected request.
  • Documentation. OpenAPI specs for settlement and status routes live at Developers and API Documentation. They are not claimed as complete. Other routes appear as they ship. Retry and verify-webhook behavior are in the docs. Queue internals and signing algorithms are not public.

Operational expectations.

Production clearing is built to run without ticket queues for ordinary operations. Simulation and sandbox environments may be rate-limited, reset, or changed without a Service Level Agreement (SLA).

Data and subprocessors.

Gutschow is software clearing infrastructure, not a bank.

  • Business KYB. Processed by an external verification provider.
  • Settlement assets. Handled via licensed partner infrastructure.
  • Hosting & Billing. Managed through dedicated subprocessors.

Subprocessor disclosures are listed in our Privacy Policy. A current named list is available on request.

Data exposure classification.

Class Typical contents Where it lives
Account & Contact Name, work email, company Gutschow (keys, billing contact)
KYB Entity, beneficial owners, verification documents Verification provider and Gutschow (as needed for live keys)
Settlement References, destination identifiers, amounts, compliance metadata Gutschow clearing and rail partners
Billing Payment method tokens, invoices Payment processor (isolated from clearing records)

Blind Ingress Privacy limits what we store at ingress. It is not zero-knowledge cryptography, and it is not an absolute guarantee against provider incidents. See our Privacy Policy and Terms of Service.

Questions? Answers.

  • Confirmed is the partner rail’s receipt. Settled is Gutschow’s clearing book. A rail receipt is not a deposit Gutschow holds. Read the full map at Platform.

  • Business KYB applies to the API customer before a live key is issued. Payees are counterparties on the settlement, not separate Gutschow customers. Every payout is screened at ingress.

  • No. Sandbox exercises screening where it applies. It does not perform business KYB or issue live keys. Practice in the Sandbox; request live access at Production.

  • No. In production, a failed check or screening timeout blocks release. There is no send-anyway path.

  • No. It is not zero-knowledge cryptography. The mechanism is referenced under Data and subprocessors.

  • No. Hash-based Message Authentication Code (HMAC) signs requests you send to Gutschow. Outbound webhooks use Gutschow’s public key. See the walkthrough in API documentation.

  • No. Same-cycle describes the clearing state. It is not a domestic Automated Clearing House (ACH) or wire product, and it is not a guarantee that fiat lands globally on the same day.

  • Neither. It is a machine-readable index of US regulatory frameworks. Written controls are at Compliance.

  • Gutschow operates from the United States. Information may be processed in the U.S. and other countries where subprocessors operate. See our Privacy Policy.

  • It depends on the system. KYB packets reside in verification flows; settlement metadata resides on the clearing ledger; billing tokens reside with the payment processor.

Same rails.
Two doors.

Sandbox

$0 to test.

Simulated clearing.
Work email required.

Production

From $900/month.

Live clearing.
License and toll apply.