Prevention alert insights
Prevent chargebacks and improve customer experience with real-time tools
Solidgate’s alert helps to address disputes efficiently by notifying merchants at various stages of the transaction lifecycle.
Pre-dispute benefits
Pre-dispute advantages are a key aspect of Solidgate’s chargeback prevention services. These services allow merchants to address disputes at the pre-dispute stage, thereby not affecting their credit and debit portfolio dispute ratios.
- Lowered dispute ratios
Merchants can lower their dispute ratios by resolving pre-disputes with credit through Solidgate. This is particularly beneficial for merchants with high dispute ratios, as it does not impact Visa’s dispute ratio. - Reduced operational requirements
Optimizing dispute resolution processes, especially for disputes with low recovery rates, leads to fewer operational demands. This streamlining effect significantly reduces the workload and resources required to manage disputes. - Eliminate over-refunding
Pre-disputes resolved through Solidgate are not eligible for future disputes, eliminating the possibility of over-refunding. - Increased dispute visibility
Solidgate provides access to adaptable reports tailored to seller reconciliation needs. This feature enhances dispute visibility, allowing merchants to better understand and manage their dispute landscape.
By resolving disputes before they progress to the chargeback stage, merchants not only avoid revenue loss from chargebacks but also maintain favorable standing with credit and debit card issuers.
PayPal and Solidgate alerts
PayPal pre-chargeback alerts differ from Solidgate PayPal alerts in enrollment, coverage, location, and resolution. Compare how each solution manages these factors to reduce chargebacks, streamline refunds, and protect revenue.
| PayPal | Solidgate | |
|---|---|---|
| Turn on | Default by PayPal | Enrollment by Solidgate |
| Enrollment information | — | PayPal Merchant ID PayPal Descriptor |
| Coverage | Limited coverage, in most cases, helps to control
Guide Chargeback rate = total count of chargebacks (current month) / total count of sales (current month). CB rates on Mastercard (1.5% threshold) | Wide coverage (up to 99%), resolves CB issues for Visa (0.9% threshold) |
| Location | Hub > Payments > APMs > Disputes Dispute channel: ALERT Lifecycle stage: CHARGEBACK Success status: Resolved | Hub > Fraud prevention > Alerts list Payment method: PayPal Alert type: Resolved |
| Resolution | 20-hour window to issue refunds | Instant resolution with automated filters |
Alert types
| Value | Definition |
|---|---|
| inquiry | Solidgate sends you inquiry requests initiated by the issuing bank, and returns additional merchant data to the issuer when your available transaction data is matched. |
| init-refund | Solidgate informs the merchant and processes refunds to prevent chargebacks. These transactions include a specific refund Guide Gain a better understanding of chargeback nature and manage them effectively. reason code. |
| resolved | Solidgate alerts merchants when a dispute is resolved. The transaction amount is automatically credited to the cardholder, thus preventing a chargeback. It is important to note that the transaction status remains success because the refund occurs at the Guide Manage chargebacks effectively to minimize losses and protect your business. chargeback flow level. |
| prevented | Solidgate sends notifications to merchants indicating successful prevention of a dispute, which originates from the initial inquiry . |
Alert outcome
| Outcome type | Description |
|---|---|
| reversed | The transaction has been refunded following the alert. This outcome occurs when an alert is successfully matched with a successful sale transaction, leading to a refund of the transaction. |
| previously-reversed | The transaction has been refunded before the alert. This outcome is determined when the transaction has already been refunded prior to the alert. |
| duplicate | The transaction has been refunded due to a duplicate alert. This outcome occurs when the alert is matched with a previously refunded transaction due to an alert received earlier. |
| decline | The related transaction was not successful. This occurs when the transaction was declined before the alert. |
| error | The processing error has occurred requiring additional communication. |
| reverse-error | Unable to process a refund. This outcome occurs when an attempt to refund has failed due to a decline by the bank. |
| not-found | The transaction has not been found. This outcome occurs when an alert cannot be matched with any existing transaction. |
| acknowledged | The default response for the alert is that no action is required with the transaction. |
| pending | A temporary status that allows for a response at a later time, recommended within 24 hours. |
| shipped | This outcome applies to physical goods that have already been shipped. |
Looking for help? Contact us
Stay informed with Changelog