Integrations
Verified inbound webhooks for your stack.
Charon Gate verifies signatures natively for the providers below — exactly the way each one prescribes — and applies the same retry, DLQ, and replay machinery uniformly. Anything else uses the generic HMAC verifier.
Stripe
Charon Gate sits between Stripe and your application: it captures every Stripe webhook, verifies the signature, retries failed deliveries with exponential backoff, holds exhausted events in a dead-letter queue, and lets you replay any event with one click — so a single deploy outage doesn't lose payments_intent.
Read more →
GitHub
Charon Gate is a reliable proxy in front of your GitHub webhook destination.
Read more →
Shopify
Charon Gate captures Shopify webhooks the moment they leave Shopify's edge: HMAC verification on X-Shopify-Hmac-Sha256, dead-letter queue when your destination is offline, and one-click replay so you don't lose orders/create or app/uninstalled when your handler is being deployed.
Read more →
Clerk
Charon Gate captures Clerk webhooks (Svix-signed) the moment they're emitted: signature verification on Svix-Id / Svix-Timestamp / Svix-Signature, dead-letter queue when your destination is mid-deploy, and replay so you don't drop user.
Read more →
Resend
Charon Gate adds reliability and replay to Resend's email-event webhooks.
Read more →
Custom HMAC
Need to ferry webhooks from a provider Charon doesn't natively support? The generic provider type accepts any HMAC-signed webhook (X-Charon-Signature, X-Webhook-Signature, X-Signature) and the same DLQ, retry, and replay machinery applies — no custom code needed.
Read more →
Provider not listed? Use the generic HMAC endpoint — same DLQ, replay, and retry behaviour, you bring your own signing secret. Or ask us to add first-party support.
Roadmap — native verifiers in flight
These providers work today through the generic HMAC endpoint. Native verifiers are on the roadmap so signature handling matches each provider’s exact spec. Want one prioritised? [email protected].