For most fintechs, the first pen test is driven by someone else’s due diligence — an investor, a sponsor bank, a card scheme, an enterprise client or an FCA authorisation application. That changes what a good test looks like.
Who asks, and what they want to see
- Investors want assurance there’s no latent breach waiting to hit the valuation. They’ll ask whether the product was tested, when, by whom — and whether critical issues were fixed.
- Sponsor banks and BaaS partners answer to their own regulators and third-party risk teams. Expect detailed questionnaires and a request for the executive summary or an attestation letter.
- Card schemes and acquirers mean PCI DSS. Requirement 11.4 calls for internal and external penetration testing at least annually and after significant change, plus segmentation testing if segmentation reduces scope.
- Enterprise clients send security questionnaires with “latest pen test summary” on page one.
The mistakes that cost fintechs time
- Testing too late. A test the week before a deadline finds a critical that needs a sprint to fix. Test four to six weeks ahead.
- Testing the wrong thing. The marketing site isn’t the product. Scope the app, the API and the cloud environment.
- Unauthenticated-only testing. Most serious issues sit behind the login — one user reaching another’s account, transactions or KYC documents.
- No retest. Due diligence teams want criticals and highs closed, not just reported.
- A report you can’t share. Ask for a separate executive summary or attestation letter that can go to third parties without the technical detail.
What a fintech test should cover
- API authorisation — object- and function-level access control (OWASP API Top 10) across every role.
- Money movement logic — race conditions on balances and transfers, replayed requests, limit bypass, rounding and currency handling.
- Authentication and sessions — MFA bypass, account recovery abuse and token handling in mobile apps.
- KYC and document handling — upload abuse and access to other customers’ identity documents.
- Cloud configuration — IAM, secrets management, storage exposure and CI/CD pipeline access.
- Mobile apps, if any — local storage, certificate pinning and API keys in the binary.
The bottom line
Treat your first pen test as a sales asset, not a compliance chore. Scoped properly and done early, it shortens every partnership, funding round and enterprise deal that follows.
Frequently asked questions
When should a fintech get its first penetration test?
Four to six weeks before any launch, funding round, banking partnership or enterprise deal that needs test evidence — leaving time to fix and retest.
Does PCI DSS require penetration testing?
Yes. Requirement 11.4 requires internal and external penetration testing at least annually and after significant changes, plus segmentation testing where segmentation is used to reduce scope.