Agent Plugins Marketplace
← All plugins

fintech-payments-engineering

v0.3.4

Fintech & payments-engineering team — agents (payments-architect, payments-integration-engineer, billing-subscriptions-engineer, payments-pci-compliance-advisor) for building payment + billing systems that don't lose or duplicate money: payment-flow architecture (PSP choice, money-as-integer, the double-entry ledger, reconciliation), payment integration (Stripe-style intents, idempotency keys, webhook verification + idempotent handling, 3DS/SCA, retries/dunning), subscription & usage billing (plans, proration, metering, invoicing, revenue events), and PCI-DSS scope minimization (tokenization, never touch raw PAN, SAQ-A posture). The ENGINEERING — accounting/GL routes to finance, financial regulation to regulatory-compliance, security verdicts to ravenclaude-core. skills, a decision-tree knowledge bank (charge-flow + PCI-scope trees + a dated 2026 map), best-practices, templates, commands, an advisory hook. Requires ravenclaude-core@>=0.7.0.

Claude Code5 Skills

By Matt CorbettLicense: MIT7 GitHub starsUpdated last week

Directory evidence

Runtimes
Claude Code
Parsed components
5 skill or MCP entries
Source updated
Sep 15, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install fintech-payments-engineering for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install fintech-payments-engineering@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/mcorbett51090/RavenClaude

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/fintech-payments-engineering/.

Plugin files

plugins/fintech-payments-engineering/
├── .claude-plugin/plugin.json
├── skills/payment-flow-architecture/SKILL.md
├── skills/payment-reconciliation/SKILL.md
├── skills/pci-scope-minimization/SKILL.md
├── skills/psp-integration/SKILL.md
└── skills/subscription-billing/SKILL.md

Included Skills5

payment-flow-architectureskills/payment-flow-architecture/SKILL.md

Architect money-safe payments: represent money as integer minor units + currency (never floats), keep a double-entry append-only ledger as source of truth (the PSP is an integration you reconcile against), design a money-event model, and reconcile continuously.

payment-reconciliationskills/payment-reconciliation/SKILL.md

Step-by-step playbook for reconciling your internal double-entry ledger against the PSP's payout and transaction reports — identifying discrepancies, classifying them, and closing the books with confidence.

pci-scope-minimizationskills/pci-scope-minimization/SKILL.md

Minimize PCI-DSS scope (engineering posture): use PSP client-side tokenization so the raw PAN never touches your servers (SAQ-A), reduce scope ruthlessly, log money operations for audit without ever logging card data, and route attestation/regulation/verdict out.

psp-integrationskills/psp-integration/SKILL.md

Integrate a PSP correctly: idempotency key on every money operation (charge/refund/payout), verify webhook signatures and handle them idempotently + out-of-order, model the charge state machine explicitly, and handle 3DS/SCA and hard-vs-soft declines.

subscription-billingskills/subscription-billing/SKILL.md

Build subscription/usage billing: model plans and prorate mid-cycle changes correctly, meter usage idempotently, run a reliable recoverable billing-cycle job, recover failed payments with smart dunning, and emit clean revenue events for finance.

Plugin manifests1

plugins/fintech-payments-engineering/.claude-plugin/plugin.json
{
  "name": "fintech-payments-engineering",
  "version": "0.3.4",
  "description": "Fintech & payments-engineering team — agents (payments-architect, payments-integration-engineer, billing-subscriptions-engineer, payments-pci-compliance-advisor) for building payment + billing systems that don't lose or duplicate money: payment-flow architecture (PSP choice, money-as-integer, the double-entry ledger, reconciliation), payment integration (Stripe-style intents, idempotency keys, webhook verification + idempotent handling, 3DS/SCA, retries/dunning), subscription & usage billing (plans, proration, metering, invoicing, revenue events), and PCI-DSS scope minimization (tokenization, never touch raw PAN, SAQ-A posture). The ENGINEERING — accounting/GL routes to finance, financial regulation to regulatory-compliance, security verdicts to ravenclaude-core. skills, a decision-tree knowledge bank (charge-flow + PCI-scope trees + a dated 2026 map), best-practices, templates, commands, an advisory hook. Requires ravenclaude-core@>=0.7.0.",
  "author": {
    "name": "Matt Corbett"
  },
  "homepage": "https://github.com/mcorbett51090/RavenClaude",
  "license": "MIT",
  "keywords": [
    "payments",
    "fintech",
    "stripe",
    "billing",
    "subscriptions",
    "pci-dss",
    "idempotency",
    "webhooks",
    "ledger",
    "double-entry",
    "reconciliation",
    "3ds",
    "sca",
    "tokenization",
    "dunning",
    "proration"
  ],
  "requires": {
    "plugins": [
      "ravenclaude-core@>=0.7.0"
    ]
  }
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[fintech-payments-engineering on Agent Plugins Marketplace](https://pluginsmp.com/plugins/fintech-payments-engineering)