Crypto SaaS and APIs
Monthly plans, billed to a wallet
Your customers already hold stablecoins. Charge them the way a SaaS business charges: a plan, a price, a renewal date, and a receipt they can file.
- Recurring
- From one bounded approval
- Settlement
- Your own address, per chain
- Failures
- Retried, then paused
Team plan
dana@acme.dev · monthly on Base
99.00 USDC
2 of 12 periods collected · 1,188.00 USDC approved
This period
99.00 USDC
Collected without a prompt
Your application heard
subscription.renewed
Signed · 142ms · 200 OK
The difference
What changes when the wallet is the payment method
Without it
Invoicing by hand
- A spreadsheet of who owes what this month
- Payment requests sent as an address and a figure
- Chasing in a group chat when nothing arrives
- Reconciling transfers against customers by eye
- No record a finance team would accept
With Reclack
Billing that runs itself
- A plan per customer, with a renewal date
- A hosted checkout that explains what is signed
- Collections against the approval they already gave
- Invoices, receipts and transaction hashes on every payment
- Signed events your application can act on
Lifecycle
From a price to a renewal
Four steps, none of which involve your team touching a wallet.
Team plan
price_team_monthly
Change what you sell without rewriting the integration.
What it means for the business
- Per customer
- One approval
- Every month
- No invoicing week
- On your systems
- No card data
- Sandbox to live
- Same code
They sign a bounded limit once, in the wallet they already hold stablecoins in.
Periods open, collect and reconcile without anybody on your side chasing them.
Nothing to store, nothing to rotate, and no card network to answer to.
Test chains and test keys first, then the same integration against live.
Questions
Before you move billing over
- Do our customers need to hold a particular token?
- They pay in USDC from their own wallet, on whichever network you accept. There is nothing to buy from us and no balance to top up with Reclack.
- What happens when somebody upgrades mid-period?
- Change the price on the subscription and the next period bills at the new amount. The approval the customer signed covers the plan, so an upgrade inside the cap needs nothing from them.
- Can we keep our own front end?
- Yes. The hosted checkout is there if you want it, and the API returns everything a page of your own needs if you do not.
- How do we reconcile at month end?
- Every period has an invoice, every payment carries its transaction hash, and every state change arrives as a signed event. Nothing is marked paid until the chain confirms it.
Put your plans on a wallet rail
Start in sandbox on test chains, then move the same code to live.