The product

Not a widget.
A full revenue stack.

Links, subscriptions, credits, receipts, recovery and a published API — one workspace, one settlement model. Everything below ends the same way: at the address you verified.

Start in test mode Read the docs

01Start

From idea to first sale in one form.

A product, a price, a link. The price is the payable link itself — there is no separate checkout to configure and no embed to paste. Share it in a bio, a DM, an invoice or an email.

Step 01

Name the product

One field. It carries your business name and logo through to the checkout the buyer sees.

API Pro

Step 02

Set a price

Fixed amount, subscription with an explicit period, or a pack of credits. Test and Live are separate from this point on.

$49.00 / 30 days

Step 03

The price is already the link

Nothing else to create. Open it and a buyer can pay from an exchange or a wallet within a minute.

bw.to/pl_8Xk2

02Recurring revenue

Subscriptions with explicit renewals. Credits with a real ledger.

Nothing is charged behind the buyer’s back — a renewal is a payment they make, announced in advance. A credit pack is a balance you can read, grant and consume through the API, with a movement behind every number.

SUBSCRIPTIONACTIVE

A period that starts and ends on a date you can name. Reminder three days ahead, renewal link, and a signed expiration event your integration can act on.

CREDITS6,582 LEFT

Every grant and every spend is a ledger line, so the balance is never a number somebody has to trust. Read it, grant it and consume it from your own code.

03Recovery

Every mismatch has an explicit state.

Money that arrives short, late or plain wrong is the normal case on an exchange path, not the exception. Each of those is a named state with a screen behind it — never a payment that quietly disappears, and never a guess made on your behalf.

What happened	Asked	Arrived	After	Result
The exchange took its fee out of the transfer	49.000000	48.800000	2m	Credited
The buyer sent less than the invoice	49.000000	31.500000	11m	Top-up shown
The withdrawal cleared long after the page closed	49.000000	49.000000	6h 41m	Your review
A buyer paid twice for the same invoice	49.000000	98.000000	3m	Your review

A shortfall the size of an exchange fee is forgiven and the invoice closes; a larger one stays open with the exact remainder. Tx-hash recovery is the fallback: the transaction is matched against the open invoice. A refund is only ever sent to an address the buyer confirms, so money never goes to a guess.

04Integration

Integrate with the published contract.

The OpenAPI document is checked against the same registry the server routes with, so what is written is what is served. Money-changing operations take an idempotency key; every webhook is signed and retried.

bashPOST /v1/checkout/sessions

$ curl "$BUILTWIDE_API/v1/checkout/sessions" \
    -H "Authorization: Bearer $KEY" \
    -H "Idempotency-Key: checkout-0143" \
    -d '{"priceId":"price_0143","payerEmail":"buyer@example.com"}'

{ "session_id": "4f70a63a-ba63-4795-9d70-161fb9953708",
  "invoice_id": "inv_e3b0c60736e92212",
  "url": "https://pay.example/i/inv_e3b0c60736e92212" }

Idempotency-KeyRequired on money-changing operations. Reusing a key with different parameters is an error, not a silent replay.

amount_microMoney crosses the wire as an integer of micro-USDC. Never parse the display amount as a float.

Signed webhooksPer-endpoint secret, seven attempts, and every attempt recorded so a miss is visible.

openapi.jsonChecked against the running registry, with a response schema per operation.

05Dashboard

A control room, not a spreadsheet.

Every screen shows the state the domain actually has and the next action it needs. Test and Live switch with one toggle and never mix — not for reads, not for mutations.

Overview: Revenue, the launch checklist and exactly one next action. Nothing else competes for attention.
Payments: Every invoice with its path, its state and the transaction that settled it.
Subscriptions: Periods, renewals and expirations, with the reminder that went out against each.
Credits: Balances with the ledger behind them: granted, consumed, reversed.
Needs attention: Short, late and unmatched transfers waiting for a decision that is yours to make.
Developers: Keys, webhook endpoints and the delivery log for every attempt.
Settings: Business details, the receiving address you verified, and the refund policy buyers see.

The whole stack. One direct settlement model

Links, subscriptions, credits and recovery all end at an address that belongs to one invoice and can only forward to the wallet you verified. There is no second mode where we hold the money instead.

Start in test mode See what it costs

No card · No call · No contract to cancel

Not a widget.A full revenue stack.