circle-webhooks

A guide for receiving and checking Circle Payments Network v2 notifications, which are messages sent to your server when payment-related events happen.

In plain words
What is it for?
It helps build webhook handlers for payment, transaction, and request-for-information events, retrieve and cache Circle's public signing keys, and troubleshoot verification failures.
Why use it?
It explains Circle's ECDSA signature checks, so your server can tell genuine notifications from altered or forged requests.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/hookdeck/webhook-skills/circle-webhooks
Any agent
npx skills add hookdeck/webhook-skills --skill circle-webhooks
Clone the repo
git clone --depth 1 https://github.com/hookdeck/webhook-skills

Made for: Claude Code, Codex.

Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,079 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00067 $0.02079
Opus 5 $0.00034 $0.01040
Sonnet 5 $0.00013 $0.00416
Haiku 4.5 $0.00007 $0.00208

Measured 2d ago against content hash 4661e432aa5c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

circle-webhooks scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

The scan reads SKILL.md. This mod also ships 7 executable files (examples/express/src/index.js, examples/express/test/webhook.test.js, examples/fastapi/main.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/circle-webhooks/SKILL.md · 172 lines

How it starts

The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Circle Webhooks

When to Use This Skill

  • How do I receive Circle webhooks?
  • How do I verify Circle webhook signatures (ECDSA / X-Circle-Signature)?
  • How do I fetch and cache the Circle notification public key by X-Circle-Key-Id?
  • How do I handle cpn.payment.*, cpn.transaction.*, or cpn.rfi.* notifications?
  • Why is my Circle webhook signature verification failing?

How Circle Webhooks Differ From Most Providers

Circle's v2 notifications are signed with an asymmetric ECDSA key — not HMAC, and not the Standard Webhooks spec. Each POST carries two headers:

Header Purpose
X-Circle-Signature Base64-encoded ECDSA (ECDSA_SHA_256) signature of the raw body
X-Circle-Key-Id UUID of the public key that signed the notification

You verify by fetching the matching public key from Circle's API (GET /v2/cpn/notifications/publicKey/{keyId}, returns a base64 DER/SPKI key), then verifying the signature over the raw request body with ECDSA-SHA256. The public key for a keyId is static — cache it by keyId to avoid an API call per event.

Two more Circle specifics:

  • HEAD validation. On subscription create/update Circle validates your endpoint with a HEAD request (no subscribe-URL handshake). Return 200 to HEAD as well as POST.
  • Product scope. This skill covers Circle Payments Network (CPN) v2 notifications, which use a notificationType body field carrying cpn.* event strings (cpn.payment.completed, cpn.transaction.broadcasted, cpn.rfi.approved, …). Circle Mint / Core API (v1) is a separate product with a different notification scheme — this skill does not cover it.

Verification (core)

Circle has no webhook-verify SDK helper, so verify manually. Node.js:

const { createPublicKey, createVerify } = require('crypto');
const publicKeyCache = new Map(); // keyId -> KeyObject (public keys are static)

async function getPublicKey(keyId) {
  if (publicKeyCache.has(keyId)) return publicKeyCache.get(keyId);
  const res = await fetch(
    `${process.env.CIRCLE_API_BASE_URL}/v2/cpn/notifications/publicKey/${keyId}`,
    { headers: { Authorization: `Bearer ${process.env.CIRCLE_API_KEY}` } }
  );
  const { data } = await res.json();
  const key = createPublicKey({
    key: Buffer.from(data.publicKey, 'base64'), // base64 DER (SPKI)
    format: 'der',
    type: 'spki',
  });
  publicKeyCache.set(keyId, key);
  return key;
}

async function verifyCircleWebhook(headers, rawBody) {
  const signature = headers['x-circle-signature'];
  const keyId = headers['x-circle-key-id'];
  if (!signature || !keyId) return false;
  const publicKey = await getPublicKey(keyId).catch(() => null);
  if (!publicKey) return false;
  const verifier = createVerify('SHA256');
  verifier.update(rawBody); // raw bytes, not parsed JSON
  verifier.end();
  try {
    return verifier.verify(publicKey, signature, 'base64');
  } catch {
    return false;
  }
}

Read the full file on GitHub · 172 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 172 lines · 67 tokens per session scan A 4661e432aa5c

Subscribe to this mod's changes

circle-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 6d ago), licensed MIT. It adds 67 tokens to every session and 2,079 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

wiki

Rebuild a flow-first project wiki using the mimirs wiki MCP tool. Use when the user asks to generate, rebuild, refresh, or write the wiki for a codebase.

TheWinci/mimirs · 38 tokens

scout

Research the web for solutions, competitors, alternatives, or prior art for a decision facing this project — then store the findings in project memory so they survive the session. Use when choosing a library or approach, comparing tools, checking what others do, or evaluating whether to build vs adopt.

TheWinci/mimirs · 60 tokens

plan

Design an implementation plan before writing code — where the change lands, what it will touch, what could break, and the steps in order. Use when asked to plan a feature, scope a change, or figure out how to approach an edit before making it. To assess a change that already exists (a diff, refactor, or rename), use…

TheWinci/mimirs · 75 tokens

research

Answer a hard, open-ended question about how the project works or is built by synthesizing every source — code, structure, git history, prior decisions, discussion, caveats — and verifying each claim against the source. Use for deep cross-cutting questions that span more than one area. Narrower siblings — a single…

TheWinci/mimirs · 88 tokens

explore

Build an accurate mental model of an unfamiliar codebase, feature, or area before changing it — where it lives, how it connects, what it does, and why. Use when asked how something works, where something is, when onboarding to a repo, or before editing code you don't know. For a cross-cutting question that needs…

TheWinci/mimirs · 79 tokens

handoff

Wrap up a work session so the next session (or another agent) can pick up cleanly — what was done, what's in flight, what to watch out for. Use when ending a session, switching tasks, or asked to hand off, wrap up, or save state for later.

TheWinci/mimirs · 61 tokens