Ac Payments And Billing Engineering

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).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit ee0c8c94d0

Frequently asked questions

npx get-skill add jiayaoqijia/ac-payments-and-billing-engineering