The team behind the testing

How an engagement is staffed

We staff each engagement from the money flows and standards in scope, so the roles follow the services you buy.

• QA lead. Owns the test strategy, the requirement-to-test traceability, and the defect log with the financial impact of each defect. Reports release risk to your engineering and compliance owners.
• Fintech QA engineers. Test money movement and financial logic: authorisation, capture, refunds, interest accrual, fee rules, proration, and reconciliation against settlement files.
• Integration test engineers. Test open banking APIs, partner bank and BaaS integrations, webhooks, KYC and AML checks, chargeback flows, and ERP sync.
• Automation engineers. Build regression suites for critical money flows and wire them into your CI with release gates. The test automation service also delivers the framework setup and a coverage and run time report.
• Performance engineers. Build a load model from your peak patterns, such as payday or market opens, and report latency and throughput against agreed thresholds.
• Security testers. Run penetration tests against the systems named in the rules of engagement and produce PCI DSS requirement 11 test evidence through security testing.

A dedicated fintech QA team combines these roles for one product over a longer period.

Where the team works

Our engineers deliver from the United States, the European Union, and Canada. Our headquarters is in Andorra.

We agree the delivery locations for each engagement before the work starts. You can limit an engagement to engineers in one of these locations, for example when access to EU personal data from outside the EU can be a transfer under Chapter V of the GDPR.

Who writes on the blog

Four authors write the blog under pen names. The company does not publish engineers' real names. Each author writes only in the categories that match their work:

• Adrian Voss, lead QA engineer for payments and acquiring, writes on incidents and practice.
• Lena Marquet, compliance testing lead for PCI DSS, PSD2, and DORA, writes on regulation.
• Tomas Reyes, test automation architect for financial platforms, writes on tooling.
• Mira Kowal, senior QA engineer for lending, BNPL, and wealthtech, writes on industry and practice.

How engineer access is controlled

Each engineer uses a named account with the minimum access that the test plan needs, as PCI DSS requirement 7.2.2 describes. Engineers accept confidentiality terms before access starts, and you can get the list of engineers with access on request. At the end of the engagement, we ask you to remove all engineer accounts. We confirm the removal list with you. The security page describes access, test data, and environment isolation in full.