Webhook Events & Event Types
Core Event Types
To see the events payload, please visit our API reference
Our webhook system currently supports the following core event types:
Chargeback events
1. chargeback.created
chargeback.createdTriggered when a new chargeback is received for the merchant.
This event fires immediately when a new chargeback is received from any of your connected PSPs (Payment Service Providers). The payload includes all available chargeback data at the time of creation.
2. chargeback.updated
chargeback.updatedTriggered when a chargeback is updated.
3. chargeback.status.updated
chargeback.status.updatedTriggered when a chargeback status update is received.
4. chargeback.evidence.submitted
chargeback.evidence.submittedTriggered when evidence is successfully submitted to the PSP.
The payload carries the outcome in status which can be succeeded | failed.
5. chargeback.accepted
chargeback.acceptedTriggered when a chargeback acceptance is successfully confirmed by the PSP.
The payload carries the outcome in status which can be succeeded | failed.
Alert events
6. pre_chargeback_alert.received
pre_chargeback_alert.receivedTriggered when a new pre chargeback alert is received from either CDRN, RDR or Ethoca.
7. pre_chargeback_alert.refund.succeeded
pre_chargeback_alert.refund.succeededTriggered when the linked transaction to a refunded alert was successfully refunded through the PSP.
8. pre_chargeback_alert.refund.failed
pre_chargeback_alert.refund.failedTriggered when a refund alert is failed to be processed.
9. pre_chargeback_alert.transaction_matched
pre_chargeback_alert.transaction_matchedTriggered when an inbound pre-chargeback alert was successfully matched to an underlying transaction.
Opt-in only, gated by an additional event types account configuration done by Justt.
Subscription-related events
10. subscription.cancel_immediately.success
subscription.cancel_immediately.successTriggered when a CRM subscription was successfully cancelled after a refund (e.g. Chargebee or Recurly).
11. subscription.cancel_immediately.failed
subscription.cancel_immediately.failedTriggered when cancelling a CRM subscription failed after a refund (e.g. subscription not found or already cancelled).
The payload carries failureCode and a human-readable failureReason. The refund went through but the cancellation did not, so Justt flags the alert as Action Required for manual follow-up.
Event Filtering
When configuring your webhook endpoint, you can:
- Subscribe to all events - Receive all event types (default behavior)
- Subscribe to specific events - Choose only the events you need to reduce noise
We recommend starting with all events for testing, then filtering to specific event types for production use.
Updated 4 days ago
