Chargeback alerts
Cardflo's chargeback alert system provides early notification of pending disputes, allowing merchants to take pre-emptive action. This reduces the number of full chargebacks and associated fees, protecting your revenue and merchant account standing.
Act quickly to resolve issues before they escalate.
- Category
- Risk
- Capabilities
- 10
- Available on
- All plans
The overview
Chargeback alerts act as an intermediary notification layer between the card issuer and the merchant, appearing before a formal dispute is finalised through the schemes.
These alerts originate from collaborative networks such as Ethoca and Verifi, which aggregate data from participating issuers when a cardholder initiates a dispute.
In the standard merchant service cycle, a dispute often results in an immediate financial debit and a permanent mark against the merchant ID.
By utilising an alert system, the merchant receives a window, typically lasting twenty-four to seventy-two hours, to issue a full refund to the cardholder. This manual or automated intervention satisfies the cardholder's request and halts the progression of the dispute into a formal chargeback.
This process is critical for maintaining merchant account stability, as it prevents the transaction from contributing to the chargeback-to-sales ratios monitored by acquirers and card schemes like Visa and Mastercard.
How it works
Issuer notification and capture
When a cardholder contacts their issuing bank to dispute a transaction, the issuer assesses if the merchant participates in an alert network.
If so, instead of immediately initiating a retrieval request or chargeback, the issuer logs the incident into the alert system, providing the original transaction details and the reason code.
Alert transmission via API
The alert provider transmits a notification through a gateway or API to the merchant or their payment service provider. This notification includes the Merchant Identification Number, transaction amount, and unique identifiers required to locate the payment.
This communication happens in real time, bypassing the traditional postal or batch-based dispute cycles.
Merchant review and resolution
The merchant receives the data and must decide whether to defend the transaction or issue a refund. Within the designated timeframe, issuing a refund triggers a signal back to the issuer.
This action indicates that the dispute is resolved, preventing the issuer from proceeding with a technical chargeback filing.
Data synchronisation and reconciliation
Once the refund is processed and the alert is closed, the systems update the transaction status. This prevents the administrative fees typically associated with formal disputes.
The merchant then reconciles their internal ledgers to reflect the avoided chargeback, ensuring their risk metrics remain below the thresholds set by card schemes.
Why it matters
Preservation of merchant accounts
Acquirers monitor Chargeback-to-Transaction ratios closely; exceeding specific limits can lead to fines, higher rolling reserves, or termination of the merchant agreement. By resolving disputes at the alert stage, these incidents do not count towards official scheme ratios.
This proactive management ensures that high-volume or high-risk merchants maintain their standing with their acquirer, avoiding the significant operational disruption of losing a primary payment channel.
Reduction in overhead costs
Formal chargebacks carry heavy administrative fees, often ranging from twenty to one hundred pounds per incident, regardless of whether the merchant wins the eventual representment. Alerts allow businesses to bypass these fees by issuing a simple refund.
Furthermore, it reduces the resources required for building complex evidence packages for representment, as many disputes are settled before they reach the stage of formal conflict.
Use cases
Subscription and recurring billing
Merchants specialising in software-as-a-service often face disputes due to forgotten renewals. Alerts allow the merchant to cancel the subscription and refund the cardholder immediately, preventing a dispute from harming their billing MID.
High-growth e-commerce retailers
Rapidly scaling retailers often experience spikes in disputes during peak seasons. Using alerts helps manage these volumes without triggering manual reviews from the acquirer or moving into scheme monitoring programmes.
Digital goods and services
Businesses selling non-tangible assets can use alerts to immediately revoke access to digital content once a dispute is flagged, minimising further loss of service while simultaneously preventing the chargeback fee.
By the numbers
This represents the typical industry decrease in formal chargebacks for merchants who effectively utilise alert networks to pre-emptively refund disputed transactions.
Typical administrative fees per chargeback that are bypassed when a merchant resolves a dispute through the alert phase rather than the formal scheme process.
The industry average percentage of card issuers globally that participate in major alert networks, determining the likelihood of receiving an alert for any given dispute.
Related terms
Talk to our team about a live rollout on your acquiring stack.
What you get with Chargeback alerts
- Integration with global issuer networks including Ethoca and Verifi to maximise dispute coverage.
- Early detection of fraudulent activity before formal claims are submitted by the cardholder.
- Automation of refund triggers to resolve alerts without manual intervention from risk teams.
- Real-time monitoring of chargeback-to-sales ratios to ensure compliance with card scheme rules.
- Detailed reporting on dispute reason codes to help identify recurring operational weaknesses.
- Direct communication with issuing banks to stop the progression of consumer disputes.
- Avoidance of costly representment cycles and the associated administrative burden on staff.
- Protection against friendly fraud by identifying recurring dispute behaviour across different merchants.
- Centralised dashboard to manage alerts from multiple acquirers and merchant identification numbers.
- Scalable notification settings to prioritise high-value alerts based on custom business logic.
A short scoping call, then a written plan for your MIDs.
Questions about Chargeback alerts
What is the difference between a chargeback alert and a retrieval request?
A retrieval request is a formal demand from an issuer for more information regarding a transaction to help a cardholder recognise a charge. It is part of the traditional scheme dispute cycle.
Conversely, a chargeback alert is an informal, early-warning notification provided by third-party networks.
While a retrieval request can still lead to a chargeback if the evidence is insufficient, an alert is designed specifically to allow the merchant to refund the payment and stop the chargeback from ever being filed, thereby protecting their merchant metrics.
Do chargeback alerts guarantee that a dispute will not be filed?
Alerts do not provide an absolute guarantee, as they depend on the cardholder's bank being a member of the alert network. If a cardholder uses a card from a non-participating issuer, the merchant will receive a standard chargeback notification without a prior alert.
However, for issuers within the network, responding to an alert with a refund within the specified time limit generally stops the formal chargeback process. It is a highly effective tool for mitigation but must be part of a broader risk strategy.
How long does a merchant have to respond to an incoming alert?
Response times are strictly governed by the alert provider and generally range from twenty-four to seventy-two hours. This timeframe is significantly shorter than the standard dispute response window.
If the merchant fails to issue a refund or acknowledge the alert within this period, the issuer will proceed to file a formal chargeback.
Therefore, many merchants choose to automate the refund process for alerts to ensure they never miss the deadline due to manual processing delays.
Can I still represent a case if I have already received an alert?
Technically, if you choose not to refund an alert and let it become a chargeback, you can enter the representment phase to defend the transaction. However, the primary purpose of an alert is to avoid the chargeback entirely.
If you have clear evidence that the transaction was legitimate, you might choose to ignore the alert and fight the subsequent chargeback, but you will then incur the chargeback fee and the negative impact on your MID standing regardless of the outcome.
Are there specific business types that benefit most from using these alerts?
Businesses with high transaction volumes, those in high-risk categories, or那些 utilising recurring billing models benefit most. These industries are susceptible to higher dispute rates, and even a small percentage increase can lead to them being placed in scheme monitoring programmes.
For these merchants, the cost of the alert service is typically far lower than the potential losses from increased scheme fees or the risk of merchant account termination.
How does the refund process work when an alert is triggered?
When an alert is received, the merchant initiates a standard refund through their payment gateway or processor. Once the refund is authorised, the merchant or their service provider updates the status in the alert portal using the specific alert ID.
The network then notifies the issuing bank that the funds have been returned, which closes the case on their end and prevents the transaction from escalating into a formal dispute.
Ready for velocity?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.