On this page

A claim form receives five times its usual activity in one afternoon. The increase could reflect a successful promotion, delayed customer action, repeated submissions during a service problem or suspected automated activity. The volume alone does not establish which explanation applies to any individual customer.

The first useful comparison is between requests and actual qualifying purchases. A spike in requests can greatly exceed the number of new award obligations. Separating those populations lets the merchant investigate uncertainty while preserving a clear route for genuine buyers and existing rewards.

Compare claim activity with actual qualifying purchases

Choose a bounded review window and record the relevant campaign exposure during that period. Did an approved reminder go out? Did a delivery delay resolve? Did the form appear unresponsive? These facts do not prove that every request is legitimate, but they provide context that a raw traffic chart lacks.

In a hypothetical afternoon, the merchant records 1,200 claim requests. Matching the authorized commercial records identifies 300 requests linked to new qualifying purchases, 700 repeat requests linked to 200 already known purchases and 200 requests without a supported purchase match. The request count is 1,200, but the known purchase relationships tell a more useful story.

Do not count the 700 repeated requests as 700 additional rewards. Also do not assume that the unmatched 200 are fraudulent. Some may contain mistyped references or concern purchases whose evidence has not yet reached the reviewing team. They belong in a separate evidence queue until the relevant facts are established.

Triage group Request count Known purchase context Immediate review objective
New supported purchases 300 300 new purchase relationships in this example Apply normal approved eligibility process
Repeated requests 700 200 already known purchases Identify existing awards and access problems
No supported match yet 200 Purchase relationship unresolved Obtain or verify minimum relevant evidence
Total 1,200 Counts are not equivalent to award obligations Preserve category-specific handling

Record how the matching was established and what remains uncertain. This is a manual triage model, not a claim that any platform automatically performs these classifications.

Separate repeated requests from new obligations

Within the repeated group, inspect whether customers are retrying because the page failed to show confirmation. If the same purchase already has an award or an active claim, route the request to that existing record. Avoid creating value merely because the customer tried again after an unclear response.

For the new-purchase group, preserve the standard review path. A traffic spike should not by itself change the published entitlement. If the team introduces a temporary operational review step, it needs the appropriate authority and should not be communicated as a finding that the affected buyers acted improperly.

For unmatched requests, define the smallest evidence gap. A missing store context, mistyped order reference and purchase outside the campaign period are different issues. The first two may be resolvable data problems; the third requires applying the actual offer condition. Use distinct labels so customer support knows what information can help.

A difficult case is a spike that mixes real purchases with repeated automated-looking requests against those same purchase references. The existence of unusual request activity does not erase the underlying buyer’s possible entitlement. Link the suspicious activity to the affected record while preserving a separate path for the legitimate recipient through the approved access process.

Track financial exposure using confirmed award states, not request volume multiplied by advertised reward value. If a request is only a duplicate contact, it does not create another commercial entitlement. If an award has already been issued, the relevant issue may be access or diversion risk rather than a new funding obligation. The distinctions change who needs to act.

Escalate the affected cases with controlled review

Create a triage board with one owner for each population. The board should show affected references, current stage, evidence gap, potential customer impact and next decision. A security team can investigate suspicious request behavior while reward operations continues to reconcile supported purchase and award relationships.

An escalation might say: “The 14:00–17:00 UTC window contains 200 unmatched requests and concentrated repeated activity against 30 existing purchase references. We need review of request behavior and confirmation of the approved customer recovery route. The 300 separately supported new purchases remain in the normal eligibility queue.” This states the scope without claiming that all traffic is malicious.

Do not instruct support to send every customer the same accusation or denial. A buyer with an existing award needs an explanation relevant to that award. A customer with an incomplete purchase reference needs a targeted request. A confirmed ineligible purchase needs the applicable condition. The communication should follow the case evidence, not the overall incident label.

Record any temporary handling change, its authorized owner and its intended end condition. If additional review was introduced, specify what evidence allows a case to leave that queue. Otherwise a short-lived spike can create a permanent backlog of customers whose status no one revisits.

After the window stabilizes, reconcile the categories to final outcomes. Determine how many requests were repeated contacts, how many supported new awards and how many remained unresolved or received a supported adverse decision. Do not present the initial unmatched count as a final fraud statistic.

The useful result is a contained review with clear commercial boundaries. Request volume becomes an input to investigation, while actual purchases and award states determine what the merchant owes attention to and which team can provide the next authorized action.

Explore which purchase and eligibility records can support investigation of a claim spike.

Explore capabilities

Back to contents

General information only

This guide is general information, not financial, legal, tax or regulatory advice. Eligibility, card availability, permitted use and responsibilities depend on the applicable offer and card terms.