FAQ

How to Handle a Pre-Dispute Alert

A step-by-step guide to reviewing and actioning a pre-dispute alert

Paula Ann Tahanlangit
Paula Ann Tahanlangit
Product Operations Associate
Published November 17, 2026
6 min read
Updated November 17, 2026

Handling Chargeblast Pre-dispute Alert: From Receipt to Resolution

A pre-dispute alert notifies you when a cardholder contacts their bank to question a transaction before filing a formal chargeback. Networks' programs such as Ethoca and Verifi (CDRN/RDR) send these alerts to Chargeblast, allowing you to review and take action on potential disputes from one centralized dashboard.

You typically have a window of about 24–48 hours to respond, though the exact timing varies by issuer and alert type. Treat every alert as urgent. The faster you match and act, the better your odds of stopping the chargeback before it posts.

The path in one line: Alert received → Transaction identified → Transaction reviewed → Refund processed (if appropriate) → Alert resolved or declined

Step 1: Open and Review the Alert

Start in the Alerts Overview of the dashboard. For each new alert, review:

  • Alert ID
  • Transaction amount and date
  • Alert type and provider (Ethoca, CDRN, RDR)
  • Card and issuer information
  • Current status

Your only goal here is to gather enough detail to go find the transaction it refers to.

Step 2: Find the Matching Transaction

Locate the corresponding order in your store or payment processor, then confirm it's the right one by comparing:

  • Amount, currency, transaction date
  • Payment method and card brand (including last 4 digits of the card)
  • Issuing bank
  • Auth code if available
  • Transaction/Order ID and descriptor

No match on the first pass? Try searching a few days before or after the transaction date. The timing may be slightly different between systems.

Step 3: Decide What the Transaction Needs

Transaction statusAction
Still refundableMatch the alert details, process the refund, then resolve the alert
Already refunded
Confirm the refund date (never issue a second one), then decline the alert
Already chargebackConfirm the chargeback date and decline with the correct reason code
Canceled, failed, blocked, or voidedNo refund needed — decline with the correct reason code

Step 4: Resolve or Decline

Resolve — the alert is fully handled, typically because a refund went through.

Decline — the alert doesn't need or qualify for a refund. Choose the closest reason:

ReasonWhen to use it
Already RefundedThe transaction has already refunded
Already a ChargebackAlready in the chargeback process
Cannot Find TransactionNo match after a full search
Not My TransactionDescriptor points to another merchant
Transaction CancelledNever successfully processed
3DSFailed 3D Secure authentication
GeneralNone of the above fits or not sure which one to select

Two Situations Worth Slowing Down For

Duplicate alerts — the same transaction can generate more than one alert. Compare the details. If they're related, act one of them and decline the other. Still not sure? Send both Alert IDs to the Chargeblast team.

Can't find the transaction — before declining as Cannot Find Transaction, re-check the amount, date, currency, payment method/card details, a wider date range, and that you're in the right store or processor. Still nothing? Send the Alert ID and whatever you have to the Chargeblast team.

Best Practices

  • Act quickly — speed is your best lever against escalation.
  • Verify the match before refunding.
  • Never refund twice — check for an existing refund first.
  • Read the transaction, not just the alert — the alert tells you why the customer is concerned. The transaction tells you what to do.
  • When in doubt, ask — send to the Chargeblast team the Alert ID, order/payment ID, and a screenshot if you have one.

Tags

pre-diputealertchargeback

Was this article helpful?

Help us improve our documentation