Welcome to Strimz
B2B subscription billing on stablecoins. Settled in USDC on Arc.
Strimz is a billing layer for businesses that accept stablecoin payments. One API covers one-time charges, recurring subscriptions, refunds, agent escrow, and cross-chain settlement. Everything settles in USDC on Arc, where USDC is also the gas token, so customers never have to top up a wallet to send a payment.
Method names follow the verb-noun shape you'd expect:
paymentSessions.create, subscriptions.cancel, refunds.create.
Webhooks carry a t=…,v1=… header signed with HMAC-SHA256. The full
endpoint list lives at /docs/api/overview.
The piece worth knowing about up front is the on-chain behaviour. The contract enforces idempotency itself, which means a retried charge cannot become a double charge. Settlement is final the moment your webhook fires. There is no three-day wait, no chargeback window, no bank that decides a week later to reverse the transaction.
Live on Arc
All examples in these docs assume Arc, Circle's stablecoin-native L1 where USDC is the gas token.
Test mode runs on Arc Testnet (chain ID 5042002). See Modes for environment
details.
Get started in 5 minutes
Quickstart
Sign up, get an API key, send your first test payment, and wire a webhook. Start to finish.
Authentication
Privy for the dashboard, API keys for the SDK, with scopes you control.
Test vs Live mode
Two completely separate environments with different chains, DBs, keys, and webhook endpoints.
Modes of failure
What can go wrong, what you'll see when it does, and what Strimz handles for you automatically.
Build by use case
Accept a one-shot payment
Hosted checkout for a single charge. Five minutes from `createSession` to fulfilled order.
Build a subscription
Recurring revenue with one customer signature. Atomic batch charging, configurable grace, on-chain idempotency.
Process a refund
Server-side intent + wallet-signed transfer. Indexer reconciles on-chain status automatically.
Verify a webhook
HMAC-SHA256 with replay protection. Six lines of code on your end.
Cross-chain (roadmap)
CCTP V2 routing from Ethereum, Base, Polygon, Solana into Arc. Schema and scheduler are in place; checkout UI ships in a later release.
The AutoPay Agent
Recovery emails, cashflow digests, anomaly detection, vendor escrow. Included in every plan.
Reference
API reference
Every endpoint, every parameter. OpenAPI 3.1 schema available at `/openapi.json`.
Server SDK
`@strimz/sdk` for Node 18+ and Bun. Type-safe, idempotent retries, Zod-validated payloads.
React SDK
`@strimz/sdk-react` for embedded checkout. `<StrimzPayButton/>`, hooks, browser-safe.
Errors
Every error code Strimz returns, what causes it, and what to do about it.
Concepts
The six processes that make up Strimz, how data flows, what's idempotent vs eventually consistent.
Self-hosting
The full stack is open source. Audit it, fork it, run it on your own infrastructure.
What's in the box
A short tour of what you get out of the box.
Hosted checkout
Branded one-shot and subscription checkout pages. No client UI to maintain.
Wallet auth
Email, social, or wallet via Privy. Embedded Arc wallets, automatic 2FA gates.
Webhook delivery
Signed, retried with exponential backoff, replay-protected, auto-disabled after persistent failure.
Refund pipeline
Wallet-signing instructions returned in the create response. Indexer closes the loop.
Cross-chain
CCTP V2 attestation plus scheduler-side message replay on Arc. Your customer pays from any USDC chain.
Analytics
MRR, churn, conversion, LTV, 90-day forecast. SQL-backed against your own Postgres.
AutoPay Agent
Recovery emails, cashflow digest, anomaly detection, vendor escrow with allowlists.
Dashboard + storefront
Hosted merchant dashboard and a no-code storefront builder so you can sell without an e-commerce stack.
OpenAPI 3.1
Machine-readable schema. Generate clients in any language: Postman, Insomnia, or your own codegen.
A note on tone
These docs assume you know what an HTTP request looks like, so they skip the lecture on JSON. They try to get to the curl command quickly. If a section is too long or too short, that's worth fixing.
If something is wrong, unclear, or out of date, open an issue. Docs PRs go through the same review as code PRs.
Need help fast?
Open a thread in #strimz-dev (link in your dashboard) on the Growth and Enterprise plans. Otherwise email support@strimz.finance; replies land inside 24 hours on every plan. For security disclosures use security@strimz.finance (PGP key on the security page).