Ext Ops Panel
Open dashboard
Comparison

paystack-webhooks vs sumup

paystack-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). sumup is a plugin bundle for AI coding tools published by sumup. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-official). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacepaystack-webhookssumup
Community marketplace hookdeck/webhook-skills Listed
Version: not stated
Forks (GitHub): 16
Stars (GitHub): 92
Not marked · First seen
Not listed
Claude Code: claude-plugins-official Not listed Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 5
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

paystack-webhooks vs sumup
Factpaystack-webhookssumup
Marketplaces that list it11
Stars (GitHub) (differs)92 (better)5 (worse)
Forks (GitHub) (differs)16 (better)1 (worse)
Last release (differs)Not published2026-10-16
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.sumup.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not published7
Licence (differs)MITNot stated
Repository (differs)github.com/hookdeck/webhook-skillsgithub.com/sumup/sumup-skills
Changes in the last 7 days (differs)23
First seen (differs)2026-10-212026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago, requires a key

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

paystack-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify Paystack webhooks. Use when setting up Paystack webhook handlers, debugging x-paystack-signature verification, or handling payment events like charge.success, transfer.success, transfer.failed, refund.processed, subscription.create, or invoice.payment_failed.

sumup

In its own words, on Claude Code: claude-plugins-official:

SumUp payment integrations across terminal and online checkout flows. Build Android and iOS POS apps with SumUp card readers, online checkout with server SDKs and the checkout widget, and control card readers remotely via Cloud API.

How to run each

paystack-webhooks As a Claude Code plugin

Claude Code
/plugin marketplace add hookdeck/webhook-skills
/plugin install paystack-webhooks@webhook-skills

sumup As a Claude Code plugin

Claude Code
/plugin install sumup@claude-plugins-official

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only sumup has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: paystack-webhooks · What it can do: sumup · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built