Tier Expiry Card: How Keep Points?
Every loyalty engine that ties reward tiers to a countdown timer eventually hits the same brutal wall: the second the clock hits zero, a player's entire point balance evaporates and the support queue detonates. The Tier Expiry Card is the patch most operators bolt on to stop that bleed, but the mechanics behind it are where platforms quietly get it wrong. I have audited enough reward ledgers to know that a badly wired expiry card does not protect the player โ it just delays the execution and hides the corpse. ๐
The Core Loop of a Tier Expiry Card
Strip away the marketing gloss and the mechanism is simple: when a tier window closes, the system checks for a valid expiry card, and if one is present, it freezes the tier status and the attached loyalty points for a fixed grace period. The trap is in the state machine. A properly built card must snapshot the point balance at the moment of expiry, not read it live, otherwise every wager made during the grace window silently mutates the frozen ledger and the reconciliation breaks at settlement. I have seen operators run a live read against a frozen tier and create phantom points that never existed in any transaction log.
Where the Points Actually Get Kept
The honest answer to how to keep points is that the card does not preserve them forever โ it buys time, and the engineering has to respect that boundary. During the grace period, the player must requalify or spend the card to convert the temporary hold into a permanent tier credit. The failure mode I keep finding is a card that renews the tier without touching the expiry timestamp, which means the tier never truly dies and the point liability on the books compounds quarter after quarter. That is not retention, that is an accounting time bomb. ๐งจ
The clean implementation writes an immutable expiry event to the ledger, tags the card as a compensating entry, and sets a hard ceiling on how many times a single account can chain cards across consecutive cycles. Without that ceiling, whales stack cards indefinitely and the house carries a point liability it can never reconcile.
Algorithmic Integrity and the Point Ledger
Point retention is a ledger problem before it is a rewards problem. Every expiry card must produce a paired debit and credit so the running balance stays auditable, and the grace window must be enforced at the query layer, not the presentation layer. If the front end hides an expired tier while the back end still serves the point balance, you have built a lie with a nice UI. Real tier expiration logic lives in the same transaction that closes the cycle, and the card is nothing more than a controlled reversal. ๐
Rate of Decay and the Card Multiplier
Here is the part most reward teams miss: the value of keeping points is not binary, it decays. A well-tuned expiry card applies a decay multiplier to the frozen balance across the grace window, so a player who waits until the last day to requalify keeps less than one who acts on day one. Set the multiplier too generous and the card becomes free money; set it too harsh and players abandon the tier entirely. The sweet spot sits in a narrow band, and I have watched operators burn millions in point liability by refusing to model that decay curve before shipping the feature.
Audit the card against the transaction log weekly, cap chained renewals at the account level, and force the decay multiplier into the settlement path. Anything less and the expiry card is a cosmetic patch on a leaking ledger.