Financial-system patterns
Monetary values
Integer minor units avoid common binary floating-point representation errors.
REFERENCE CATEGORY
Financial-system patterns
15 practical topics
Financial-system patterns
Transaction states
Explicit states distinguish pending, successful, failed, and unknown outcomes.
Financial-system patterns
Atomic operations
Atomic operations either apply completely or have no effect.
Financial-system patterns
Database transactions
Database transactions group related local financial writes.
Financial-system patterns
Idempotency
Persisted idempotency prevents a repeated logical request from producing a second effect.
Financial-system patterns
Duplicate requests
Duplicate handling defines behavior when the same action arrives again.
Financial-system patterns
Audit trails
Financial audit records should explain state changes with actor and correlation data.
Financial-system patterns
Immutable records
Immutable financial history is amended with new compensating records.
Financial-system patterns
Reconciliation
Reconciliation compares independent records and surfaces discrepancies.
Financial-system patterns
Authorization
Financial authorization checks ownership, capabilities, limits, and separation of duties.
Financial-system patterns
Concurrency
Concurrent financial operations can both act on an old balance.
Financial-system patterns
Optimistic locking
Optimistic locking updates only if a version has not changed.
Financial-system patterns
Pessimistic locking
Pessimistic locking holds database locks while checking and changing state.
Financial-system patterns
Consistency
Consistency preserves invariants across records and systems.
Financial-system patterns
Failure handling
Financial failure handling distinguishes rejected, failed, and unknown outcomes.