01
Rail selection matrix
Decision dimensions for enabling settlement and payout rails—risk, reconciliation cost, and operational maturity tradeoffs.
Integration references
Operational design references
Matrices and state models for integration architects and payment operators—citation-friendly, bounded to merchant policy. Not live API documentation.
Playbooks: /playbooks. Docs: /docs.
02
Confirmation policy matrix
Map amount tiers, asset types, and use cases to confirmation depth and human review gates—merchant-defined, not universal.
03
Reconciliation state model
States across commerce, provider, and finance planes—and allowed transitions when matchers succeed or fail.
04
Settlement checkpoint model
Checkpoint types, owners, and progression rules between detection, policy confirmation, and treasury posting.
05
Provider retry semantics
Conceptual comparison of at-least-once delivery, handler response expectations, and idempotency responsibilities.
06
Webhook delivery model
Ordering assumptions, duplicate delivery, replay windows, and observability signals for event-driven integrations.
07
Async settlement lifecycle
Intermediate states when detection precedes confirmation and treasury posting—without collapsing to a single paid flag.
08
Ledger state transitions
Merchant ledger states, posting gates, and alignment with provider lifecycle labels under finance controls.
09
Operational signal catalog
Bounded observability signals for payment operations: webhook recency, checkpoint lag, exception depth, drift, provider latency, payout backlog.
10
Dashboard model
Role-oriented dashboard concepts for finance, integration, support, treasury, and executive views—anti-patterns for single-plane dashboards.