How a Points Expiration Clock Is Triggered

Credit card rewards programs assign points a finite lifespan, but the countdown rarely begins at the moment a point is earned. Instead, the expiration clock is a conditional timer — it starts, pauses, resets, or accelerates based on discrete account events defined entirely within the program's own terms and conditions. Federal law does not standardize how points expire, which means the triggering logic varies considerably from one program to another.

Understanding the expiration mechanism requires separating two distinct concepts: the trigger (the event that starts or resets the clock) and the forfeiture rule (the condition under which accumulated points are actually removed from the balance). Both are governed by the card issuer's program agreement, a document that functions as the authoritative rulebook for the rewards system.

The Events That Actually Start or Reset the Expiration Timer

The most common trigger architecture is activity-based expiration. Under this model, the program tracks the date of the most recent qualifying activity on the account — typically a purchase, a redemption, or both — and sets a rolling window, often 12, 18, or 24 months, measured forward from that date. If no qualifying activity occurs before the window closes, all accumulated points are forfeited. The clock does not tick from the date a point was earned; it ticks from the date of the last eligible event. A single qualifying transaction resets the entire balance's expiration window, including points earned years earlier.

A second architecture is anniversary-based expiration. Here, the program assigns each batch of points an expiration date tied to the anniversary of the account opening or the end of the calendar year in which the points were earned. Points earned in January and points earned in November of the same year may share the same December 31 forfeiture date. This model does not reset with activity — the date is fixed at the time the points are credited, and no subsequent transaction alters it.

A third, less common model is a hybrid: points carry a fixed lifespan from the date they are individually earned (e.g., 36 months per point batch), but qualifying activity may extend that window by a set number of months. In this case, the program tracks both a per-point expiration date and a global activity date, and applies whichever is more favorable to the cardholder — or, in some programs, whichever results in earlier forfeiture.

Account status events can also serve as immediate triggers. Account closure — whether initiated by the cardholder or the issuer — typically causes all unredeemed points to expire at once, often within a short grace window of 30 to 90 days, or sometimes immediately upon closure. A similar forfeiture event can be triggered by a delinquency: some programs void the entire points balance when an account becomes significantly past due, a mechanism that operates independently of any activity-based clock. This delinquency-triggered forfeiture is disclosed in the program terms but is frequently overlooked because it appears in a different section from the standard expiration rules. The mechanics of how an account reaches delinquency — including how a late fee is calculated and capped — are governed by separate regulatory frameworks, but the downstream effect on rewards is determined solely by program policy.

The Components and Parties That Govern the Clock

The program agreement. This is the legal document — typically incorporated by reference into the card's terms and conditions — that defines every rule governing point accrual, valuation, and forfeiture. It specifies what counts as qualifying activity, what the expiration window is, and what events cause immediate forfeiture. Amendments to this agreement can alter expiration rules prospectively, and issuers are generally required to provide advance notice of material changes under the Truth in Lending Act (TILA) and its implementing regulation, Regulation Z.

The card issuer. A card issuer operates the rewards ledger as a liability on its own books. Points represent a contingent obligation — the issuer owes the cardholder a future redemption value. Expiration rules reduce that liability. The issuer's systems log the timestamp of every qualifying transaction and compare it against the program's trigger thresholds during each billing cycle processing run.

The cardholder's account record. The account record contains the last-activity date, the current points balance, and, in some program architectures, individual point-batch timestamps. The expiration engine queries this record to determine whether a forfeiture event has occurred. The record is internal to the issuer's systems and is not reported to credit bureaus — points balances and expiration events have no effect on a credit file or on how a FICO score's five factors are weighted.

Partner networks. Many rewards programs are linked to airline, hotel, or retail loyalty programs. In these arrangements, a transfer of points from the card program to the partner program may itself constitute qualifying activity that resets the card program's expiration clock — or it may not, depending on the agreement between the card issuer and the partner. The partner program then applies its own independent expiration rules to the transferred points, which may differ entirely from the card program's rules.

Where the Clock Produces Results Cardholders Do Not Anticipate

The most common source of unexpected forfeiture is the gap between what a cardholder believes counts as qualifying activity and what the program actually recognizes. A redemption for one reward category (e.g., merchandise) may not reset the clock in the same way as a redemption for another category (e.g., travel). A purchase that earns zero points — such as a balance transfer or a cash advance — is frequently excluded from the definition of qualifying activity even though it appears on the statement as a transaction. The mechanics of how a cash advance differs from a purchase in fee and rate structure extends to the rewards layer as well: cash advances typically earn no points and do not reset an activity-based expiration clock.

A second friction point arises from program amendments. An issuer may lengthen or shorten the expiration window, or change the definition of qualifying activity, with advance notice. If a cardholder is operating on a mental model of the old rules, the new clock may expire points sooner than expected. The amendment notice is often delivered as a statement insert or a separate mailing and may not be prominently flagged.

Account closure creates a particularly abrupt forfeiture scenario. When an issuer closes an account for inactivity — a separate mechanism from expiration, though related — any points that have not yet expired may be immediately voided. The cardholder may not receive advance notice of the account closure itself, only of the general policy that closure causes forfeiture. The sequence of events (account closure, then forfeiture) can compress into a very short window.

Finally, program discontinuation — when an issuer ends a rewards program entirely — typically triggers a wind-down period during which all points must be redeemed. The length of that window is set by the issuer and disclosed in the discontinuation notice. Points not redeemed within the window are permanently forfeited, regardless of the account's activity status or how recently points were earned.

What the Statement and Program Disclosure Actually Show About Expiration

A monthly credit card statement typically displays the current points balance and, in many programs, the number of points scheduled to expire within the next billing cycle or within a defined forward window (commonly 30 to 90 days). What the statement does not show is the full expiration schedule for all point batches in a hybrid architecture, the precise last-activity date the system has recorded, or the complete list of events that would or would not qualify as activity under the program rules.

The program agreement — not the statement — is the authoritative record of the expiration trigger logic. Under Regulation Z, certain credit card terms must be disclosed in the Schumer Box (the standardized table of key terms), but rewards program details, including expiration rules, are not required to appear there. They are disclosed in the program terms, which are a separate document. The CFPB has noted that rewards terms can be lengthy and complex, and that material program changes must be communicated to cardholders in advance, but the agency does not prescribe the format or placement of expiration disclosures within the program document itself.

An online account portal may display a more granular expiration schedule than the paper statement, including per-batch expiration dates in programs that use fixed-date architecture. However, the portal display is a convenience feature, not a regulatory requirement, and its accuracy depends on the issuer's internal data systems correctly populating the display fields. Discrepancies between the portal display and the actual program ledger are resolved by the program agreement, not by the portal.

The expiration clock in a rewards program is a contractual mechanism, not a regulatory one — its triggers, resets, and forfeiture conditions exist entirely within the program agreement, and the diversity of architectures across programs reflects the absence of any federal standard governing how or when points must expire.

Note: This explains how credit cards work as financial systems. It is not financial advice, it is not a recommendation of any card or provider, and it is not a substitute for the CFPB's own guidance. Check the cited sources for current regulatory detail.