Skip to content

Fintech QA engineering blog

The FintechAssuranceLabs engineering blog publishes in five categories: regulation clauses with primary sources, public incident timelines with the test that would have caught each failure, tooling configuration with versions, copyable practice checklists, and dated industry data with its testing implication. Every post names its author, with pen names disclosed on author pages, and lists dated sources.

  • Incidents

    Visa outage of 1 June 2018: a partial switch failure that failover did not catch

    On 1 June 2018, a partial failure of a core switch in Visa Europe's primary UK data centre stopped the backup switch from taking over, and 5.2 million of 51.2 million transactions sent to Visa's European systems failed over ten hours. Failover tests that inject degraded, half-working components, plus merchant fallback tests, target that failure class.

    Adrian Voss

  • Practice

    Test strategy vs test plan for a fintech product: definitions and the template we use

    A test strategy sets the rules every release follows: how risk is rated, which environments and test data are allowed, and how evidence is kept for audits. A test plan applies the strategy to one release: flows in scope, selected tests, schedule, owners, and exit criteria. Separate documents give auditors one rule set for every release.

    Mira Kowal

  • Industry

    Agentic Commerce Protocol 2026-04-17: what merchant and PSP integrations now have to test

    The Agentic Commerce Protocol (ACP), an open specification maintained by OpenAI and Stripe, reached version 2026-04-17 with a mandatory Idempotency-Key on every POST, eleven checkout session statuses, and signed order webhooks. A merchant or payment service provider (PSP) integration now needs tests for delegated token allowances, state transitions, replay behaviour, and webhook signature windows.

    Mira Kowal

  • Incidents

    Evolve Bank data breach (2024): timeline and the partner data tests for BaaS programmes

    The Evolve Bank & Trust data breach of 2024 was a LockBit ransomware intrusion, active in February and May 2024, that exposed personal data of the bank's customers and of its fintech partners' end users. For Banking-as-a-Service (BaaS) programmes, tests can verify the partner data inventory, minimal data in test environments, access reviews, and network segmentation.

    Adrian Voss

  • Incidents

    Capital One outage, January 2025: a vendor data centre failure and the posting backlog it left

    The Capital One outage of 15 to 19 January 2025 followed a local power loss and hardware failure at vendor Fidelity Information Services (FIS), which delayed direct deposits, ACH payments, and transfers. Tests that limit this failure class are vendor failover drills, exactly-once posting of the recovery backlog, and one balance and status across every customer channel.

    Adrian Voss

Scope your testing

Send FintechAssuranceLabs your product, segment, money flows, and the standards that need evidence, and get a proposed test scope with its deliverables.

Scope your testing