# Billing Payments Specialist

> Payment authorization, settlement, refunds, credits, invoices, financial ledgers, and billing controls. Use when validating or executing product-related financial operations and payment state transitions.

- Skill: `br3eze-code/billing-payments-specialist` (Agent Skill)
- Install (CLI): `npx skillmds@latest add br3eze-code/billing-payments-specialist`
- Raw SKILL.md: https://api.skillmd.com/api/skills/br3eze-code/billing-payments-specialist/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: br3eze-code (https://skillmd.com/u/br3eze-code)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/br3eze-code/billing-payments-specialist

---


# Billing and Payments Specialist

Protect financial correctness and customer trust by separating calculation, authorization, settlement, reconciliation, and refund operations.

## Workflow

1. Validate tenant, customer, order, amount, currency, tax context, payment method, idempotency key, and authority.
2. Recalculate or verify the amount from trusted product and pricing records; never trust client totals.
3. Authorize the payment or credit and record provider response without exposing sensitive payment data.
4. Settle, refund, reverse, or credit only through explicit state transitions and policy gates.
5. Reconcile provider transactions with internal ledger entries and surface mismatches for review.
6. Record immutable activity evidence, redacted provider identifiers, actor, timestamp, and outcome.

## Boundaries

Pricing and Promotions proposes calculations. Orders and Checkout owns order intent. Catalog owns product definitions. Procurement owns supplier commitments. Voucher and Access owns entitlement state. Billing owns the financial ledger and must not silently change operational or network state.

## Controls

Use integer minor units, explicit currencies, idempotency, authorization checks, least-privilege access, redacted logs, retry-safe provider calls, webhook signature validation, replay protection, and reconciliation jobs. Require approval for refunds, credits, manual adjustments, high-value transactions, and exceptions.

Never log raw card data, credentials, voucher secrets, or full payment tokens. Treat provider callbacks as untrusted until authenticated and matched to a known transaction.