Hey all Paul here, founder of QBitFlow. We go live Tuesday, and I wanted to open a thread early for anyone who's ever fought with getting paid. Quick version of why this exists: I kept hitting crypto "subscriptions" that were really just "prepay 6 months and trust us." And cards aren't actually safer you hand a company the keys to your account and hope they only take what's fair. The real problem was never crypto vs cards. It was trust. So I built QBitFlow: accept crypto payments and run real subscriptions where the money goes straight from your customer's wallet to yours. We never hold it, you hold the keys, and for subscriptions the amount and schedule are enforced on-chain the merchant literally can't pull more than agreed. Live in minutes, no KYC. I'd genuinely love feedback from people who've felt this pain before Tuesday. Two questions:
What's your worst "getting paid" story a held payout, a frozen account, a country locked out, a subscription you couldn't trust?
If you accept (or want to accept) crypto, what's the one thing that's stopped you or annoyed you most?
I'll be in here answering everything. Tear it apart that's how it gets better.
@qbitflow safety in transactions is such an important factor now more than ever, this is awesome
@salome_coste Thanks so much 🙏
That's exactly it — the safest payment is the one that's already yours. Straight to your wallet, you hold the keys, on-chain and verifiable. Grateful for the support! 🚀
@qbitflow How do the recurring subscriptions actually work if you never hold the funds? That's the part I've never seen done properly in crypto — what stops a merchant from just charging whatever they want?
@julien_couderc Great question — this is the part I'm most proud of, because it's the reason QBitFlow exists.
When your customer subscribes, they sign a one-time on-chain authorization that sets two things: the amount per cycle and the schedule. That approval is enforced by the smart contract itself — so when a payment's due, the contract releases exactly that agreed amount from the customer's wallet to yours, and not a cent more. If a merchant tried to charge double, the contract would simply reject it. It's not a policy or a promise — it's math.
And the customer stays in control the whole time: they can raise their cap, or cancel on-chain, themselves — no emailing support, no dark patterns. Compare that to a card, where you hand over your number and hope they only take what's fair.
So: real recurring billing, but nobody has to trust anybody. That "approve once, can't be overcharged, cancel anytime" model is exactly what didn't exist before — everything else was just "prepay and trust us." That's the gap we built for.
the no-chargeback angle is genuinely refreshing, feels like the first time a payments pitch actually put my mind at ease rather than pitching me on features i dont need
@berke9f56 Thank you — that genuinely means a lot, because it's exactly the nerve we were trying to hit. Chargebacks (and held payouts, frozen accounts) are the quiet anxiety every merchant lives with, and no amount of feature-listing fixes that feeling — only removing the risk does. Curious: are you selling something today, or building toward it? Would love to hear what your setup looks like.