GET /v1/analytics/metrics computes, from live sessions, payments,
subscriptions and catalog: checkout conversion, per-payment-link opened /
paid / conversion / revenue, repeat customers, average revenue per
customer, subscription churn, ARPU and an estimated lifetime value, with
exact bigint money. Checkout repositories gain listCreatedSince
(in-memory and Postgres). The dashboard Analytics page shows the new
cards and a payment-link table.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merchants can publish a store (slug, title, tagline, https logo, accent
colour, search description, optional custom domain) through settings or
the dashboard. The checkout app serves it at /store/<slug> with SEO and
Open Graph metadata, listing active products (invoice products hidden)
that each open their payment link, and a middleware rewrites '/' on a
merchant's custom domain to its store when CHECKOUT_PRIMARY_HOSTS is set.
Slugs and domains are unique; public data at /v1/public/stores. Carts of
several products stay out of scope because hosted checkout fulfils one
product per session.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GET /v1/merchant/offramp builds sell links for Transak, MoonPay (signed
server-side with the secret key) and Ramp with the amount, network and
the merchant's own receiving wallet prefilled. SettleKit takes no
custody; partners appear only once the owner configures their keys
(TRANSAK_API_KEY, MOONPAY_PUBLISHABLE_KEY/MOONPAY_SECRET_KEY,
RAMP_HOST_API_KEY). The dashboard Balances page gets a Cash out action per
mainnet network.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Refunds no longer depend on a pasted hash alone. POST
/v1/merchant/payments/:id/refund/prepare creates a pending refund and
returns the exact transfer back to the buyer: ERC-20 transfer calldata,
token, chain id and an EIP-681 link on EVM networks, or a Solana Pay
transfer request with a unique reference. The destination is the wallet
that paid when known, else the merchant enters it (validated per chain).
POST /v1/merchant/refunds/:id/confirm verifies the signed transfer
onchain with the payment verifiers (destination, amount, time, Solana
reference, one refund per tx) and only then settles: access revoked,
payment refunded once fully refunded, refund.succeeded with source
wallet. Pending refunds can be canceled. Dashboard refund form gets a
'Send from my wallet' mode (browser wallet or mobile link, auto-verify).
apps/refund-protocol stays unwired.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Security fix plus team access. Before this change any valid API key,
including access keys the delivery system hands to BUYERS, authenticated
as the merchant on the whole management API, and GET /v1/api-keys listed
every organization's keys. Now only platform keys (issued at sign-up or
via POST /v1/api-keys/platform, marked with the platform product id) can
call the API, and each request needs its resource scope
(<resource>:read|write, write implies read; platform:admin or * for
full access), answered with 403 and details.requiredScope otherwise.
Keys cannot mint broader keys, customer keys cannot carry management
scopes, key listing is tenant-scoped and keys can be revoked by id.
Dashboard sessions get team roles (owner, admin, developer, support,
viewer) mapped to scopes. /v1/team manages members and email
invitations (packages/invitations, token hash only, 7-day expiry);
/v1/auth/invitations/accept joins the org and creates the account. The
last owner is protected and only owners grant owner. Dashboard: Team
page, invite accept page, and an API keys page that creates restricted
keys and shows the secret once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every seller webhook delivery now keeps an attempt log (status code,
error, time, next retry) in the worker queue (Postgres) or in memory.
New routes: GET /v1/webhooks/deliveries(/:id), POST
/v1/webhooks/events/:id/resend, POST /v1/webhooks/endpoints/:id/test
(signed webhook.test event), rotate-secret with a 0-168h grace window
(both secrets sign as two v1 values, verified by @settlekit/webhooks, the
TS/Python/Go/Rust SDKs and the WooCommerce plugin), and disable/enable.
The worker retries on a 1m..6h exponential schedule instead of every tick,
signs with the live endpoint secret, skips disabled endpoints and
auto-disables one after 100 failed attempts in a row
(WEBHOOK_DISABLE_AFTER_FAILURES). Outbound requests get a 10s timeout.
The dashboard Webhooks page shows the event log with Resend and endpoint
actions.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Prices can now be set in EUR, GBP and other ECB reference currencies
(displayCurrency + displayAmount, or currency on quick products). Each
checkout converts them to USDC at the live rate from a frankfurter
service (MIT, FX_RATES_URL), rounded half-up to the cent with exact
bigint math, and locks the quote on the session (fxQuote) until it
expires, so onchain verification expects exactly the quoted USDC. Promo,
tax, receipts and the hosted checkout lines use the locked rate; the
payment link page shows the fiat price and today's USDC amount. Missing
or implausible rates fail closed (503); fiat subscriptions and mixed
fiat currencies are refused. Dashboard product form gets a currency
picker.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
apps/checkout/public/embed.js opens a payment link, checkout or invoice
from the same checkout origin in an overlay iframe on any site; links
marked data-settlekit-checkout bind automatically, SettleKit.open() is
available from code, and there is an open-in-new-tab fallback for
wallets that block iframes. The success page posts settlekit:success
only to a site the seller listed under Settings > Embedding
(org embedOrigins, validated https origins), and embed.js only accepts
messages from its checkout frame. Payment requests gain sendEmail and
successUrl so store plugins can redirect buyers and bring them back.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
New tenant-scoped /v1/exports routes: payments, refunds, invoices and
payouts CSVs, a full USDC ledger, and bank statement files that Xero
(DD/MM/YYYY statement import) and QuickBooks Online (three-column bank
upload) import directly, with optional date ranges. packages/exports
gains a formula-injection guard (opt-in, admin unchanged) and the
accounting formatters. The dashboard Payments page links every export
through a session-authenticated download route.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sellers can turn on checkout tax in settings (label, own country and tax
ID, legal name, per-country rates, default rate, EU reverse charge).
Sessions add tax on top of the net price after any promo, so onchain
verification expects the tax-inclusive total. Buyers set billing country
and VAT ID via the API (billingCountry, vatId) or on the hosted checkout
until a payment is recorded; EU cross-border B2B with a VAT ID of the
right shape is zero-rated. Settled checkouts get a PDF receipt (pdfkit)
with the seller's tax ID, buyer country / VAT ID, tax rate and the
settlement transaction, linked from the success page, the receipt email
and the customer portal. packages/tax calculateTax is now used at
checkout.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Coupons now reach checkout. POST /v1/checkout-sessions takes an optional
couponCode, payment links accept ?promo=CODE (a refused code falls back to
full price with a notice), and the hosted checkout gets a promo field
while the session is open and unpaid. The discounted total becomes the
session amount before network bindings, so onchain verification expects
the discounted amount and a locked Zcash quote is re-priced. Codes are
tenant-scoped, product-scoped codes discount only their products, and
free-trial or 100% codes are refused. The redemption is counted once
after the payment confirms (API confirm and hosted checkout).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SettleKit's advertised per-payment fee was never collected because buyers
pay merchants' wallets directly. When PLATFORM_BILLING_ORG_ID is set, the
API now issues each merchant a monthly statement (confirmed payments x the
fee schedule) as an invoice from SettleKit's own org, paid through the
hosted checkout on the G2 payable-invoice path. Totals below the minimum
carry forward, test accounts are skipped, runs are idempotent and happen
automatically every six hours (or via POST /v1/billing/statements/run).
A statement unpaid past due + grace restricts new products to the free
plan limit from packages/pricing (402 with the pay link). Merchants see
accrued fees, statements and a Pay button on the Balances page.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Invoices can now be paid onchain. POST /v1/invoices/:id/send issues the
invoice, binds a public pay page (/i/<token> on the hosted checkout),
opens a checkout session for the invoice total on the merchant's
networks and emails the link. POST /v1/invoices/requests sends an
ad-hoc amount + memo to an email. The invoice turns paid only when a
confirmed onchain payment exists for one of its sessions (on read in the
API and in the new worker invoice-settle job) and emits invoice.paid.
Invoice and receipt PDFs render with pdfkit (MIT). Voiding cancels open
sessions. Dashboard gets a request-a-payment form, send buttons, pay
links and PDF downloads.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The page posted to a route the API does not have and read fields it does not
return. It now creates /v1/webhooks/endpoints with the chosen events
(default: payment.confirmed, subscription.charged, subscription.canceled,
refund.succeeded) and reveals each endpoint's signing secret for verification.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Subscriptions: every buyer subscription with plan, network and collection
method, status, next charge, last charge (explorer link), dunning state and
cancel at period end / now; active count, MRR and dunning totals. Falls back
to the core list when onchain billing is off.
- Payment detail: Refund payment sends the funds on-chain through
POST /v1/onchain-billing/refunds (operator wallet per network, Base escrow
via the escrow) and shows the refund transaction link; when the operator is
not configured for the network it offers "I refunded manually" to record
the tx hash. Refund rows link to the explorer.
- Refunds ledger links each refund to its payment instead of creating
unsent pending refunds.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- checkout: buyers connect Discord (OAuth2 identify + guilds.join) in the
delivery-fields step; the callback saves their user id on the session and
joins them to the product's server. After payment the bot adds the role via
PUT /guilds/{guild}/members/{user}/roles/{role}; the grant is recorded for
access-sync revocation. Without DISCORD_BOT_TOKEN the buyer sees
"pending setup" instead of a fake success.
- worker: discord-delivery-retry grants pending Discord entitlements once the
bot is configured (backoff per entitlement); DISCORD_BOT_TOKEN is optional.
- api: a configured bot delivers roles even before GitHub is set up;
checkout subscriptions pass the buyer's Discord / GitHub ids so subscription
delivery reaches the right accounts.
- dashboard: product settings explain server / role ids and link the bot invite.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- /onboarding: business name, accepted networks and receiving addresses
(one EVM address for every EVM chain, Solana, HyperCore, Zcash t-address)
validated per chain, first product, shareable link + embed button
- Payments list (network, asset, route, buyer, explorer link, filters) and
detail with created/paid/verified/delivered timeline and refund recording
- Products create/edit with USD price, delivery type, per-network toggles,
pause/re-open; customers with spend and access; live on-chain balances
- Settings: networks and addresses, webhooks, API keys; short sidebar
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- AuthService.unlinkWallet — clears the linked wallet, refusing to strand a
wallet-only account (no password) from its only sign-in method.
- DELETE /v1/auth/wallet (bearer); dashboard Unlink button + /api/wallet/link DELETE.
- InMemoryAuthStore.saveAccount removes the stale wallet index on unlink (Pg: column→NULL).
- docs/DEVELOPMENT_ROADMAP.md: phased feature plan driving the continuous loop.
- 1308 tests / 213 suites, typecheck + builds green.
CRITICAL-1: validate SIWE domain/chainId server-side (EIP-4361 cross-site replay guard); AuthService gains siweDomain/siweChainIds, wired from AUTH_SIWE_DOMAIN/AUTH_SIWE_CHAIN_IDS in apps/api context.
CRITICAL-2: UNIQUE index on auth_accounts.wallet_address (migration 0007) as the final gate against the link/login race; loginWithWallet + linkWallet catch the violation -> conflict. Verified on live Postgres (dup rejected, NULLs allowed).
CRITICAL-3: /api/session (dashboard + portal) now verify the token with the API before persisting the cookie (no session fixation); + same-origin check on cookie-setting + /api/wallet/link routes (MEDIUM-3 CSRF).
HIGH-1: require expirationTime; enforce notBefore + issuedAt skew (shared verifyWalletMessage); clients now set expirationTime.
HIGH-2 (rate-limiting, task a): /v1/auth no longer exempt — stricter AUTH_RATE_LIMIT_PER_MINUTE (default 20) in a separate bucket; opportunistic expired-nonce prune (store + Pg).
HIGH-3: reserve the wallet email domain — block email/magic-link registration on it (no synthetic-email squatting).
HIGH-4: gate X-Forwarded-For trust behind TRUST_PROXY.
LOW-1: require a 65-byte (130-hex) ECDSA signature at the API boundary.
+ web3 tests for domain mismatch, missing-expiration, reserved-email. 1308 tests / 213 suites, typecheck + full build green; migrations 0006/0007 verified on Postgres.
- Root cause: isomorphic ids.ts uses globalThis.crypto (a global only in Node 20+, per engines.node>=20). A Vercel project building on Node 18 has no global crypto, so any page generating an id at build time throws and the deploy fails.
- Add .node-version=20 to repo root + every app (Vercel reads it from each app's Root Directory) so deploys use Node 20.
- ids.ts: resolve Web Crypto lazily with an actionable error instead of a cryptic undefined access — still browser-safe (no node:crypto import).
- 1304 tests / 213 suites, typecheck + full build green.
Replace the dark blue→purple gradient SaaS look across all 7 apps with a
gradient-free settlement-ledger identity grounded in what SettleKit does:
reconcile money to the cent.
- Palette: greenbar ledger paper + ink, with accounting semantics
(credit-green / debit-red / ink-blue seal). No gradients or glows.
- Type: Archivo (display/body) + IBM Plex Mono carrying every number,
label and section reference; loaded via next/font in each app layout.
- Signature: apps/web hero is a live settlement statement — debit/credit
line items printing in sequentially with a rotated "SETTLED" stamp.
- apps/web fully rebuilt (globals, layout, components, pages); dashboard,
portal, marketplace, admin, checkout, docs rethemed by flipping :root
token values (component JSX untouched); shared packages/ui/theme.css
moved to the same system.
All 7 apps + @settlekit/ui build clean.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The checkout app pinned experimental.outputFileTracingRoot to its own dir, so
Next omitted the @settlekit/* workspace package files from the serverless
function — causing a runtime 500 ("Cannot find module") on Vercel while local
`next start` worked (full node_modules). Point tracing at the monorepo root.
docs: add the live Render + Vercel deployment URLs to the README.
Render's default Web Service runs `pnpm start` at the repo root, which had no
script — deploys failed with ERR_PNPM_NO_SCRIPT_OR_SERVER and "no open ports".
Add a root `start` that boots the API (@hono/node-server binds 0.0.0.0:$PORT),
so a plain root-level Render service now works (build = full workspace, start =
API). For API + worker + Postgres together, the render.yaml Blueprint still applies.
Add per-app vercel.json (web/dashboard/marketplace/checkout/docs) with the
pnpm-workspace install + filtered build and the correct package names
(marketplace-app / checkout-app / docs-app). Document the Render-API +
Vercel-frontends split in DEPLOYMENT.md.