How Double Dipping Works
Classic Double Dip Example
Retailer Loyalty
Earn 100 points on $100 purchase
1% value = $1
Credit Card Rewards
Earn 200 points on $100 purchase
2% value = $2
Total Value
$3 in rewards from $100
3% effective return
Reward Sources That Stack
Retailer Loyalty Programs
Points earned directly from the merchant. Usually required to identify yourself (card scan, phone number, app). The foundation for most stacking.
Credit Card Rewards
Points/cashback from payment card. Earned regardless of loyalty program participation. Category bonuses (3x on groceries) increase value.
Shopping Portals
Click through airline/bank shopping portals for bonus miles/points. Start at portal, then shop normally. Often overlooked but adds significant value.
Digital Coupons & Offers
Manufacturer or retailer digital coupons loaded to loyalty account. Stack with points earning for price reduction + reward accumulation.
Receipt Apps
Apps like Ibotta, Fetch, or Receipt Hog reward for scanning receipts. Post-purchase layer that works alongside other rewards.
Partner Programs
Coalition partners or transfer partners. Earn in one program, transfer to another. Multiplies value through partnerships.
Stacking Strategies
Grocery Shopping Stack
Maximize grocery rewards:
- Load digital manufacturer coupons to loyalty card
- Activate loyalty app bonus offers
- Shop through grocery delivery for delivery promo
- Pay with 3x grocery credit card
- Scan receipt in Ibotta/Fetch
Potential: 8-12% total value
Online Shopping Stack
Maximize e-commerce rewards:
- Start at airline/bank shopping portal
- Use retailer loyalty account
- Apply coupon codes
- Pay with best-category credit card
- Earn retailer credit card bonus if applicable
Potential: 6-10% total value
Fuel Purchase Stack
Maximize fuel rewards:
- Earn cents-per-gallon discount from grocery loyalty
- Use fuel station loyalty program
- Pay with fuel bonus credit card (5%)
- Use fuel app for station-specific bonus
Potential: $0.25-0.50+ per gallon savings
The Loyalty Game
There's an entire community of "points maximizers" who treat reward stacking as a hobby. They know which cards work with which portals, optimal redemption values, and transfer partner sweet spots. Your most engaged members may be playing this game—reward their engagement.
Program Design Considerations
- 1. Don't fight credit card rewards. Customers will use rewards cards regardless. Your loyalty program should complement, not compete with, payment rewards. Make it easy to stack.
- 2. Clarify offer stacking rules. Be explicit about what can combine. "Cannot combine with other offers" frustrates customers expecting to stack. If stacking is allowed, say so.
- 3. Consider partner integrations. Coalition partnerships enable intentional stacking. Members earn your points AND partner benefits. This can be a feature, not a cost leak.
- 4. Watch for abuse. Intentional stacking is fine; gaming loopholes isn't. Monitor for suspicious patterns—multiple accounts, coupon fraud, or systematic exploitation of unclear rules.
- 5. Embrace your stackers. Members who optimize rewards are often your most engaged customers. They shop more frequently to maximize value. Reward their engagement rather than penalizing optimization.
- 6. Co-branded card opportunity. A co-branded credit card turns payment rewards into YOUR loyalty currency. Members earn your points from both loyalty program AND payment—stacking within your ecosystem.
| Stacking Scenario | Customer Value | Program Impact |
|---|---|---|
| Loyalty + credit card | High combined value | Neutral (no extra cost) |
| Loyalty + digital coupons | Discount + points | Funded by manufacturer |
| Multiple promotions | Maximum savings | Higher cost if unrestricted |
| Coalition + own program | Earn everywhere | Shared cost with partners |
Exchange Solutions Stacking Support
Exchange Solutions' platform handles complex stacking scenarios—clear offer combination rules, partner integration for coalition earning, and fraud detection to catch abuse while rewarding legitimate optimization. Let members maximize value within the rules you set.
