Estimated value
Uses the modeled midpoint for each program. This is best for users who redeem strategically, including transfer partners and higher-value travel redemptions where available.
Currency: configured base currency
Value unit: cents per point (cpp)
Valuations last verified: 2026-02-27
How CreditCombo converts rewards to cash value
For each rewards program, CreditCombo stores an estimated cpp value and a minimum guaranteed cpp value. Your selected mode controls which value is used to convert reward units into annual cash-equivalent value.
annual_value = annual_reward_units × (selected_cpp ÷ 100)
Two valuation modes
Minimum guaranteed value
Uses the conservative floor for each program. This reflects broadly accessible redemption paths such as statement credits, cashback, fixed-value travel portals, and other reliable low-variance options.
Cashback-denominated programs are modeled at face value (1.0 cpp equivalent), so estimated and minimum values are usually the same.
Where valuation inputs come from
- Published third-party points valuations are used as primary benchmarks for points programs.
- Additional valuation references are used as fallback benchmarks where primary valuations are unavailable.
- Program and issuer documentation are used to verify transfer mechanics, redemption structures, and fixed-value floor paths.
These values are directional planning estimates, not guaranteed redemption outcomes for every itinerary, merchant, or booking channel.
How to pick a mode in practice
- Choose Estimated value if you are willing to optimize transfers and redemption timing.
- Choose Minimum guaranteed value if you want a lower-bound forecast that is less sensitive to redemption strategy.
- Compare both modes to understand upside range versus dependable baseline.
What CreditCombo models today
- Category spend is allocated to the highest value card first, with cap overflow rerouted to the next best eligible card.
- Annual fees are subtracted from gross rewards to report net annual value.
- Programs marked as non-earning are excluded from optimization value contribution.
Out of scope: unstructured merchant/portal-specific special rules, MCC edge cases, broad acceptance constraints, and one-time promotions or welcome bonuses.