agency-payments-billing-engineer

Architect idempotent Stripe payment flows with webhook verification and subscription billing state machines.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/rajyeole6/AI-RECRUITER --skill agency-payments-billing-engineer-rajyeole6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-payments-billing-engineer
Source: https://github.com/rajyeole6/AI-RECRUITER/tree/main/.agents/skills/engineering-payments-billing-engineer
Command: npx skills add https://github.com/rajyeole6/AI-RECRUITER --skill agency-payments-billing-engineer-rajyeole6

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires stripe.

What problem does it solve?

This Skill addresses the high-risk complexity of building payment systems, preventing common failures like double-charging, silent data loss, and PCI compliance violations.

Core Features & Use Cases

  • Idempotent Payment Flows: Ensures every transaction is safely retryable and auditable using business-derived keys.
  • Webhook Reliability: Implements signature verification, event deduplication, and out-of-order processing to ensure the system remains the source of truth.
  • Subscription Lifecycle Management: Models complex billing states like dunning, proration, and upgrades as explicit state machines.
  • Use Case: A developer can use this Skill to design a Stripe integration that handles 3DS challenges, manages subscription dunning, and reconciles daily payouts against internal ledgers.

Quick Start

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

Frequently Asked Questions about agency-payments-billing-engineer

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

FAQPage Schema
How does webhook event deduplication work for Stripe subscription billing?

Stripe webhook reliability requires signature verification, event deduplication, and out-of-order processing. Implementing these mechanisms ensures your system remains the source of truth and prevents silent data loss during event delivery.

How do I reconcile Stripe payouts against internal ledgers to ensure zero-drift accuracy?

Managing subscription billing states like dunning and proration is best achieved by modeling them as explicit state machines. This method accurately tracks complex lifecycle events including upgrades, downgrades, and failed payment retries.

Do I need tokenization to maintain PCI compliance when integrating Stripe payments?

Reconciling Stripe payouts against internal ledgers ensures zero-drift accuracy by matching daily payout reports with internal transaction records. This financial reconciliation process identifies and resolves discrepancies between the payment processor and your database.

Does this approach handle 3DS challenges and out-of-order webhook processing for SaaS platforms?

Tokenization is required to maintain PCI compliance by minimizing your security scope when integrating Stripe payments. Utilizing tokenization and hosted fields ensures sensitive card data never touches your servers directly.

Does this approach handle 3DS challenges and out-of-order webhook processing for SaaS platforms?

This approach handles 3DS challenges and out-of-order webhook processing for SaaS platforms by architecting secure payment systems. It manages the full lifecycle of subscription billing and webhook events to ensure consistent state synchronization.