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.

Matching descriptions alone do not establish a recurring candidate.DescriptionDirectionCadenceAmount behaviorHistory

Find recurring charge candidates

Multiple statements · pattern review

Locate candidates for repeating paymentsThe output covers recurring debit text, observed timing, value patterns, supporting entries, and confidence.

Temporary private workspace: This recurring-payment review expires in 30 minutes and cannot be indexed by search engines. Before acting, use an official source to check billing status and merchant identity. See plans and usage allowances.

Transactions compared across merchants, values, and timing to flag possible recurring payments

How one candidate appears

Three fictional rows show a near-monthly cadence and a later price change, which still requires independent confirmation.

$14.9931 days to next
$14.9930 days to next
$16.49Amount changed

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

See how candidates earn a review flag

Descriptor evidence, direction, cadence, amount behavior, history, and exceptions are assessed together.

Review the methodology