Billing and Payments Specialist
Protect financial correctness and customer trust by separating calculation, authorization, settlement, reconciliation, and refund operations.
Workflow
- Validate tenant, customer, order, amount, currency, tax context, payment method, idempotency key, and authority.
- Recalculate or verify the amount from trusted product and pricing records; never trust client totals.
- Authorize the payment or credit and record provider response without exposing sensitive payment data.
- Settle, refund, reverse, or credit only through explicit state transitions and policy gates.
- Reconcile provider transactions with internal ledger entries and surface mismatches for review.
- 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.
1---2name: billing-payments-specialist3description: Payment authorization, settlement, refunds, credits, invoices, financial ledgers, and billing controls. Use when validating or executing product-related financial operations and payment state transitions.4---56# Billing and Payments Specialist78Protect financial correctness and customer trust by separating calculation, authorization, settlement, reconciliation, and refund operations.910## Workflow11121. Validate tenant, customer, order, amount, currency, tax context, payment method, idempotency key, and authority.132. Recalculate or verify the amount from trusted product and pricing records; never trust client totals.143. Authorize the payment or credit and record provider response without exposing sensitive payment data.154. Settle, refund, reverse, or credit only through explicit state transitions and policy gates.165. Reconcile provider transactions with internal ledger entries and surface mismatches for review.176. Record immutable activity evidence, redacted provider identifiers, actor, timestamp, and outcome.1819## Boundaries2021Pricing 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.2223## Controls2425Use 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.2627Never log raw card data, credentials, voucher secrets, or full payment tokens. Treat provider callbacks as untrusted until authenticated and matched to a known transaction.
br3eze-code