Engineering
How we solved chargebacks without custody: the QBitFlow refund architecture.
QBitFlow Team
9 min read
On this page · 6 sections
The QBitFlow refund architecture
Every conversation about non-custodial crypto payments hits the same wall.
You walk through the architecture: funds go directly from the buyer's wallet to the merchant's, no escrow, no holding period, no processor sitting in the middle. Someone in the room nods along until you finish, then asks the question that ends most of these conversations: "but what about chargebacks?"
The assumption underneath the question is that chargebacks equal consumer protection. Remove them and you remove the safety net. No safety net means scams, exit-scams, and customers left holding the bag. The dichotomy is clean: card rails protect buyers, crypto rails do not, and that gap is why crypto cannot replace cards.
Chargebacks aren't consumer protection. They're forced arbitration with a cost baked into every transaction the merchant processes, clean or not. Removing them isn't removing a safety net; it's removing that cost. The interesting question isn't whether to keep them. It's what you build instead: a dispute-resolution layer that protects buyers without seizing funds, charging merchants for other people's disputes, or putting an opaque arbiter between two willing parties.
This is what we shipped at QBitFlow. The architecture, the trade-offs, and why we think it's a better deal for both sides than the chargeback model it replaces.
What chargebacks actually are
Strip away the consumer-facing marketing and a chargeback is three things stacked on top of each other.
One: a fraud-reserve levy. Roughly 1% of card interchange goes into the fraud-reserve bucket that funds chargeback resolutions. Every merchant pays this, on every transaction, whether they cause a chargeback or not. The honest sellers subsidize the dishonest ones. There is no opt-out. If you process cards, you pay it.
Two: an opaque arbitration process. When a chargeback is filed, the card network's arbitration process decides who's right. The merchant submits evidence through a portal, the cardholder submits their side, and the network rules. Merchants regularly report decisions that contradict the evidence they provided, with no explanation, no appeal path that works at scale, and no transparency on the decision criteria. The arbiter is the same company that benefits from the fee structure, which is a conflict structure most regulators would not let stand in any other industry.
Three: a stack of penalties layered on top. Stripe holds reserves for 7+ days. Chargeback fees run $15–$25 per dispute, whether you win or lose. Adverse decisions claw back the original transaction amount plus the fee. A merchant with a chargeback ratio above 1% gets flagged, throttled, or shut down, and "1%" is the ratio across all transactions, meaning a single bad month against a small base is enough to trigger the algorithm.
Sum it up and the "protection" narrative starts to look like marketing. Buyers get a recourse mechanism, yes. But the cost of that mechanism is paid by every merchant on every transaction, and the mechanism itself is run by an entity that profits from the fee structure, makes decisions in private, and reserves the right to deplatform you if its statistics say so.
The right framing isn't "chargebacks protect consumers." It's "chargebacks redistribute fraud loss from buyers to merchants, with a fee for the privilege of being inside the system." That's a defensible product. It's not the only possible product.
What we built instead
The design constraint was straightforward: keep the dispute resolution that buyers actually need, drop everything that exists to serve the processor rather than either party, and never custody funds.
Here's the flow.
The customer side
Every QBitFlow payment gives the buyer their own page for it. The page shows the transaction hash, the amount, the merchant and the product, and, for a completed payment, a "Request refund" button. A subscription's bills can be refunded the same way.
When the buyer requests a refund, three things happen:
- They write why they want the refund.
- They sign a message from the wallet that made the original payment, proving they own that wallet today.
- The refund request lands in the merchant's dashboard, attached to the original transaction.
The wallet signature step matters. Without it, anyone with the transaction hash could pose as the buyer. With it, the merchant has cryptographic proof that the request comes from the wallet that paid: no email account takeover, no impersonation, no social-engineering path.
You decide whether customers can request refunds, and for how long after a payment: 30 days by default, set in your settings.
The merchant side
Refund requests don't sit in an email queue or a hidden tab. They surface on your dashboard's home, among what needs your attention, because they're one of the few things there that needs a decision.
You see the full context: the original transaction, the buyer's wallet, the written explanation, and the timestamp. From there, two paths:
Accept. You choose the share to send back, all of it or part of it. The base is everything the buyer paid: the amount, the fees, and the network fee they paid on top. The dashboard prepares the transfer, you sign it from the wallet that was paid, and the buyer has the funds back once the transaction confirms. Both parties get an on-chain record of the refund, and it shows in your records and your accounting export.
Refuse. You must write why. Your answer shows on the buyer's refund page, beside the original transaction. There's no path to refuse silently and leave the buyer wondering.
You can also refund a payment without being asked: start the refund yourself, then sign it the same way.
That's the whole flow. No escrow. No reserves. No processor sitting in arbitration. No fee per dispute. Two parties, one transaction history, and a written record of every step.
Why this is structurally better
The chargeback model and the refund model both resolve disputes. The difference is who pays, who decides, and what the record looks like when it's over.
The merchant decides, not the processor. You have full context: you shipped the product, ran the service, talked to the buyer. You're closer to the truth than a Visa arbitration team that has never seen either party. When you get it wrong, the buyer has the receipts: the on-chain payment, the request they filed, and your written refusal on their refund page.
No interchange levy on the 99% of clean transactions. Honest merchants stop subsidizing dishonest ones. The cost of dispute resolution is paid by the disputes that happen, not socialized across every transaction. If you process a thousand payments and have zero refund requests, you pay zero dispute costs. That's not how cards work and never will be.
No 7-day reserve, no $25 dispute fee, no chargeback ratio. The money is in your wallet once the payment confirms. There's no holding period, no per-dispute penalty, no algorithm watching your ratio and deciding whether to throttle your account this quarter. Your relationship is with the buyer, not with a processor's risk team.
Verifiable, end to end. Visa's chargeback decisions are opaque by design. QBitFlow's are not. The money layer (the original payment and any refund transfer) is on-chain and immutable, queryable from any block explorer. The decision layer (whether you refunded or refused, your answer, the timestamps) shows on the buyer's refund page, and every step sends you a webhook: refund.requested, refund.completed, refund.denied. Whether a refund happened is never a matter of opinion.
Buyers keep a meaningful recourse. Within your refund window, the buyer can request a refund of any completed payment. If you refuse without grounds, the buyer has the record: the on-chain payment, their signed request, and your written refusal. The protection is real. It's just not enforced by a third party seizing funds you have already earned.
Trade-offs we accept
This isn't a clean-sweep win.
One refund per payment. A payment (or a bill) can be refunded once, fully or partly. If you refund 30% today, you can't send another 20% through the same flow next week. Settle on the right share before you sign.
No automated arbiter when the merchant goes silent. The chargeback model has an end-state: Visa rules, money moves, the case closes. The QBitFlow model relies on the merchant responding. If a merchant ghosts a refund request, the buyer's recourse is the written record, not a forced settlement. For most merchants this is fine; the dashboard puts refund requests in front of you, exactly to make ghosting unlikely. For pathological cases, the record does the work, but that's slower than a 30-day Visa cycle.
Network fees shift in the refund flow. Across the rest of QBitFlow, the customer pays the network fee. Refunds are the inverse: the refund transfer is sent from your wallet, so your wallet pays the network fee on the refund itself. The buyer's request is a wallet signature, not a transaction, so it costs them nothing. And QBitFlow keeps its fee on the original payment. Net effect: you absorb a small on-chain cost when you accept a refund. Small on Base or Solana, more noticeable on Ethereum mainnet. Worth pricing in.
We name these because they're real. The point isn't that the chargeback model has no virtues. The point is that the virtues it has come bundled with a fee structure and an opacity that most merchants would not voluntarily sign up for if they were pricing them honestly. Trade off the opacity and the levy, accept that the merchant must respond, and you end up with something that respects both parties' time and money more than the existing system.
The bigger thesis
The cardinal sin of crypto payments thinking was treating "non-custodial" as synonymous with "no protection." That framing concedes the entire dispute-resolution layer to the legacy rails and tries to compete only on settlement speed and fees. It loses the conversation in the second sentence.
The right framing is that non-custodial is a settlement architecture, not a recourse architecture. The recourse layer can be rebuilt on top of non-custodial settlement: better, more transparently, with the merchant as decision-maker instead of an opaque third party. You don't have to choose between "buyer keeps Visa-style protection" and "merchant keeps the funds the buyer sent them." Both can be true.
QBitFlow's broader product thesis is exactly this: the rails are the easy part. The interesting work is the tools around the rails: subscriptions that don't custody, marketplace fee splits that settle on-chain, refund flows that don't charge clean merchants for other people's disputes. Each one rebuilds a piece of the payments stack that custodial processors charge a premium for, on terms that respect the architecture underneath.
The refund flow is live in QBitFlow today. Every payment and every subscription bill supports the request-and-respond flow described above. The smart contracts are open-source on GitHub, readable and forkable by anyone who wants to dig in. They're not formally audited yet; until then, the code is open.
If you've been turning away from non-custodial crypto payments because "but chargebacks," this is the answer. Chargebacks aren't a feature you pay 1% interchange forever to keep. They're a feature you ship, and shipping it differently turns out to be cheaper, more transparent, and more respectful of both parties.
Try the flow in test mode. See for yourself.
Try it: Sign up at qbitflow.app, take test tokens from the dashboard's faucet, and run the full refund flow end to end in test mode.
Builders: an SDK can start a refund (POST /transaction/refunds/initiate), and the refund.* webhooks tell you each step. Sending the money is signed in the dashboard, from the wallet that was paid. Details at qbitflow.app/docs/api.
Smart contracts: Open-source on github.com/QBitFlow: readable, forkable, verifiable on-chain (the Solana program's verified build is pending). Not formally audited yet.



