FAQ

Troubleshooting Webhook Issues

Common webhook problems and how to resolve them quickly

Virnie Rose Apal
Virnie Rose Apal
Product Operations Specialist
Published January 18, 2024
4 min read
Updated November 17, 2026

Webhooks send alert and deflection events from Chargeblast to an endpoint on your server as they happen

⚠️ Important: If webhook deliveries fail, your system may not receive alert updates in time to act on them

Common Problems

ProblemCauseFix
Missing eventsEndpoints only receive the events they're subscribed to. New endpoints receive alert.created onlyIn Chargeblast, go to Settings → Developer → Configure, open your endpoint, and edit Subscribed events. Select the events you need, then save
externalOrder field is missingalert.created doesn't include this fieldSubscribe to alert.updated. It's sent once an alert is matched to a transaction, so unmatched alerts won't have this field
Signature verification failsThe signature is being checked incorrectlyAsk your developer to remove the v1, prefix from the svix-signature header and verify against the raw request body. See the Webhooks developer docs
Endpoint was disabledDeliveries kept failing, so the endpoint was disabled automatically. You'll receive a "Webhook Endpoint Has Been Disabled" emailResolve the error on your server, then re-enable the endpoint from its actions menu in Settings → Developer → Configure. Resend what was missed using the steps under Testing and resending events

Available Events

AlertsDeflections
alert.createddeflection.created
alert.updateddeflection.updated
alert.refunded
alert.matched
alert.will_expire
alert.within_refund_rules
Webhooks cover alerts and deflections only. There are no dispute or chargeback events.

Checking webhook status

  • All deliveries: In Settings → Developer → Configure, open the Logs tab. Click a message to see its payload, delivery attempts and the response code your server returned
  • A single alert: Open the alert, scroll to Webhook deliveries, and expand a row

Note: An alert's createdAt is when the alert was created, not when the webhook was sent. The Logs tab shows the actual delivery time

Testing and Resending Events

In Chargeblast, go to Settings → Developer → Configure and open your endpoint.

Test your endpoint. Use this to confirm your server can receive events

  1. Open the Testing tab
  2. Click Send Event
  3. Check your server. If the event arrived, your endpoint is working

Resend missed events. Use this to recover events from the last 14 days

  1. Pick the option that matches the problem:
  • Recover Failed Messages: resends deliveries that failed
  • Replay Missing Messages: sends events that were never delivered
  1. Choose a time window
  2. Confirm. Nothing is sent until you do

Resend a single event. Use this to resend one specific message or alert

To resend an existing message:

  1. Open the message
  2. Click Replay

To create a new event for an alert:

  1. Open the alert
  2. Go to Actions → Replay Webhook
  3. Select Emit new alert.created

    Getting Help

    Contact support and include:

    • The affected alert IDs (for example, al_…)
    • The message IDs from your webhook logs (for example, msg_…)

    Tags

    webhookstroubleshootingtechnical

    Was this article helpful?

    Help us improve our documentation