E-commerce Orders, payments and refunds →

Never lose
an order event.

Payments, orders and refunds arrive as webhooks from a handful of providers. Ensue receives them all, checks each one is genuine, drops duplicates and delivers them to every system that needs them.

Get early access Talk to us

shopifyCopy URL

Requests · last 24h12,964

Ensue

Dedupe

key     id
window  3 days
a resend is accepted, not run again

fulfilmentHealthy

Last 12 attemptsp50 182ms

Delivered today6,318

Transform

order_id ← id
total    ← total_price
email    ← customer.email

hubspotHealthy

Last 12 attemptsp50 240ms

Delivered today6,301

Filter

Only orders with total_price over 500, so the channel hears about the big ones.

#ordersHealthy

Last 12 attemptsp50 310ms

Delivered today214

Why Ensue

Every order counts.
So does every webhook.

A missed orders/paid webhook is a customer who paid and never got their order. Ensue sits in front of your services so a deploy or an outage never costs you one.

Verified at the door

Stripe, Shopify and WooCommerce signatures are checked before anything reaches your code.

Duplicates dropped

Providers resend. Ensue keys on the provider’s own event ID, so a refund is processed once.

Accepted while you are down

Events are stored and acknowledged in milliseconds, then delivered when your service is back.

Route on any field

Send big orders to Slack, refunds to finance and everything to the warehouse, with filters on the payload.

Reshape on the way

Transforms turn each provider’s payload into the one shape your fulfilment service expects.

Replay a bad day

Fixed a bug in your order handler? Replay the window it missed, from the dashboard.

In practice

Where order events go.

Fulfilment

Paid orders reach your warehouse system, retried until it confirms.

shopify orders/paid → fulfilment API · retried

Customer records

Payments and refunds update the customer in your CRM.

stripe charge.refunded → hubspot · transform

Big-order alerts

Orders over a threshold ping the team in Slack.

orders/paid where total_price > 500 → slack #orders

Receipts and follow-ups

Order events trigger the right email, once.

order.created → resend · deduped

Build or buy

Your own endpoint
vs. Gateway.

Your own endpoint

Returns 500 during a deploy, and the provider gives up
Signature checks copied for each provider
A resent refund processed twice
Each new system means another webhook to register
“Did that order come in?” answered from logs

Ensue Gateway

Stored and acknowledged even while you are down
One place that verifies every provider
Duplicates dropped by the provider’s event ID
One source, fanned out to every system
A timeline for every event, with each attempt

Built on

The parts of Ensue you’ll use.

GatewayReceive webhooks from any sender, verified, deduped and delivered with retries.Learn more → IntegrationsVerified sources for the tools your team already uses.Learn more → DispatchSend signed, retried webhooks to your own customers with one API call.Learn more →

Keep every order in sync.

Early access opens in waves. Tell us where to reach you and we will be in touch when your spot is ready.

Want to walk through your setup first? Talk to us.

Every order counts.So does every webhook.