Moving money: the payment intent as the durable state machine, idempotency keys scoped to the money operation, authorization versus capture as two liability moments, decline handling that never doubles a charge, webhooks as confirmation, the double-entry ledger behind every balance, dunning and subscription lifecycle states, proration and metered billing, dispute evidence, PCI scope and card boundaries, and the payments record. It never recommends a processor. Use when asking "charge a card", "payment state machine", "idempotency key", "authorization versus capture", "webhook signature verification", "double entry bookkeeping", "trial then charge", "failed renewal", "dunning", "proration", "metered billing", "chargeback evidence", "PCI scope", "why was the customer charged twice". Not for general API design and idempotency (ac-api-design), not for webhook delivery to consumers (ac-webhook-and-async-delivery), not for money representation and rounding (ac-money-arithmetic).
cp -r cryptoskill/skills/exchanges/anoscranel-ac-payments-and-billing-engineering .claude/skills/clawhub install anoscranel-ac-payments-and-billing-engineeringCapabilities below are detected automatically by an open-source scanner that reads the skill's text and scripts (see how this is computed). Not measured means the scanner couldn't make a confident call — it is NOT a green check, and you should treat it as a possible red flag until a human or a stronger scanner has measured it.
read_only Phase 1 single-mode classification — multi-mode breakdown deferred to Phase 2.
We did not find any well-known hosted services in this skill's text or scripts. This does NOT mean the skill is local-only — it might use services we don't yet recognize, or talk to them through code paths our scanner can't reach. A complete dependency list (every package, library, and binary, with integrity hashes) is on the roadmap; today we only show recognized hosts.
No one has audited this skill yet. That is different from “audited and clean” — it just means no professional reviewer (a security firm, the CryptoSkill team, or a verified independent researcher) has signed off on it. There are no audit reports to read. How reviewer levels work →
SKILL.md → SOURCE.md → TRUST.auto.yaml → Browse directory →
Auto-generated by cryptoskill/extract-capabilities/0.3.1 · hosted-service list version 2026-09-06 · how this is computed