Crypto was never built for subscriptions.So we fixed it.
On-chain, no one can pull money from a wallet on a schedule — which is exactly why recurring crypto payments have been broken for years. QBitFlow makes them work properly: billing runs automatically, non-custodial the whole way, on a subscription your customers can never get trapped in.
The problem nobody solved
Card networks are built for recurring revenue. A customer enters their details once, and the merchant is allowed to pull a payment on a schedule — next month, the month after, indefinitely. The whole subscription economy runs on that one assumption.
Crypto is the opposite by design. Nobody can move funds out of your wallet without you signing for it, every single time. That's the entire point of self-custody — and it's a good thing. But it also means the card playbook simply doesn't work on-chain. There is no pull.
So for years, "crypto subscriptions" meant picking your compromise:
Custodial platforms
Solve it by taking custody of the funds — the exact thing crypto users came to avoid.
Manual re-payment links
The customer has to remember to click every month. They forget. Revenue churns for no reason but friction.
Roll-your-own billing
A cron job, a signing key, ledger reconciliation, retry logic, failure handling — that you now own and are liable for.
None of these are recurring billing. They're workarounds. Most builders tried one, got burned, and gave up on on-chain subscriptions entirely.
How QBitFlow solves it
QBitFlow makes recurring payments work on-chain without ever holding anyone's money and without taking control away from the customer.
When a customer subscribes, they sign one on-chain approval that grants a bounded, revocable allowance — a ceiling on how much QBitFlow is permitted to charge, and for how long. From then on, QBitFlow executes each billing cycle against that allowance automatically. No monthly signing. No custody. No manual links.
Nobody holds funds
Settlement is non-custodial from end to end. QBitFlow is the rails, not the bank.
The customer stays in control
The allowance is theirs. They set its size, and they can revoke it on-chain whenever they want.
Never more than approved
Not "shouldn't" — can't. The ceiling is enforced on-chain, not by our promise.
Read the side that's yours
Real recurring revenue. Integrate once, forget it.
What you get
True recurring revenue on-chain
Billing runs on a schedule against the customer's approved allowance, with no monthly action required from them.
Zero custody, zero fund liability
You never touch customer money, and neither do we. No signing keys to guard, no balances to reconcile, no billing loop to babysit.
Higher conversion
The approve-once model removes the single biggest reason people hesitate to subscribe. Customers who'd never risk a card-on-file will try you.
Real-time lifecycle events
Know the instant a subscription changes state, without polling.
How billing actually works
The customer approves an allowance once. QBitFlow charges against it each cycle. Because the allowance is a hard on-chain ceiling, you get a property card billing can't offer: customers can never be over-charged, and they can bound their own exposure. That's not a limitation you're working around — it's the reason hesitant customers convert.
You see it as predictable revenue landing on schedule; they see a subscription they can't get trapped in — the same mechanism serves both sides at once.
A subscription moves through a clear lifecycle — active, low_on_funds, past_due, cancelled — and QBitFlow pushes every transition to you in real time through the subscription status webhook. Configure it once and react the instant something changes: nudge a customer to top up, gate access, or save a churning account.
Getting started
- 1
Create your product and plan
Define what you're selling and the billing frequency (weekly, monthly, yearly, or custom), with an optional trial and optional minimum billing periods.
Subscriptions - 2
Configure your webhooks — once
In Settings → Webhooks, set your transaction endpoint (fires on each payment and on subscription creation) and your subscription status endpoint (fires on lifecycle changes). Do this first, so you're notified from the very first payment. Test and Live keep separate endpoints.
Webhooks - 3
Generate a subscription link — no frontend to build
You just define a session — the product, the billing frequency, the customer — with the SDK or API. QBitFlow hands you back a hosted checkout link; you share it and you're done. There's no checkout page to build and no payment UI to maintain: everything after the link is handled for you — the checkout page, the customer picking their crypto, the one-time allowance signature, payment processing, and error handling. When a payment goes through, your webhook fires — that's how you know.
Session checkouts - 4
Your customer subscribes in one signature
They open the link, pick their cryptocurrency, and approve the allowance once. That's the last action ever required of them — billing then runs automatically against that allowance, every cycle, with nothing more to sign.
Allowances & pricing - 5
Test, then go live
Run the full flow with a test key — including manually triggering a billing cycle — before switching on live mode.
Testing & going live
Less support, by design
QBitFlow hosts a public self-service page where your customers manage their own subscriptions — topping up, cancelling, viewing billing history, and requesting refunds — all without logging in and all verified by wallet signature. That's support load that never reaches your inbox. QBitFlow builds and maintains that whole subscription-management surface for you; you don't build any of it.
Pay on a schedule, in crypto, without getting trapped.
Subscribing takes one signature
You open the checkout link, pick the cryptocurrency you want to pay in, and sign one approval. That approval sets an allowance — a hard ceiling on how much can ever be charged, and over what period. After that, billing just happens on schedule. You don't re-sign every month, and you're never asked to hand your funds to anyone: the money stays in your wallet until each payment is due.
You decide how much you're willing to risk — up front
We've all done it: subscribed to something "just to try it," then forgotten. The card sat on file. You got charged for months before you noticed. The card model is built so that forgetting costs you money. QBitFlow flips that, because you choose your runway when you subscribe:
Just trying it out?
Approve a single period. After one cycle you cannot be charged again — by anyone. Getting billed for something you forgot about is structurally impossible.
Love it, want it hands-off?
Approve a long runway. Set an allowance that covers a year and never think about it again.
Somewhere in between?
Approve a few months at a time and top up as you go, keeping a light hand on the wheel.
So you can genuinely try a service with zero risk of a runaway charge, and deepen your commitment only once it's earned your trust. No hesitation, no guard up.
Manage everything yourself, anytime
QBitFlow gives you a self-service page for your subscription — no account, no login. You prove it's yours by signing with your wallet, and from there you can:
Top up your allowance
Extend your runway whenever you want to keep a subscription going.
Cancel the subscription
Instantly, with a wallet signature. No emails, no retention flow.
See your full billing history
Every charge, each with a link to view the transaction on a block explorer. Nothing is hidden — verify every payment on-chain yourself.
Request a refund on a billing
Raise a refund request for a specific charge directly from the page.
Adjust your limits
If prices move and a charge would exceed your cap, update it to keep the subscription running — or leave it, and the subscription simply pauses.
Your management page lives at a link the merchant shares with you, of the form:
qbitflow.app/user/<ref-id>/manage?uuid=<your-subscription-id>Why this is safer than a card
You never give a merchant a standing key to your money. You grant a bounded, revocable allowance that youcontrol, every charge is verifiable on-chain, and you can walk away at any time with a single signature. Security and transparency aren't features bolted on — they're how the whole thing is built.
Security, simplicity, and transparency — recurring, by design.