agency-payments-billing-engineer

Design idempotent payment systems and subscription billing architectures for payment service providers.

Updated Jul 24, 2026

Search Tags:#reconciliation #billing #payments #stripe #webhooks #idempotency #pci-compliance

Ready to run

npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill agency-payments-billing-engineer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agency-payments-billing-engineer
Source: https://github.com/imMamdouhaboammar/kaku-chatgpt-harness/tree/main/.agents/skills/engineering-payments-billing-engineer
Command: npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill agency-payments-billing-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the high-stakes challenge of building payment integrations that are prone to duplicate charges, silent failures, and complex PCI compliance requirements.

Core Features & Use Cases

Idempotent Payment Flows: Ensures every money mutation is safe to retry, preventing double-charging.
Webhook Reliability: Implements signature verification, event deduplication, and out-of-order processing for PSP webhooks.
Financial Reconciliation: Automates the matching of processor payouts against internal ledgers to detect drift.
Use Case: Use this to design a Stripe integration that handles subscription lifecycles and automated dunning without ever touching raw card data.

Quick Start

Use the agency-payments-billing-engineer skill to design an idempotent payment flow for a new subscription service.

Frequently Asked Questions about agency-payments-billing-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent duplicate charges when building idempotent payment flows?▼

Idempotent payment flows ensure every money mutation is safe to retry, preventing double-charging. They use high-reliability state machine transitions to manage payment lifecycles and test failure paths, guaranteeing duplicate webhook deliveries do not trigger duplicate charges.

How do I handle Stripe webhook reliability and out-of-order processing?▼

Stripe webhook reliability is handled by implementing signature verification, event deduplication, and out-of-order processing. This ensures webhook consumption accurately tracks payment lifecycles even when network delays cause events to arrive out of sequence.

What is the best way to automate financial reconciliation against internal ledgers?▼

Automated financial reconciliation matches processor payouts against internal ledgers to detect drift. The best way to automate this is by designing systems that continuously compare transaction records, identifying discrepancies between processor reports and your internal financial state.

Can I build a subscription billing architecture without touching raw card data for PCI compliance?▼

Yes, you can build a subscription billing architecture without touching raw card data for PCI compliance. By designing integrations that manage subscription lifecycles and automated dunning through tokenization, you effectively reduce your PCI compliance scope.

Why does my payment system experience silent failures during webhook consumption?▼

Silent failures during webhook consumption occur when signature verification and event deduplication are not implemented. Without these reliability measures and out-of-order processing logic, your payment system cannot accurately track state machine transitions.

Does this payment integration approach support automated dunning for subscription lifecycles?▼

Yes, this approach supports automated dunning for subscription lifecycles. It designs robust subscription billing architectures that manage complex financial workflows, ensuring failed recurring payments are retried safely without risking double-charges.