Tap-to-phone is the fastest-growing acceptance category in payments, and PCI MPoC is the standard that gates it. 192 individual security requirements. Accredited labs. Mandatory annual pen tests. Visa and Mastercard mandates already in effect. Paying.co's MPoC Certification Program is the end-to-end engagement that takes ISVs, acquirers, and OEMs from app to certified-and-shipping. Our target is 90 days. The actual timeline depends on your solution's readiness, scope, lab scheduling, and PCI review, and it is not guaranteed.
Not sure where MPoC fits next to SPoC and CPoC? Here's what MPoC certification actually is.
Tap-to-phone has three groups of companies trying to ship it — and each one comes into PCI MPoC with a different problem to solve. We've built the program to match.
You already have a vertical SaaS product — field service, restaurant ordering, healthcare scheduling — and you want to add tap-to-phone so customers can take a payment without leaving your app.
Talk to usYou're an acquirer or PayFac who wants to give your merchants a branded tap-to-phone product without building it from scratch. Certification stays under your name.
Talk to usYou build Android-based devices — phones, rugged terminals, enterprise hardware — and want MPoC compliance baked in at the firmware/OS layer.
Talk to usMPoC isn't one task. It's an engineering project, a security project, a documentation project, and a lab project running in parallel. The program covers every piece so the only thing you're tracking is the calendar.
Full technical gap analysis against all 192 PCI MPoC requirements across five domains. Written readiness report on day one, fixed-cost path on day three.
Tamper detection, root/jailbreak resilience, code obfuscation, runtime monitoring. If you have an existing app, we adapt it. If not, we build it.
MPoC requires PCI DSS backend, PCI PIN processing, and Secure SLC development. We bring you to alignment on all three.
We bring the accredited security lab, deliver the evidence pack, run the mandatory pen test through Flaw.co, and get you onto the PCI approved list.
PCI MPoC is the toughest security spec PCI has ever issued. 192 requirements across five domains, with dependencies on PCI DSS, PCI PIN, and Secure SLC compliance underneath. Most companies trying to ship tap-to-phone either lose 12 months figuring it out themselves, or pay several different consultancies to handle the pieces.
Paying.co brings the engineering depth to deliver MPoC certification as one engagement: SDK hardening, secure SLC alignment, backend DSS expertise, pen testing via Flaw.co, and experience working with the accredited labs PCI recognizes. We start every project with a written gap analysis and a scoped quote, and we work toward a 90-day target.
Tap-to-phone is the fastest-growing acceptance category in payments. SoftPOS is projected to be a $27.7B market by 2030. Visa and Mastercard are mandating MPoC compliance for SoftPOS solutions. The window to be early is open right now.
Talk to our MPoC teamPCI MPoC v1.1 breaks 192 requirements into five security domains. Most teams that fail certification fail because one of the five was treated as an afterthought.
Tamper detection, code obfuscation, anti-debugging, root and jailbreak resilience, runtime integrity checks.
The attestation server validates device posture in real time, wired to the SDK, the backend, and the runtime hooks.
PCI DSS for the payment processing back end. PCI PIN for PIN handling. Existing controls leveraged where they exist.
PCI MPoC requires development against the Secure SLC standard — threat modeling, code review, vulnerability response.
Annual penetration testing of mobile + backend is a hard requirement, run through Flaw.co on the first pass.
Certification programs often slip, so we define scope and responsibilities up front. The six elements below describe how the program is structured. The binding terms for each engagement are set in the engagement agreement.
Our target is the PCI approved list within 90 calendar days of kickoff. It is a target, not a guarantee, and depends on readiness, lab scheduling, and PCI review.
A written gap analysis defines the scope, and the quote follows from it. Changes to scope are handled through the engagement agreement.
An internal pre-assessment before submitting to the accredited lab, to find and fix issues early. It reduces risk but does not guarantee the lab's result.
The PCI MPoC listing is intended to be in your company name. Ownership of the solution and its documentation is set in the engagement agreement.
The required penetration test is performed through Flaw.co, covering the mobile app and attestation server, with remediation support. Inclusion and pricing are stated in your agreement.
We can support annual recertification. Scope and pricing for year two are discussed and set in the engagement agreement.
Every MPoC engagement follows the same three-phase shape. Status meetings every Friday. Slack channel open the whole time.
Gap analysis first, followed by a scoped quote. SDK hardening, attestation server, backend DSS and PIN alignment, SLC documentation by day 30.
Internal pre-assessment against the lab's evidence pack. Mandatory pen test through Flaw.co on mobile + backend, remediated and submitted.
Lab assessment runs against the cleaned evidence pack. The target is PCI listing by day 90, subject to lab scheduling and PCI review.
Tell us where you are today — existing SoftPOS app, idea phase, or somewhere in between — and which audience you fit (ISV, acquirer, or OEM). We'll come back with a written gap analysis, a scoped quote, and a delivery plan built around a 90-day target.