Webhook Monitoring for Marketplaces
Buyers complain when something breaks. Sellers just leave, and a missed payout webhook is the fastest way to lose your supply side.
Marketplaces have two customer bases with different tolerances. Buyers complain loudly and give you a chance to fix things. Sellers, particularly good ones, tend not to complain at all. They quietly move their inventory somewhere else.
That asymmetry means seller-side webhook failures deserve tighter monitoring than buyer-side ones, which is the opposite of how most marketplaces allocate attention.
Payouts are the one to watch
A failed payout that nobody notices is a seller who was told they would be paid on Friday and was not. There is no notification from your platform, because the event announcing the failure is precisely the one you dropped.
By the time the seller emails you, they have already been paid late once. By the second time, they are evaluating alternatives.
| Missed event | Who it affects | Their likely response |
|---|---|---|
| payout.failed | One seller | Emails once, then quietly delists |
| account.updated (requirements due) | One seller, mid-onboarding | Abandons signup; you never learn why |
| transfer.failed | One seller | Balance looks wrong, trust drops |
| capability.updated | One seller | Cannot transact, no explanation given |
| order.paid | One buyer and one seller | Buyer emails; seller never ships |
Notice that every row affects one participant. This is what makes marketplace failures so hard to see: nothing shows up in an aggregate graph, because 0.4% of sellers having a problem is a flat line.
Onboarding stalls are pure lost supply
Seller onboarding is a multi-step process spanning your platform and a payment provider's verification flow, and it can stall at any step. A seller whose additional documents were requested by a webhook you never processed sits in a pending state forever.
They will not chase it. They will assume your platform is broken or that they were rejected, and they will go to a competitor. You will never see a ticket, and your funnel will simply show a conversion rate slightly lower than it should be.
Track onboarding as a sequence per seller with a time limit on each step, so a seller stuck at step three for 48 hours becomes an alert rather than a statistic.
Split orders fail partially
An order covering three sellers is three fulfilment obligations, three payouts and three notification paths. A failure affecting one of them leaves the order in a state that is neither complete nor failed.
Aggregate order-completion metrics treat that as a success, because the order was paid and two thirds of it shipped. The buyer experiences one missing item and one seller never gets paid.
Correlate per line item rather than per order. It is more work to instrument and it is the only way this failure becomes visible.
Escrow timing creates dated obligations
If you hold funds until delivery confirmation, you have a set of deadlines running continuously. A confirmation webhook that goes missing means funds held past the point you committed to releasing them, which in some jurisdictions is more than a customer service problem.
Monitor the age of held balances directly, not just the events that should move them. A balance older than your stated release window is evidence something upstream failed, whatever your event log says.
Where to start
Payout events first, onboarding sequences second, order splitting third. That order reflects how quickly each failure costs you supply, which is the constraint marketplaces actually run into.
SensaCat tracks sequences per entity, so a single seller stalled at step three is an alert rather than a rounding error. Start free.