Refunds, disputes, and the things that don't happen

The mental model

Before getting into the mechanics, the framing that makes this lesson useful:

Cards are designed around customer protection. The chargeback system exists because credit cards extend the customer credit, the customer doesn't always trust the merchant, and the bank wants a mechanism to claw back funds if something goes wrong. The merchant lives with this.

Bitcoin is designed around finality. Once a Lightning payment lands, it's permanent. No bank in the middle, no third-party authority that can reverse it. The customer doesn't have a "I want my money back" button on their wallet the way they do with their credit card.

This sounds harsh from a customer perspective. In practice, it isn't — because legitimate refunds are still possible and easy. What disappears is the unilateral chargeback — the customer's ability to call their bank, dispute a charge, and get their money back without your involvement.

The trade-off works in your favor in almost every realistic scenario.

What refunds look like in practice

A customer paid you $87 in Bitcoin two weeks ago. The product didn't fit, they want to return it. Here's what happens:

1. The customer brings the product back to you (or ships it, same as any return).
2. They give you their Lightning address or a Lightning invoice for a refund.
3. You open your VoltageAI dashboard, find the original transaction, tap "Refund."
4. The system asks you to enter the refund amount (up to the original $87) and the customer's Lightning destination.
5. You confirm. The system sends Bitcoin equivalent to $87 at the current price back to the customer's wallet. (You can choose to send Bitcoin-equivalent to the original USD amount, or Bitcoin-equivalent to the current USD amount of the original Bitcoin paid — most merchants choose the former, which protects the customer from Bitcoin's price moves between purchase and refund.)
6. Customer's wallet receives the funds in seconds. Refund complete.

Total time on your side: about 60 seconds. Faster than a card refund, which typically takes 3–10 business days to appear back on the customer's statement.

The four "what about..." questions

When merchants new to Bitcoin think about refunds and disputes, they raise four predictable concerns.

"What about chargebacks?"

Gone. A chargeback is a card-network mechanism. Bitcoin doesn't have card networks. The customer can't call Visa and dispute a charge because no Visa was involved.

This matters more than it sounds. The average US merchant loses 0.5–1.5% of their card revenue to chargeback fees, fraudulent disputes, and the labor of contesting them. For a business doing $1M in annual card revenue, that's $5,000–$15,000 per year in pure loss. On Lightning, that line item is zero.

Customers who want a refund can still get one — they just have to ask you. You become the gatekeeper of refund legitimacy, which is the model most merchants actually want.

"What about fraud?"

Transformed. Card fraud comes in two main flavors:

1. Stolen card fraud — someone uses a stolen card number to pay you, and the cardholder later disputes. Card networks protect the cardholder; the merchant loses the goods AND the money. Lightning eliminates this entirely because Bitcoin payments are bearer payments — the person with the Bitcoin sent it on purpose.

2. Friendly fraud — a real customer pays, then disputes the charge anyway, claiming they didn't recognize it. About 80% of US merchant chargebacks are friendly fraud. Lightning eliminates this entirely too — the customer's wallet has a clear, signed record of every payment they sent.

Bitcoin doesn't eliminate every form of fraud (a customer can still pay, then claim they never received the product), but it eliminates the categories that account for nearly all merchant losses.

"What about my reserve account?"

Goes away. Card processors often hold a percentage of your sales in a "reserve account" — typically 5–10% — for 90+ days as a hedge against chargebacks. This is real working capital you can't access.

Bitcoin payment processors don't need to hold reserves for chargebacks because chargebacks don't happen. Your funds settle to your bank account on the normal payout schedule (daily for most merchants), with no portion held back.

For a business doing $100K/month, eliminating a 10% reserve means recovering $10K of working capital, every month, that was previously locked up.

"What about the 'unhappy customer' problem?"

Becomes a conversation. This is the only one where Bitcoin requires you to do more work, not less.

On cards, an unhappy customer can call their bank and unilaterally start a chargeback. On Bitcoin, an unhappy customer has to come to you and ask. You decide whether to refund. If you say no, they have no escalation path through a payment network — their only recourse is reviews, social media, or small claims court.

This sounds like a customer service nightmare. In practice, it's the opposite: it forces every refund to be a conversation, which means you handle most of them quickly and fairly, and the rare bad-faith refund request gets denied (which on a card you couldn't refuse).

The merchants who do this well treat the refund conversation as a service moment, not a defensive posture.

Partial refunds, store credit, and exchanges

All standard features.

• Partial refund: Same flow as a full refund — you just enter a smaller amount in the refund field.
• Store credit: Issued the same way you'd issue store credit on any sale — via your e-commerce platform or POS, not through the Bitcoin payment system.
• Exchange: No refund needed. The customer brings back item A, you give them item B at the same price.

Disputes that aren't chargebacks

There's still a category of dispute you can face — even without card chargebacks:

• Reviews and social media complaints. This isn't a payment dispute; it's a reputation dispute. Standard customer service applies.
• Small claims court. Rare, but possible. Bitcoin payments are well-documented (every transaction has a verifiable record on the Lightning network), which actually helps your case.
• Marketplace platform disputes (Etsy, eBay, etc.). If you sell through a marketplace with its own dispute system, the marketplace's rules govern.

For 99% of merchants, the dispute landscape on Bitcoin is dramatically simpler than on cards.

When you should — and shouldn't — refund

A useful framing: Bitcoin refunds give you the same discretion you have with cash.

Almost always refund:

• Defective product
• Wrong product shipped
• Within published return policy window
• Customer was misled by the listing

Case-by-case:

• Outside return window but reasonable explanation
• Product as described but customer doesn't like it
• Customer used the product for a while and now wants to return

Almost never refund:

• Customer demands a refund for service rendered (e.g., they ate the meal and now want their money back)
• Customer claims fraud you can't verify
• Repeated customer making suspicious refund requests across multiple orders

The discretion is yours. On a card, you don't have it — the chargeback system makes the customer's claim primary. On Bitcoin, your judgment is primary.

What's next

Next up: Lesson 9 — Reading your dashboard: what numbers actually matter. Volume, conversion, settlement timing, hold-or-sell rate.