Find Recurring Charges Across Credit Card Statements
The finder compares normalized descriptor clues, debit direction, interval consistency, amount behavior, and history. It produces candidates for review, not a list of proven subscriptions.
Find recurring charge candidates
Multiple statements · pattern review
Preparing your private analysis
Your statement is being secured before analysis begins.
Leave this window open; your private results will load here when ready.

How one candidate appears
Three fictional rows show a near-monthly cadence and a later price change, which still requires independent confirmation.
Evidence for a candidate
A credible candidate repeats in the same direction and shows compatible merchant evidence across more than one cycle.
Cadence can be monthly, annual, weekly, or irregular within an explainable window; identical wording alone is insufficient.
Patterns that need care
Taxes, usage pricing, foreign conversion, promotions, and annual increases can change the amount without ending recurrence.
Installments, duplicated charges, marketplace purchases, refunds, and payroll-like credits can resemble a recurring pattern for different reasons.
Confirm before acting
Check invoices, merchant accounts, contract terms, authorized users, and the issuer record before calling a candidate active or unwanted.
Record the next expected date, cancellation route, contact evidence, and final decision without exposing the card number.
Candidate confirmation record
- At least two source rows support the candidate.
- Direction and merchant evidence are compatible.
- The interval and any amount change are explained.
- Refunds, installments, and duplicates were considered.
- Status was confirmed through a trusted source before action.
Maintain a candidate decision sheet
For every candidate, list the supporting rows, normalized clue, observed intervals, amount range, missed cycles, price changes, and evidence checked outside the statement. Keep confirmed, inactive, cancelled, and unresolved statuses separate.
Set a next expected date and review it after the period passes. A missed prediction is useful evidence that the pattern, merchant match, or account status needs another look.
Keep dismissed candidates with a short reason so the same harmless pattern does not return as a fresh alert every cycle. Reopen the decision when the descriptor, cadence, amount behavior, authorization, or merchant evidence changes.
Example: a price change after two equal charges
Two monthly rows share the same descriptor and value; the third arrives two days late at a higher price. The sequence remains a candidate because cadence and merchant evidence agree.
An invoice or merchant account is still needed to confirm the new price and current authorization.
Investigate repeating card activity
How to Find Recurring Charges on Credit Card Statements
Recurring-charge detection produces candidates, not confirmed subscriptions. Compare several complete cycles and verify the service before acting.
How to Decode Credit Card Transaction Descriptions
A descriptor is a compact routing label, not a receipt. Decode its parts while keeping facts and inferences separate.
How to Categorize Credit Card Transactions Consistently
A useful category describes the review purpose while the original statement row remains untouched and every uncertain purchase stays open for verification.
See how candidates earn a review flag
Descriptor evidence, direction, cadence, amount behavior, history, and exceptions are assessed together.