Folio 00 · Surenbay

Deposit stablecoins. Spend at real AI vendors.

Your treasury is USDC. OpenAI, Anthropic, and your cloud vendors settle in fiat. Surenbay holds the deposit with a custody partner, posts it to a double-entry ledger, and spends it through official card and bill-pay rails.

Open an account Read the mechanism

One deposit, two legs

Dr system:clearing_usdcCr org:availablePosted only after required confirmations

The gap

Paying AI vendors is where finance discipline breaks down.

Crypto-native teams hold USDC. Their vendors do not accept it. What fills that gap today is improvisation, and improvisation does not reconcile.

Someone's personal card is the account of record

An engineer's Amex is on file at OpenAI. Finance cannot see it, cannot cap it, and finds out when the statement lands.

Unbudgeted · invisible until month end

Wire-and-hope top-ups

OTC desks and manual transfers with no idempotency key and no reconciliation trail. Every top-up becomes a spreadsheet argument later.

No idempotency · no audit trail

One shutoff switch

An expired card or a frozen grey-market proxy takes production down. There is no reserve, no fallback, and nothing to reconcile against.

Single point of failure

Posted instead

And what replaces it.

One account of record

The organization holds the balance, not an individual. Roles, caps, and freeze live with finance.

Idempotent top-ups

Each deposit credits exactly once, keyed on the deposit, with the fee disclosed before you send.

Reserve before spend

Credit is held before an authorization is approved. Fail closed — an underwater balance is a defect, not a rounding issue.

Mechanism

Four postings between your treasury and a vendor invoice.

Balances are computed from the journal, never edited in place. Credit is posted after confirmations, and spend reserves before it settles — a card authorization that cannot be reserved is declined rather than reconciled later.

Deposit
Send USDC on Base to your organization's own partner-custodied deposit address. No shared address, no memo field to get wrong.
Deposit state machine · no ledger entry yet
Credit
Once the required confirmations clear, the top-up posts as spendable credit — to the cent, net of the fee disclosed before you sent it.
credit_topup → org:available ↑ · system:fees ↑
Reserve
A card authorization or bill-pay request moves credit into a hold before anything is approved. Nothing settles against a balance that is not there.
reserve → org:available → org:held
Settle & release
Actual cost is consumed from the hold and the remainder is released. Every leg lands in an exportable trail your finance team can close the books on.
settle_usage · release_hold → org:held → org:available

Product

Built like a ledger, not a wallet.

The register of what Production v1 actually does. Anything not on this list is not shipped, and is not implied.
Ref	Capability	What it means
LDG-01	Double-entry ledger	Every deposit, reserve, settlement, and release posts as a journal entry. Balances are computed from the journal and never edited in place.
RAIL-02	Official rails only	Virtual card and bill-pay funded by your credit — never an unofficial key resale sitting behind a proxy.
ORG-03	Roles and budgets	Owner, admin, developer, and finance roles, with monthly caps and per-instrument budgets that hard-block overspend.
AUD-04	Exportable audit trail	Every reservation, settlement, and administrative action is logged and exportable — built for a finance close, not a demo.
CUS-05	Partner custody on Base	USDC deposits are held with a custody partner rather than a solo-signer hot wallet, at a unique deposit address per organization.
VND-06	Vendor playbooks	Documented steps for attaching Surenbay to OpenAI and Anthropic billing, with a staging checklist before you cut over.

Security & compliance

Money movement stays on regulated rails.

Surenbay is a technology platform. Custody, card issuing, and identity verification are performed by partners built for those functions. Surenbay does not self-custody deposits and does not run an unofficial vendor proxy as its core product.

Deposits are held with a custody partner, not a solo-signer hot wallet.

Spend flows through official card and bill-pay networks, never a shared master key.

Organizations complete KYC/AML checks before balances go live.

No interest is paid on balances by default and there is no platform token. Fees are disclosed USD line items.

Folio 06 · Receipt

Three levers, all visible before you deposit.

Indicative starting bands. Final numbers are set per plan and shown before every deposit and on every invoice — the business does not run on an undisclosed spread.

Who this is for: Organizations already spending roughly $2,000 a month or more on LLM and cloud infrastructure.
Why a minimum: KYC and custody carry real per-organization cost. The floor keeps deposits meaningful rather than optimizing for dust.

Open an account

Surenbay

Statement of charges · Team

Platform subscription$99–$499 /moTeam and Enterprise. Covers KYC, custody, and support.

Take rate on top-up1.5–4%Disclosed at deposit time, scales down with volume.

Minimum top-up$500Per deposit, not per month.

Markup on vendor charges$0Vendor invoices pass through at cost. No hidden spread.

Total disclosedBefore you deposit

Indicative · not a quote

Folio 07 · Closing entry

Give your AI spend a ledger to answer to.

Deposit once. Reserve, settle, and reconcile every dollar that leaves for OpenAI, Anthropic, and whatever you adopt next.

Open an account Re-read the mechanism