forge-payments
Skill2 starsChanged 6 days agoMITView on GitHub
Playbook for payments and billing: Stripe, Mollie, refunds (gebruik bij betalingen).
- Reads credentials
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- ForgeyClap/claude-forgeedited, first seen Oct 11, 2026
- is-bo/fullstack-forge-skilltheir own version, first seen Aug 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- ForgeyClap/claude-forge★ 236% same
Wrote their own version · 1
- is-bo/fullstack-forge-skill★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository99 other files it gives its agents.
- docs/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brainstormingSkill
- claude-md-improverSkill
- dispatching-parallel-agentsSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- forge-a11ySkill
- forge-agent-reportSkill
- forge-agentSkill
- forge-apiSkill
- forge-authSkill
- forge-autoresearchSkill
- forge-botsSkill
- forge-brainstormSkill
- forge-cliSkill
- forge-cmsSkill
- forge-code-reviewSkill
- forge-contextSkill
- forge-councilSkill
- forge-craftSkill
- forge-databaseSkill
- forge-dataSkill
- forge-debugSkill
- forge-deeplearnSkill
- forge-devopsSkill
- forge-docdriftSkill
- forge-doctorSkill
- forge-ecc-adapterSkill
- forge-ecommerceSkill
- forge-electronSkill
- forge-extensionSkill
- forge-figmaSkill
- forge-fullstackSkill
- forge-gameSkill
- forge-graded-verifySkill
- forge-guardianSkill
- forge-heartbeatSkill
- forge-i18n-docsSkill
- forge-intakeSkill
- forge-integrationSkill
- forge-long-form-writingSkill
- forge-mcp-clientsSkill
- forge-memorySkill
- forge-migrationSkill
- forge-mindmapSkill
- forge-mlopsSkill
- forge-mobileSkill
- forge-n8nSkill
- forge-nightshiftSkill
- forge-observabilitySkill
- forge-plan-largeSkill
- forge-prdSkill
- forge-predictionSkill
- forge-projectbrainSkill
- forge-prompt-coachSkill
- forge-qualitySkill
- forge-ragSkill
- forge-registrySkill
- forge-releaseSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use for: payments, checkout and billing: tokenized capture, minor-units money, idempotent charges, verified webhooks.
- Very specific: line 39
No raw PAN/CVV in code, logs, DB, or memory (grep the diff for card-shaped literals + cardNumber/cvv/pan).
- Very specific: line 41
Every charge/refund call sends an Idempotency-Key.
- Very specific: line 42
Every webhook verifies the signature on the raw body, dedupes on event.id, returns 2xx before heavy work, and is safe under …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Forge playbook — Payments / checkout / billing
When to use
- Use for: payments, checkout and billing: tokenized capture, minor-units money, idempotent charges, verified webhooks.
- Domain framing, team roles and honesty rule:
references/overview.md.
Hard rules (non-negotiable)
- No raw PAN, ever.
- Integer minor units only.
- Idempotency-key per charge (send side).
- Signature-verified webhooks (receive side).
- Test vs live separation.
- Secrets in env +
.env.exampleplaceholders. - Refunds, disputes, and chargebacks handled explicitly.
Full text of every rule: references/hard-rules.md.
Team (conditional)
Lead: integration-boss (or build-boss if payments are one slice of a larger app). Full roster: references/team-and-tools.md.
Skills / commands / MCP
claude-api only if an LLM is in the loop; otherwise gateway SDK docs (Context7 / vendor docs) for exact API + version behavior. Reuse the gateway's official verification library — never hand-roll HMAC. If checkout renders a UI, load forge-website for the checkout page (real content, responsive, a11y). If billing runs through n8n, defer webhook handling to forge-n8n.
Provider references (read the one that applies before writing gateway code): Stripe → references/stripe.md (API choice, fulfil-in-webhook, restricted keys, subscription event set); Mollie → references/mollie.md (triage, fetch-to-verify webhooks, mandates, refund 409 handling). Both add a Forge-authored idempotency section the vendor skills lack.
Fan-out & flow
L2 single gateway + one charge flow; L3 subscriptions + refunds + multi-event webhooks + reconciliation. Parallel: checkout/capture path ∥ webhook receiver ∥ refund/void path (independent once the money model + idempotency schema are fixed). Serial: money model (minor units + currency) → tokenized capture → idempotent charge → signature-verified webhook → state machine (auth→capture→refund) → reconciliation/audit trail.
Domain gates
- No raw PAN/CVV in code, logs, DB, or memory (grep the diff for card-shaped literals +
cardNumber/cvv/pan). - Money is integer minor units + currency everywhere; no float money math.
- Every charge/refund call sends an
Idempotency-Key; keys are persisted. - Every webhook verifies the signature on the raw body, dedupes on
event.id, returns2xxbefore heavy work, and is safe under duplicate/out-of-order delivery. - Auth / capture / void / full + partial refund each handled explicitly with a clear failure path (timeout + bounded retry, never a silent failure).
- SCA / 3D Secure supported where the market/regulator requires it (EU/EEA cards).
- Payment-page script integrity (SAQ A r1 / reqs 6.4.3 + 11.6.1): the checkout page either (a) carries the processor's written confirmation that its embedded solution self-protects against script tampering, or (b) applies script-management + tamper/change-detection on the page that includes the iframe. Record which path is used.
- Sandbox + test-card scenarios exercised (success, decline, 3DS challenge, duplicate webhook) before anything is called production-ready.
Ship-readiness (unique)
Evidence checklist before handoff: references/ship-readiness.md.
Safety, approval and honesty
- Approval / safety: no live charge and no live-key touch without explicit owner approval.
- Approval / safety: gateway and webhook signing secrets in env only.
- Honest failure: never claim PCI compliance or a working live charge that was not verified in the sandbox; if Codex did not run, say so.
- Untrusted content: see
references/untrusted-content.md. - Shared gates for every playbook (honesty, owner approval, secrets, reviews):
.claude/docs/forge-reference/playbook-template.md.
References
references/overview.md— domain framing paragraph(s) from under the title.references/hard-rules.md— full text of every hard rule.references/team-and-tools.md— full team roster, skills, commands, MCP and opt-in runtimes.references/ship-readiness.md— full ship-readiness evidence checklist.references/untrusted-content.md— Untrusted-content note.references/stripe.md— Stripe specifics (adapted from stripe/ai, MIT; notice inLICENSE).references/mollie.md— Mollie specifics (adapted from mollie/ai, MIT; notice inLICENSE)..claude/skills/forge-integration/references/webhooks.md— the shared Forge webhook rule set (raw-body verify, dedupe with a uniqueness guarantee, persist before2xx, retries and dead letter); the payment rules above stay stricter where they differ.
Provenance
only a link to the shared webhook section was added here; no external text. That section's own provenance (hookdeck/webhook-skills, pinned SHA 0aa8c48e3e1c65dc1fa893190006248b92805417, MIT) is inside the linked file.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

