Skip to main content
“All combinations” must have an explicit boundary. The full Cartesian product is large and includes prohibited combinations. This review defines dimensions, forbidden combinations, mandatory high-risk cases and a process for generating the final test catalogue after policy selection. It does not claim every permutation is implemented or tested.

Dimensions

Required acceptance catalogue

Test generation and evidence

For each enabled product, enumerate allowed institution/party/channel combinations, add all applicable S cases and record expected states, book entries, notices and owners. Use pairwise coverage for low-risk display combinations; use exhaustive boundary/concurrency tests for money, permissions, approval and idempotency. Track requirement/feature/journey/scenario IDs to automated test and human UAT evidence. Actual issuer/network/hardware certification and bank policy acceptance cannot be replaced by mocks or a local browser demo. Document excluded combinations and the reason. Expand this matrix when an offering adds a new legal duty or financial transition.