The points-program problem
Almost every retail business runs a loyalty program. Almost none of them work as well as the operator thinks.
The standard structure: customer earns points on every purchase, redeems them for discounts or rewards. The math looks clean. The reality is messier.
Three structural problems with conventional points programs:
1. Customers know the points are worth less than they look. A program that says "earn 1 point per dollar" and "100 points = $5 reward" is effectively offering 5% back. But customers correctly perceive the points as devalued currency — they have to remember a redemption code, the rewards expire, the catalog is limited, and the redemption math is opaque. The perceived value is usually 40-60% of the actual offered value.
2. Points only matter at your store. A customer who's collected 500 points at your business has 500 points worth nothing anywhere else. That's actually the intent of the design (lock-in), but it also caps the perceived value.
3. The accounting overhead is real. Points programs create a liability on your balance sheet — every point you've issued is a future obligation. Modern accounting standards (ASC 606) treat unredeemed loyalty points as deferred revenue.
Sats-back loyalty doesn't solve all three of these problems, but it solves the first two cleanly. And the third one is actually somewhat better because the obligation is denominated in Bitcoin, not dollars.
What sats-back loyalty actually is
The mechanic is simple: when a customer pays, you send them a small amount of Bitcoin (denominated in sats — the smaller unit, 100 million sats per Bitcoin) as a reward. Typically 1-5% of their purchase value.
The Bitcoin lands directly in their wallet via Lightning. No points balance to track. No redemption code. No expiration. They just have slightly more Bitcoin than they did five seconds ago.
What this changes for the customer:
- The reward is denominated in a real asset. Bitcoin isn't store credit. It's money the customer can spend anywhere Bitcoin is accepted, or hold as savings.
- The reward has no expiration. Bitcoin doesn't expire.
- The reward grows. If Bitcoin appreciates, their loyalty rewards literally grow in value.
What this changes for the merchant:
- No points balance system to maintain. The Bitcoin leaves your platform the moment you send it.
- Real-time accounting. Each reward is just an outbound Bitcoin payment, recorded the same way as any other payment.
- Brand differentiation. In 2026, sats-back loyalty is still a noticeable point of differentiation.
The math, with real numbers
Let's compare a 2% sats-back program against a 5% points program (which sounds more generous on paper).
Scenario: A merchant doing $300K/year in card revenue, with 40% repeat-customer rate.
5% points program:
- Theoretical cost: 5% × $300K = $15,000/year in rewards offered.
- Actual redemption rate: ~50% (industry average). $7,500 in actual rewards delivered.
- Perceived value to customers: ~60% of face value. Customers feel they got $4,500 of value.
2% sats-back program:
- Theoretical cost: 2% × $300K = $6,000/year in rewards offered.
- Actual delivery rate: ~99% (Bitcoin goes directly to wallet — no redemption required).
- Perceived value to customers: ~100% of face value (real asset, no expiration).
The 2% sats-back program costs less than the 5% points program, delivers more actual value to customers, and avoids the accounting complexity. The points program sounds more generous on the marketing material; the sats-back program is more generous in reality.
Setting it up
Configuration through your VoltageAI dashboard takes about 15 minutes:
- Enable the sats-back program in your dashboard under Loyalty Settings.
- Set the reward percentage — common settings are 1%, 2%, 3%, or 5%. We recommend 2% as the starting point.
- Choose the trigger — typically "every purchase" but you can scope to "purchases over $X" or "card payments only."
- Configure the delivery mechanism — customer's Bitcoin payment automatically returns sats to the same wallet. For card-paying customers, they receive a Lightning invoice link via email or SMS.
- Communicate the program to customers — via signage, receipt language, or website copy.
Cohort data: what we've observed
For merchants who've run sats-back programs for at least 6 months:
Customer participation:
- Among Bitcoin-paying customers: ~95% participate.
- Among card-paying customers: ~25% claim their sats reward via the email/SMS link.
- Net effective reward rate: For a 2% sats-back program, expect to actually pay about 1.4% across the full customer base.
Customer behavior change:
- Repeat-purchase rate from sats-back claimants is typically 1.5-2x higher than from non-claimants.
- Average transaction size from sats-back claimants is 15-30% higher.
- Word-of-mouth: merchants consistently report sats-back is the most-mentioned feature when customers explain why they shop with them.
When sats-back doesn't make sense
Worth being honest about this. Sats-back is not for every merchant.
Don't run sats-back if:
- Your customer base is mostly older (60+) and Bitcoin is unfamiliar to them.
- Your margins are too thin to give back 1-2% on every transaction.
- Your existing points program is generating strong observable value.
- You're philosophically opposed to participating in Bitcoin beyond accepting it.
Do run sats-back if:
- Your customer base skews younger, tech-aware, or international.
- Your average transaction value is meaningful enough that 1-3% back is a real reward.
- You're looking for differentiation in a competitive local market.
- You want a loyalty program with no operational overhead.
What's next
Next up: Lesson 12 — Paying contractors internationally. Manila, Lagos, Buenos Aires — same payout, no wires, no FX fees, no 5-day delays.
Frequently asked
Questions that come up after this lesson.