Overview

After receiving an alert by webhook, your application returns a status to Rapid with the result of its analysis:

• Ethoca (Mastercard): mandatory within 24h. The answer goes back to Ethoca and can prevent the dispute from becoming a chargeback.
• Verifi RDR (Visa): optional. The refund was already made automatically; the status is only for your internal organization.

Summary flow

1. Your application receives the alert by webhook
2. You analyze the transaction in your system
3. You call PATCH /chargeback-alert/alerts/:id/status with one of the three valid statuses
4. Rapid processes and stores it and (for Ethoca) forwards it to the provider

Alternatively, you can update the status directly in the Rapid dashboard (useful for manual operations).

Authentication

The callback uses Basic Auth with client_id/client_secret. See Authentication.

Valid statuses

There are three: notfound, account_suspended and other. What each one means, the deadlines for each card network and the allowed transitions are in Rules and deadlines.

List alerts

If your integration needs to look up alerts (e.g. confirm whether an alert with a given provider_alert_id arrived, or page through history), use the listing endpoint:

GET /api/v1/chargeback-alert/alerts

It accepts filters by status, provider_alert_id, date range, BIN and card last digits. Useful when you only have the provider’s ID (Ethoca/Verifi) and need to find Rapid’s internal ID to update the status.

Next steps

• List alerts: list alerts with filters (including search by your provider_alert_id).
• Update status: full spec of the callback endpoint.