Pre-payment validation suite
|
|
| ID |
MOD-020 |
| System |
SD04 |
| Repo |
bank-payments |
| Build status |
Deployed |
| Deployed |
Yes |
| Last commit |
178e49975435ec5926a3b4f612f5d9ee9efc8495 |
Runs mandatory sequence before any payment is authorised: balance sufficiency, daily limit, sanctions screen, fraud score, account status. Any failure blocks. See ADR-001.
Module dependencies
Depends on
| Module |
Title |
Required? |
Contract |
Reason |
| MOD-013 |
Real-time sanctions screener |
Required |
contract/events/ |
Sanctions screening is a mandatory gate in the pre-payment validation chain. |
| MOD-023 |
Transaction fraud scorer |
Required |
— |
Fraud score check is a required gate before any payment is permitted to proceed. |
| MOD-003 |
Real-time balance engine |
Required |
— |
Sufficient funds check uses real-time balance to validate payment can be funded. |
| MOD-021 |
Payment limit & velocity controller |
Required |
— |
Velocity limit check against customer-configured limits is a mandatory pre-payment gate. |
| MOD-104 |
AWS shared infrastructure bootstrap |
Required |
— |
AWS shared infrastructure provisioned by MOD-104 (EventBridge buses, S3, KMS, Kinesis, Cognito) is required before this module can be deployed. |
| MOD-103 |
Neon database platform bootstrap |
Required |
— |
Neon database and schema provisioned by MOD-103 must exist before this module can read or write Postgres. |
Required by
| Module |
Title |
As |
Contract |
| MOD-022 |
Payment audit trail |
Hard dependency |
— |
| MOD-051 |
Financial automation rules engine |
Hard dependency |
— |
| MOD-067 |
Trade finance operations |
Hard dependency |
— |
| MOD-071 |
Payment initiation |
Hard dependency |
— |
| MOD-114 |
Direct debit mandate management |
Hard dependency |
— |
| MOD-119 |
BPAY payment integration |
Hard dependency |
— |
| MOD-120 |
PayID and Osko integration |
Hard dependency |
— |
| MOD-122 |
NZ faster payments and A2A integration |
Hard dependency |
— |
| MOD-135 |
Batch payment and payroll file processing |
Hard dependency |
— |
| MOD-141 |
Intra-bank transfer engine |
Hard dependency |
— |
| MOD-145 |
Payment hold & friction engine |
Hard dependency |
— |
| MOD-150 |
Risk management platform |
Hard dependency |
— |
| MOD-159 |
Synthetic transaction engine |
Hard dependency |
— |
| MOD-160 |
Cross-module acceptance suite |
Optional enhancement |
— |
Policies satisfied
| Policy |
Title |
Mode |
How |
| PAY-001 |
Payment Operations Policy |
GATE |
No payment leaves the bank without passing all pre-flight checks — enforced as sequential gate |
| AML-007 |
Sanctions Screening Policy |
GATE |
Sanctions screen is one of the mandatory pre-payment gates — cannot be bypassed |
| PAY-005 |
Payment Fraud Prevention Policy |
GATE |
Fraud score gate applied before every payment — high-risk payments blocked or challenged |
| CLQ-002 |
Liquidity Risk Management Policy |
CALC |
Payment volume and size contributes to intraday liquidity monitoring automatically |
Capabilities satisfied
| Capability |
Title |
Mode |
How |
| CAP-080 |
Contingent obligation management |
LOG |
Records each contingent obligation — guarantee, LC, committed facility — as a validated ledger structure with trigger conditions attached. |
| CAP-086 |
Trade document validation |
GATE |
Validates trade documents against LC conditions and blocks payment execution until all conditions are confirmed compliant. |
| CAP-087 |
Conditional fund holding & release (escrow) |
GATE |
Holds escrow funds in a restricted state and authorises release only after all defined conditions are validated. |
Part of SD04 — Payments Processing Platform
Compiled 2026-05-22 from source/entities/modules/MOD-020.yaml