PCI DSS Penetration Testing for Fintechs, Payments & Online Lenders

Internal, external, and segmentation testing mapped to PCI DSS Requirement 11.4. You get one report your QSA, acquirer, and sponsor bank can review, and we retest your fixes for free.

Written authorization and agreed scope before testing. Retesting terms are confirmed in the engagement proposal.

Why a scan or last year’s report may not be enough.

Payments teams often find out late that their testing evidence does not match what the standard asks for.

Scans are not pentests

Vulnerability scanning and penetration testing are separate requirements. A clean scan does not replace a manual test of your environment and applications.

Changes restart the clock

Significant changes to your infrastructure or applications can require new testing before the next annual date.

Segmentation has its own cycle

If segmentation reduces your PCI scope, it must be tested too. Service providers face a six-month cycle that is easy to miss.

Built for companies that move money or handle card data.

  • Payment gateways and payment facilitators
  • Fintech apps and digital wallets
  • Online lenders and buy-now-pay-later platforms
  • Merchants with complex card environments
  • Service providers that host or process card data for others
  • Companies preparing for a sponsor bank or partner security review

One engagement. Everything your assessor will ask to see.

External and application-layer testing

Testing of internet-facing systems and your payment or lending applications and APIs, including authentication, authorization, and transaction logic.

Internal network testing

Testing from inside your environment to see what an attacker could reach after getting a foothold.

Segmentation validation

Checks that the controls separating your card environment from out-of-scope systems actually hold.

Report mapped to Requirement 11.4

An executive summary and technical findings with severity, reproduction steps, and fixes, organized so your assessor can follow it.

Engineer walkthrough

A live call with your developers and infrastructure team to explain each finding and agree priorities.

Free retest

We verify your fixes within 30 days and update the report, so the evidence shows issues were corrected.

How it works

  1. Scoping callWe review your card data flows, systems, and deadline. You get a fixed-price quote within 2 business days.
  2. AuthorizationWe sign an NDA and written rules of engagement covering scope, dates, test accounts, and data handling.
  3. TestingTypically 2 to 3 weeks, depending on scope. We flag critical issues as soon as we find them.
  4. Report and retestYou receive the report and walkthrough, fix the issues, and we retest at no charge.

What we do and what we don’t

Silmagnate delivers penetration testing and the evidence that goes with it. We are not a Qualified Security Assessor (QSA), and we do not issue a Report on Compliance or Attestation of Compliance.

We work alongside your QSA or acquirer, and we can format findings to fit their requests.

Questions we hear from payments teams

How often does PCI DSS require penetration testing?

PCI DSS v4.0.1 asks for internal and external penetration testing at least every 12 months and after significant changes. Your QSA or acquirer will confirm exactly what applies to your environment.

Does a vulnerability scan count as a pentest?

No. Scanning and penetration testing are addressed by different requirements, and a scan does not replace a manual test.

What about segmentation testing?

If you use segmentation to reduce PCI scope, it needs to be tested. The standard sets a 12-month cycle for most organizations and six months for service providers. We include segmentation validation in the engagement.

Do you need access to real cardholder data?

No. We use test accounts and agreed methods. If we encounter live card data, we stop, tell you, and follow the handling rules in our authorization.

Will testing affect production?

We prefer a staging environment that mirrors production. If production testing is needed, we agree safe methods and time windows in writing first.

Can you work with our QSA?

Yes. Share their requirements at the scoping call, and we will organize the report to match.

Tell us your validation date. We will plan back from it.

Book a call or send a short note about your environment and deadline. Please do not send passwords, card data, or confidential system information by email.