Financial event ledger.
Append-only record of reserve, settle, and release events. Gross amount, platform fee at ingress, and net payout are recorded for reconciliation.
Compliance
Know-your-business (KYB) before a live key.
Sanctions on every payout before release.
Gutschow LLC provides B2B clearing software for settlement on USDC and EURC. Gutschow is not a bank, broker-dealer, money transmitter, or custodian. Gutschow does not take deposits and does not provide legal, tax, or investment advice. This is not a domestic USD ACH or wire product.
Settlement assets move on licensed partner infrastructure, under partner terms.
Nothing on this website is an offer of securities or a solicitation where such activity is prohibited. Additional terms governing your use of this site are set out in our Terms of Service, Privacy Policy, and Disclaimer.
Gutschow serves software companies that embed B2B (business-to-business) payouts, disbursements, and invoice settlement on USDC and EURC — same-country counterparties and cross-border flows. The product is not a consumer wallet, retail trading venue, or domestic USD ACH or wire service.
Production access requires automated business KYB (know-your-business) of the API customer through a vendor. When the vendor decision clears, live API credentials are issued automatically. A pending, flagged, or rejected decision does not issue a live key.
Every settlement is evaluated at ingress — before funds move. Controls include:
| Control | Description |
|---|---|
| KYB | Business identity verification of the API customer — the legal entity and beneficial owners — before a live key. Payees are not separately KYB’d as Gutschow customers. |
| Sanctions screening | Screening of the settlement, including destination, before release. A vendor timeout stops the settlement. |
| Travel Rule | Originator and beneficiary data when the amount requires it. You are responsible for accuracy. |
| Velocity limits | Transaction size and rolling volume limits before dispatch. |
Controls run as part of the clearing pipeline, not as a separate step after settlement. See Platform for how they fit the state machine. US framework index: compliance.json.
Append-only record of reserve, settle, and release events. Gross amount, platform fee at ingress, and net payout are recorded for reconciliation.
Every settlement status change is logged with an idempotency key. The full pipeline history supports dispute review and internal audit.
Human-initiated approve, reject, or escalate actions are attributed to a named operator with a timestamp and reason.
Financial and audit records are retained per regulatory and contractual requirements. See Privacy Policy.
Verified work email. A gsk_sandbox_… key exercises the pipeline without production clearance. Start at Sandbox.
Business KYB of your company at Production Access. A cleared vendor decision issues gsk_live_…. A flagged or rejected decision does not.
Sandbox runs the same screening logic as production where applicable. It does not substitute for business KYB or issue live keys.
When the amount requires it, originator and beneficiary data must be supplied at ingress before settlement proceeds. That is a metadata gate — not a second KYB of every payee. Sanctions screening still applies below threshold amounts.
Start with the machine-readable compliance.json manifest (US frameworks). For supplemental diligence, use Contact.
The API customer, including beneficial owners, before a live key. Payees are not separately KYB’d as Gutschow customers.
No live API key is issued until a cleared vendor decision. Status and any operator action are recorded in the audit trails.
No. Gutschow provides clearing software, not banking services. Settlement assets move on licensed partner infrastructure. This is not a domestic USD ACH or wire product.
No. Sandbox credentials test the pipeline; they are not production clearance. Live keys require business KYB at Production Access.
Live API key only after a cleared decision.