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

    Synapse bankruptcy: the FBO ledger shortfall across four partner banks, timeline to September 2026

    Synapse Financial Technologies filed for Chapter 11 bankruptcy on 22 April 2024, and its partner banks held $60 million to $90 million less for consumers than Synapse's records showed, according to the Consumer Financial Protection Bureau (CFPB). The failure class is for-benefit-of (FBO) ledger reconciliation across banks; a daily per-bank match exposes it.

    Adrian Voss

  • Regulation

    European Accessibility Act in 2026: EN 301 549 V4.1.1 and the banking test scope

    The European Accessibility Act, Directive (EU) 2019/882, has applied to consumer banking and e-commerce services since 28 June 2025. EN 301 549 V4.1.1, published 2 September 2026, moves web and app tests from Web Content Accessibility Guidelines (WCAG) 2.1 AA to WCAG 2.2 AA. V4.1.1 was not cited in the Official Journal on 22 September 2026.

    Lena Marquet

  • Industry

    Stablecoin payments in September 2026: GENIUS Act proposals, MiCA, and what to test

    US stablecoin payments come under the GENIUS Act on 18 January 2027, since no final implementing rule appeared by 22 September 2026; the EU Markets in Crypto-Assets Regulation (MiCA) already applies. Test scope covers redemption at par and its timing, reserve reconciliation, travel rule data, on-chain sanctions blocking, and foreign exchange (FX) settlement at on- and off-ramps.

    Mira Kowal

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

    Adrian Voss

  • Regulation

    UK APP fraud reimbursement rules after the PSR's July 2026 evaluation: what stays in test scope

    After the Payment Systems Regulator (PSR) 1 July 2026 evaluation, UK authorised push payment (APP) fraud rules require sending payment service providers (PSPs) to reimburse in-scope claims up to £85,000, minus an optional £100 excess, within five business days unless the clock stops, except first-party fraud or gross negligence. After reimbursing, they can require up to 50% from receiving PSPs.

    Lena Marquet

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

    Adrian Voss

  • Practice

    A risk based testing approach for fintech: the scoring matrix we use

    Our risk based testing approach for fintech scores each test item by impact per failure (money moved, regulatory exposure, customer harm) and by likelihood (change frequency, integration count), and multiplies the two scores into a risk level that sets test depth. In our practice, a top-level money or regulatory item never drops below the second of four depth tiers.

    Mira Kowal

  • Tooling

    WireMock tutorial: stubbing a payment processor with WireMock 3.13.2

    This WireMock tutorial stubs a payment processor with WireMock 3.13.2 JSON (JavaScript Object Notation) mappings: an approval, a soft decline, a timeout after approval using fixedDelayMilliseconds, an authorise-then-capture state machine built from scenarios, and a capture webhook. Every mapping was re-run against WireMock 3.13.2 on 22 September 2026 with synthetic tokens.

    Tomas Reyes

  • Regulation

    Nacha 2026 rule changes: fraud monitoring phases and PAYROLL and PURCHASE descriptors

    The Nacha 2026 rule changes require risk-based fraud monitoring from originating banks (ODFIs), non-consumer Originators, Third-Party Senders, Third-Party Service Providers, and receiving banks (RDFIs), with Phase 1 from 20 March 2026 and Phase 2 from 22 June 2026. ACH test scope now covers fraud alert rules, R17 return handling, and PAYROLL and PURCHASE descriptors.

    Lena Marquet

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

    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