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>
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>
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>
Brings in packages/routing, packages/hyperliquid (hypercore network), checkout
AnyTokenPay/HyperCorePay, Node 22 pins, tenant-ownership guards and the zcash
tag lock. Only conflict: drizzle _journal.json (kept 0010_onchain_billing and
0011_coupons_organization in order).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
/v1/onchain-billing: networks, subscription intents (what the buyer
signs or sends per network), grant submission with immediate first
charge and entitlement grant, cancel with revoke actions, Base escrow
authorize/capture/void/reclaim, and owner refunds recorded in
@settlekit/refunds and dispatched per network.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- HYPERCORE_* config; the registry registers a hypercore SettlementVerifier
(payee ledger via @settlekit/hyperliquid) only when enabled
- checkout sessions accept requireMemo (Tempo only); confirmations then need
transferWithMemo(keccak256(session id))
- a route provider's stored destination fill skips only the payer and memo
bindings; hypercore joins the observable networks
- drop the unused @settlekit/routing dependency from the API
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
New @settlekit/hyperliquid on @nktkas/hyperliquid (MIT): EIP-712 usdSend
typed data pinned by golden vectors against the SDK signer, submission of
buyer-signed actions, and fail-closed verification through the payee's
userNonFundingLedgerUpdates (destination == payTo, USDC >= expected, time >=
session creation, payer binding). HYPERCORE_ENABLED / NETWORK / API_URL env.
Registers the workspace packages in the lockfile (filtered install; unrelated
peer rewrites reverted).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@x402/core, evm, svm, hono, fetch 2.27 (Apache-2.0) and mppx 0.11 (MIT)
for x402 v2 on every chain and MPP on Tempo. Scaffolds the
@settlekit/x402-facilitator package manifest. Lockfile peer churn in
unrelated importers (checkout, app-kit-viem) reverted.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The cherry-picked fail-closed payment fixes imported @settlekit/solana, which
does not exist on this branch, breaking tsc -b and the api/worker suites.
Solana verification, env and session references are removed; arc/base/
ethereum keep the per-network verifier registry and the worker keeps
payTo-bound verification. A solana network is now rejected as unsupported
(400 on checkout/observe, unsupported in the worker). Also adds the missing
packages/circle project reference to the api, points the api/worker test
scripts at the root vitest config, and removes the operator's
vitest.apps.config.ts workaround.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@settlekit/chains carries the verified EVM registry (Ethereum, Base,
Arbitrum, Robinhood Chain, HyperEVM, Tempo, Arc; mainnet + testnet), a
generic stablecoin verifier over the arc EvmRpc seam (chain-id assertion,
receipt status, token/payTo/amount, confirmations, block time vs session,
payer binding, Tempo TIP-20 memo), CAIP-2 ids, network-aware tx-hash and
payTo rules, env loaders (SETTLEKIT_CHAIN_ENV, ENABLED_EVM_CHAINS, per-chain
overrides, Zcash) and the settlement-verifier contract. Tests replay
receipts recorded from each chain's public RPC.
PaymentNetwork widens to solana|base|arc|ethereum|arbitrum|robinhood|
hyperevm|tempo|zcash and CheckoutSession gains settlementQuote,
payerAddress, acceptedNetworks and payToByNetwork. The hosted checkout
fails closed on the new networks until its wave-2 UI lands.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
OperatorAgent drives the Anthropic SDK tool runner (betaZodTool) over read
tools (treasury state, open bills, counterparty risk, payment history, x402
quotes) and policy-checked action tools that require rationale,
alternatives and confidence. claude-sonnet-5 handles revenue and ticks,
claude-opus-5-5 bills, refunds and disputes; at most 12 iterations, with
HeuristicOperator fallback when no key is set or the API fails.
OperatorService turns each event into one hash-chained DecisionRecord with
the tool trace, verdict, usage cost and outcome. The vault anchors a
pre-execution commitment hash of the reasoning; owner approvals, rejections
and 72h expiries are recorded as decisions too. Invoice and customer text
is passed as escaped untrusted data.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds @settlekit/attribution — reuse-detection, weighted provenance lineage,
and HMAC-signed proofs-of-citation — wired live into the rsshub-citation-toll
sidecar (POST /attribution/{detect,proof,verify}) and persisted via
PgLineageStore/PgProofStore over new lepton_lineage_edges + lepton_citation_proofs
tables.
Adds apps/creator-dashboard — a Next.js earnings view in the Statement
greenbar-ledger design system, driven by real domain logic (createSource +
computeRoyaltyDistribution + detectReuse, not mocks). Statement / Sources /
Payouts / Reuse & proofs (interactive) / Wallet. next build green.
Also bundles in-progress settlement hardening: settlement-core idempotency
concurrency, api env validation, bundles + contracts/worker tweaks.
Verified: 943 vitest tests, 27 Foundry tests, next build all green.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add @settlekit/oss-fund: read package.json / requirements.txt (+ optional
lockfile), map the (transitive) dependency graph to maintainer wallets, and
split a small monthly budget across them — settled over the existing
nanopayment spine (payee-registry, x402 Settler, RecursiveSplitDistributor).
The allocation is the core: an engine weighs four signals per package —
directness, reach (criticality), usage, and maintainer underfunding — and the
capability layer converts a proposed weighting into a conserved integer
allocation (legs sum to the budget exactly, only resolvable wallets paid,
unregistered maintainers earmarked to escrow). Two engines, mirroring the paying
agent: a deterministic heuristic (default/CI) and a Claude (claude-opus-4-8)
tool-use brain that proposes weights under the same enforced policy.
- packages/oss-fund: manifest/lockfile parsing, graph + reach, signals,
resolver, conserved allocation, heuristic + Claude engines, settlement +
on-chain distributor calldata, realistic seed, CLI, tests (12 passing).
- apps/api: public PUBLIC routes GET /v1/fund/demo and POST /v1/fund/plan.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>