PCI MPoC vulnerability assessment and penetration testing.

Need the vulnerability assessment and interface penetration test that requirements 1A-1.3 and 4A-3.1 call for? We find the vulnerabilities in your MPoC Software and its backend interfaces before the laboratory does.

PCI Mobile Payments on COTS (MPoC) addresses payment acceptance on commercial off-the-shelf devices, such as smartphones.

For your PCI MPoC evaluation, you need a vulnerability assessment of the MPoC Software and a penetration test of its backend interfaces, and you must repeat both every year. This is reflected in the following requirements from the standard:

  • Requirement 1A-1.3: A vulnerability assessment has been performed on the MPoC Software prior to initial assessment and at least once per year thereafter.
  • Requirement 4A-3.1: A penetration test has been performed on the interfaces between the COTS-based MPoC Software and back-end environments (e.g., A&M, payment processing and/or remote kernel) prior to the validation and listing of an MPoC Solution or A&M service provider, and at least once per year thereafter.

Vulnerabilities found during the formal evaluation have to be fixed while it is in progress, which can delay validation and listing. The laboratory cannot tell you how to fix them, because it cannot take part in designing or developing a solution it evaluates.

We check whether an attacker can reach the assets PCI MPoC requires you to protect, such as card data, the PIN, cryptographic keys or attestation data. We define the scope with your team to cover the parts of your MPoC Solution or A&M service that the requirements apply to. Depending on your solution, testing can cover:

  • MPoC Software on COTS devices, whether delivered as an app or an SDK.
  • Interfaces with backend environments, such as attestation and monitoring, payment processing and remote kernels: whether an attacker can compromise your backend from a tampered app.
  • Software protections the solution relies on, such as anti-tampering, runtime checks and white-box cryptography.
  • Card reading and PIN entry flows, including NFC, where they are part of your solution.
  1. Call: you tell us about your solution and your evaluation date.
  2. Proposal: we set out the agreed scope for the applicable requirements, what we need from you, the schedule and a fixed price.
  3. Testing: you send us the builds and we start. If we find something critical, we let you know right away.
  4. Report and review: we send you the report and go through it with your engineers.
  5. Retest: once you have fixed the vulnerabilities, we confirm they are resolved and send you a new version of the report for your laboratory.
  6. Annual cycle: we repeat the assessment and the penetration test each year, as the requirements expect.

Technical report

States what we tested: the MPoC Software on each platform it supports, the build and the backend interfaces. Every finding includes evidence, reproduction steps, impact, a CVSS score and vector, CWE and OWASP MASWE references, and how to fix it.

Executive summary

Covers the scope and build tested, the results and the priorities, for management and non-technical readers.

Retest report

If you include the retest, we send a new version of the report with the status of each finding on the new build (fixed, mitigated or open), before you submit your solution to the laboratory.

Letter for your customers

On request, at no extra cost, we provide a signed letter with what we tested, the version, the date and the result, for your customers or auditors. After the retest, we update it with the new results.

We have been evaluators

Our team comes from security certification laboratories, with experience in mobile payment standards such as EMVCo SBMP and in Common Criteria. We know the EMV protocols and payment processing that PCI MPoC expects from whoever performs these tests.

Specialists in mobile security

Our team contributes to OWASP Mobile Application Security, the main reference for testing mobile apps. OWASP recognized this work by naming vulnit an OWASP MAS Advocate.

We help you fix what we find

We explain how to fix each finding and, if you include the retest, check the fixes before you submit your solution.

Meet the team
What is PCI MPoC?

PCI Mobile Payments on COTS (MPoC) is a security standard for solutions that accept payments on commercial off-the-shelf devices, such as smartphones. It covers the mobile software, its connections to supporting services and other parts of the payment solution.

Who performs the formal PCI MPoC evaluation?

An independent PCI-recognized MPoC laboratory checks your solution against the applicable requirements and reviews the supporting evidence. Our vulnerability assessment and interface penetration test are part of that evidence; they are not the formal evaluation.

Can't the laboratory perform the vulnerability assessment directly?

In principle, yes. But the vulnerability assessment is additional work beyond the formal evaluation: it requires its own testing process and a separate report. The laboratory cannot tell you how to fix the vulnerabilities it finds, during the formal evaluation or outside it, because it cannot evaluate a solution it has helped design or develop. Consider the level of remediation support your team will need when deciding who performs the assessment.

Can I perform the vulnerability assessment myself?

Potentially, if you have testers independent of the software development team and can document the scope, testing and findings. The standard expects them to understand EMV protocols and payment processing, and to have experience in mobile security and penetration testing.

Do you test on physical devices?

When needed. On Android we mainly work with Chameleon, our analysis environment: it gives us deep visibility into what the app does in the operating system, and handles root, pinning and anti-instrumentation checks at the OS level by default. If we hit a limitation that matters for your solution, we use physical devices. On iOS we use physical devices.

What do you need from us?

The builds of your MPoC Software (the app or SDK you plan to submit for evaluation), test accounts and access to the backend environments in scope, whether production, pre-production or a test environment. The proposal sets out the details.

Do you need source code?

No. By default, testing is black-box: we work with the same information an attacker would have, using the build you plan to submit for evaluation. If you prefer, we can also review the source code.

Do you use AI on my solution?

Yes, to cover more of your solution and go deeper in the same time. We use AI providers that do not train their models on your data. We only use accounts you provide or that we create ourselves, never other real users' accounts. Our specialists lead the work and validate every result. If your policy does not allow external AI, tell us when we agree on the scope and we work without it.

How long does it take and what does it cost?

It depends on the number of apps or SDKs and platforms, their complexity (for example custom cryptography or hardware features such as NFC), the backend interfaces in scope and your evaluation date. We send you a proposal with a fixed price and the schedule. It usually takes one to two weeks per platform, interface penetration test and report included, depending on the complexity of your solution. We can usually start the same week you accept the proposal; the start date depends on our team's workload and is stated in the proposal.

Is retesting included?

Retesting is quoted separately at a reduced rate. In the proposal we give you two options, testing only or testing with one retest round, so you know the total cost from the start.

Do you offer recurring contracts?

Yes. If you plan your annual assessments with us, we agree special conditions for the whole cycle.

What format do the findings come in?

You receive one report per platform, with every finding detailed. If you also want to use them in your own tools, we provide them as CSV or JSON too.

What language is the report in?

English by default. If you need it in Spanish, just tell us.

How do you handle confidentiality?

We agree confidentiality terms before you share builds or documentation. We have a standard NDA, but if you prefer to use yours, we are happy to review it.

Can you help with other PCI MPoC requirements?

Our service focuses on 1A-1.3 and 4A-3.1. Tell us which other requirements you are working on, and we can discuss whether our mobile security expertise can help. We do not perform the formal MPoC evaluation.

Is this the same as a general mobile application penetration test?

No. A general mobile application penetration test investigates vulnerabilities in an agreed app scope. This service is scoped to PCI MPoC Software and backend interface requirements, including the evidence these requirements call for in the laboratory evaluation and the annual testing cycle.

Tell us about your solution and your evaluation date. We reply within one business day to arrange a scoping call.

Talk to our team

A necessary cookie remembers your choices for up to 180 days. Privacy policy.