Skip to content

Adrian Voss

Lead QA engineer, payments and acquiring

Pen name. The company does not publish engineers' real names.

Tests card payment flows end to end, from authorisation and 3-D Secure to settlement files and refunds. Writes about payment incidents and what testing would have caught.

  • Practice

    A shift left testing approach for fintech: the checklist we run on money-moving stories

    A shift left testing approach for fintech moves money checks into the story, before code exists. We review every money-moving story against a nine-item checklist: amounts in minor units, rounding rule, currency, idempotency, failure states, reversal, reconciliation hook, regulatory trigger, and audit log. Pull request, continuous integration, and staging checks then test the recorded answers.

  • Practice

    UAT sign off checklist for fintech releases: the one we use

    Our UAT (user acceptance testing) sign off checklist for fintech releases records six decisions before go-live: business owners accepted each money flow on real-like synthetic data, UAT runs reconciled with no unexplained difference, customer notices were verified, open defects carry financial impact, rollback was rehearsed, and named signers approved with evidence retained.

  • Practice

    Regression test plan for a payments release: the template we use

    A regression test plan for a payments release selects tests by the money flows a change touches, runs them in risk tiers, and ends with a ledger reconciliation of the test run. Our template records scope, suites per tier, entry and exit criteria, environment, synthetic data, the reconciliation check, and the named roles who sign the release.

  • Incidents

    CrowdStrike outage of 19 July 2024: what Channel File 291 means for payment and banking tests

    The CrowdStrike outage started on 19 July 2024 at 04:09 UTC (Coordinated Universal Time), when a Falcon sensor content update crashed online Windows hosts until its revert at 05:27, including hosts at financial firms. The failure class is a vendor update sent to every host without staged rollout. Fintech teams should test vendor update canaries, offline payments, and recovery time.

  • 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.

  • 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.

  • 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.

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