Use cases
Where webhook reliability shows up in revenue and ops.
The same primitives - verify, queue, retry, dead-letter, replay - map to different business paths. These are the patterns we see most often after an outage or audit.
Payments
Payments and subscriptions.
Invoice paid, charge failed, subscription renewed - events that must not be processed twice or dropped during deploys.
Payment processors retry aggressively but still stop after their window. If your billing service is down during a deploy, you can miss entitlements or dunning steps. Marevans holds events until billing is healthy, with dedupe on processor event ids so a retry storm does not double-charge.
Typical sources: Stripe, Adyen, PayPal, Braintree. Typical destinations: billing API, ledger, dunning worker, revenue analytics.
match: source: stripe type: invoice.paiddeliver: - billing-entitlements - revenue-warehousededupe: key: payload.id window: 72hCommerce
E-commerce order flow.
Orders, fulfillments, and refunds fan out to inventory, WMS, and support - without one slow service blocking the rest.
Shopify and similar platforms emit high-volume, bursty webhooks. Marevans absorbs spikes, routes orders/paid to fulfillment and refunds/create to finance, and gives each destination its own timeout and retry budget so a stuck WMS integration does not block customer emails.
During peak sales, queue depth becomes the signal to scale consumers - not a hidden backlog in a single monolith endpoint.
DevTools
Developer workflows and CI.
GitHub, GitLab, and internal hooks that trigger builds, scans, and deployments - with an audit trail.
CI systems care about delivery order less than durability: a workflow_run or push event must survive a brief API outage. Marevans stores the payload, retries the deploy webhook, and lets you replay a range after fixing a misconfigured secret.
Signature verification uses each vendor’s scheme out of the box. Internal hooks can use HMAC with a shared secret stored in SSM Parameter Store.
sources: github: path: /in/github verify: scheme: github secret: ${ssm:/webhooks/github/secret}routes: - match: { source: github, type: workflow_run.completed } deliver: [deploy-orchestrator]CRM
CRM and lifecycle sync.
HubSpot, Salesforce, and marketing tools - keep sales data consistent without polling APIs all day.
CRM webhooks are lower volume but high value: a contact property change should update your data warehouse and trigger sales alerts. Marevans routes property changes to multiple consumers and redacts email or phone fields before storage when policies require it.
When a downstream sync job fails for a week, dead-letter review shows exactly which contacts did not propagate Then replay after the fix instead of running a full re-import.
Start with the webhook that already woke someone up.
Most teams begin with payments or orders, then move internal and CRM sources behind the same gateway once the event log proves its worth.