House notice · For operators
For the businesses a panel underwriter would call a Tuesday-afternoon problem.
If you have been routed to a high-risk processor, declined for vague reasons, or held on a queue for three weeks waiting on underwriting, the house was built for you. We are taking on a small number of operators this quarter.
Plate I.
Onboarding, in four motions.
- I.
Send a letter
A short note, written by a person, about what you sell, where you sell it, and which processor (if any) you use today. We do not send a fourteen-field discovery form.
Reply within two working days, signed. - II.
We read your file
An underwriter — a person, with a name and an extension — reads the file. We pull the bureau and sanctions data, look at your storefront, and write back with a structured offer or a polite decline.
Average underwriting time: 38 minutes. - III.
We open a book
You receive a signed agreement, an account number that reads like a ledger folio, and credentials for the dashboard. The dashboard reads like a register, not a feed.
First charge: typically the same day. - IV.
We post your day
Each evening we post the day's register and settle the next morning, never later. Refunds, holds, and disputes appear on the page in plain English with their own folio numbers.
Settlement window: T+1, written into the contract.
Plate II.
What the house does for an operator on the books.
- § 01
Underwriting that reads, not parses.
Risk is read by a person against the actual behaviour of specialty trades — not against a generic SaaS baseline that does not know what a wine room looks like in October.
- § 02
One operational page, not a feed.
Onboarding, risk, and settlement consolidated into a single, readable register. No tab archaeology to find what posted today.
- § 03
Reconciled reporting in one schema.
Settlement statements that close cleanly to your books regardless of how the day routed under the hood.
- § 04
Settlement on the next business day.
Standard T+1 funding with a written reserve and held-funds policy. Where we are late, we say so on the page and pay a defined penalty.
- § 05
A person on the line.
Direct correspondence with the operations and risk staff for chargebacks, disputes, and escalations. The same names answer the email and the phone.
- § 06
An honest API.
REST endpoints, idiomatic SDKs, signed webhooks, and an OpenAPI 3.1 specification you can generate tooling from. No surprises in the request body.
Closing
Write to the house.
Tell us what you sell, where you sell it, and what your current processor is costing you. We will read the note ourselves and reply within two working days.