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.