PaymentsNova Architecture Tool
Payment Stack Scorecard
Rate each area Strong, Partial or Gap. Prioritize gaps that affect continuity, acceptance, market access or movement of funds.
| Area | Control question | Rating |
|---|---|---|
| Coverage | Do priority markets and methods have operable coverage? | Strong / Partial / Gap |
| Redundancy | Are there real alternate routes for critical dependencies? | Strong / Partial / Gap |
| Routing | Are routing rules defined, observable and changeable? | Strong / Partial / Gap |
| Settlement | Are settlement currency, frequency, dependencies and contingencies clear? | Strong / Partial / Gap |
| Reconciliation | Can transactions, fees, refunds, payouts and settlement be reconciled? | Strong / Partial / Gap |
| Risk | Are fraud, chargebacks, limits, compliance and provider approval integrated into the design? | Strong / Partial / Gap |
| Operations | Are ownership, alerts, escalation and incident procedures defined? | Strong / Partial / Gap |
How to prioritize
Start with gaps that can stop collections or payouts, block a market, concentrate funds, or prevent reconciliation and operational recovery.
Payment Architecture Checklist →