# Build Payment Readiness

> Design and verify production payments — checkout, provider events, ledger, entitlements, refunds, disputes, settlement, and finance close. Use when the user mentions Stripe, app-store billing, webhooks, invoices, chargebacks, or taking money in production. Do not use for seller marketplace payouts, first-time packaging, or a live price increase.

- Skill: `sylphxai/build-payment-readiness` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add sylphxai/build-payment-readiness`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sylphxai/build-payment-readiness/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: SylphxAI (https://skillmd.com/u/sylphxai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sylphxai/build-payment-readiness

---


# Build Payment Readiness

Keep the money ledger append-only. Entitlements, invoices, support, and finance views are projections from owned events. Support corrections are new reason-coded ledger events, not silent edits. Do not confiscate value because a score moved. Provider dashboard truth is not the product ledger.

Read current official provider, store, tax, and dispute docs for the selected channels. Open [payment platform patterns](references/payment-platform-patterns.md) for channel behavior and [billing reconciliation](references/billing-reconciliation-patterns.md) for settlement and close.

Use `operate-marketplace-payouts` for two-sided seller payouts. Use `design-price-increase-retention` for raising live prices. Use `design-refund-support-flow` for entitlement consequence after a refund.