Payables.
Embedded supplier payouts inside your product.
Clearing is the product. The payout ties out.
B2B settlement on USDC and EURC. Gross, fee, and net on one record to settled.
$100k in. $99.5k out.
One 0.5% fee at ingress. The request and the ledger carry the exact same numbers.
| Gross | 100,000.00 USDC |
|---|---|
| Fee | 500.00 USDC at ingress |
| Net | 99,500.00 USDC to the payee |
| Clearing state | settled |
platform_fee = max(round(gross × 0.005, 4), 1.0000), assessed at ingress. Default 0.50% (50 bps) of gross with a $1.00 minimum per release. See Pricing.
confirmed is the partner rail’s receipt. settled is the clearing book, where gross, fee, and net are final.
Five rules. Zero exceptions.
Reserve. Fee. Screen. Record. Executed before anything touches the rail.
- Reserve first. Funds are reserved before anything is released. Release happens on settlement or on an explicit rollback.
- Fee once, at ingress. The fee is computed once, at ingress. Net is the remainder, to four decimal places. The request and the ledger carry the same numbers.
- Screen before release. Screening runs before release. Sanctions, including the destination, and velocity limits are checked first. A vendor timeout stops the settlement.
- Record. State changes are appended, never rewritten. Every transition adds a record.
- Same-cycle. Same-cycle means the book closed. It does not mean a bank wire lands in every country that afternoon.
Ingest to settled.
Same pipeline in sandbox and production. Real-time clarity for finance and engineering.
- Ingest. You call api.gutschow.xyz with an Idempotency-Key. The settlement is staged.
- Reserve. Screening runs, and funds are reserved before anything moves out.
- Confirmed. The partner rail returns its receipt. It is not a deposit Gutschow holds.
- Settled. The clearing book closes with gross, fee, and net final.
Signed webhooks fire at each transition. If you miss one, poll GET /v1/settlement/status/{id}. Every state is defined on Platform.
Built for platforms.
Stop chasing status across three systems. One API for embedded supplier payouts, B2B disbursements, and invoice settlement. USDC and EURC.
Disbursement.
Programmatic B2B payouts your engineering team controls.
Invoices.
Settlement on invoice workflows you already run.
Cleared before release.
Business verification (KYB) verified. Automated sanctions on every settlement. Built-in Travel Rule data. Gutschow is clearing software, not a bank. Not a domestic USD ACH or wire product.
| Check | What runs |
|---|---|
| KYB | KYB of the API customer, the legal entity and its beneficial owners, before a live key is issued. |
| Sanctions | Sanctions screening on each settlement, including the destination, before release. |
| Velocity | Velocity limits before release. A vendor timeout in screening stops the settlement. |
| Travel Rule | Travel Rule originator and beneficiary data, when the amount requires it. Payees are not separately KYB'd. |
Read. Build. Launch.
Explore open docs. Test in sandbox. Go live after business KYB.
- Read. The API documentation and the open simulation. No account.
- Sandbox. Request a key on Sandbox. It lands after you verify a work email.
- Production. Start business KYB at Production Access. A cleared vendor decision issues a live key. A flagged or rejected decision does not.
Stage a settlement. Audit the numbers.
Get a sandbox key with a verified work email, then check the ledger.