PCI MPoC for African Acquirers: Prepare Your Payment Rollout

Content authorBy EGSPublished onReading time11 min read
A group of business consultants collaborates in a modern office, focused on a digital screen displaying financial data and graphs.

This article is a delivery guide for acquirers and payment service providers in Africa that have already decided to accept card payments on standard smartphones. It explains how to set scope and read supplier evidence properly, then how to split responsibilities across the delivery chain to avoid the rework that shows up late in integration.

Why the standard decides your rollout plan

Once you accept a PIN on a merchant's own phone, PCI MPoC stops being a procurement checkbox and starts shaping your architecture and your vendor contracts. The decision has already been made in most acquiring teams across the continent. What hasn't been done is the unglamorous work of figuring out who owns which control and what breaks when Android ships its next release.

That gap is where budgets go. A supplier says "we're certified," and six months later the assessor asks a question nobody prepared for. This guide works through the sequence that prevents it, from acceptance model to final readiness gate.

Choose the acceptance model

Start by writing down, in one page, what you're actually deploying. Who is the merchant, a street vendor with a R2,000 handset or a franchise chain with managed devices? Which devices and operating system versions are in scope, and where is the PIN entered? Until those answers are fixed, every downstream conversation stays theoretical.

The reason PCI MPoC applies is narrow and specific. The Mobile Payments on COTS standard, the MPoC standard, covers payment acceptance on commercial off-the-shelf devices that have no certified tamper-resistant hardware, which means the security that a traditional terminal gets from its enclosure has to come from software and attestation instead. The PCI Security Standards Council published the standard in November 2022 as a single framework covering both contactless reads and PIN entry on the same consumer device. Its two predecessors, software-based PIN entry and contactless payments on COTS, split those use cases apart and constrained solution design in ways that didn't match how merchants actually use phones.

You've chosen an acceptance model where the merchant's own phone does the work, and that choice carries a defined set of obligations. Treat the model description as a controlled document, because when it changes, your scope changes with it.

Set PCI MPoC scope

Infographic showing the flow of attestation and monitoring services in financial transactions, with interconnected cards and arrows in a blue palette.

Scope is where most rollouts quietly go wrong. The Council runs separate PCI MPoC listings for validated MPoC solutions and for MPoC software. It also runs a PCI MPoC listing for MPoC components, and those listings are not interchangeable. A component listing tells you one piece has been assessed against the relevant requirements. It tells you nothing about whether your assembled deployment holds together.

The MPoC standard is deliberately modular, which is its strength and its trap. Vendors can validate parts independently and sell them into different architectures, so you can assemble a solution from pieces that each carry a legitimate listing and still have no validated solution of your own. Component-level responsibility ends at the component boundary. Accountability for the complete solution sits with whoever puts their name on it, and in African acquiring arrangements that is frequently you.

Start building your financial platform?

Speak with EGS engineers about open banking, payment infrastructure, cloud systems, and enterprise software.

Get in Touch →

MPoC standard software

The acceptance application is the part everyone looks at first. Assessment covers how the application handles account data and PIN and how it behaves when the device it's running on turns out to be rooted. All of that is evaluated against declared conditions rather than in the abstract.

Those conditions matter more than the listing line itself. The software's validation names supported device classes and operating system versions. The MPoC standard expects the software to depend on an attestation and monitoring service that can confirm the device state before a transaction proceeds, which is why Google's Play Integrity API and hardware-backed key storage through Android StrongBox keep appearing in vendor architecture diagrams.

Service component scope

Plenty of what keeps you compliant never runs on the merchant's handset. Attestation and monitoring services decide whether a given device is trustworthy at a given moment. Key management generates and rotates the keys protecting account data and PIN blocks. Back-end decryption and the lifecycle machinery for registering and deactivating merchant devices sit in the same category.

These services carry their own assessment scope and their own operational obligations, and they're the ones that fail quietly. A monitoring service that nobody watches is an audit finding with a delay fuse. When you map your architecture, draw the service boundaries before you draw the application boxes, because the services determine where your evidence has to come from.

Complete solution validation

A complete PCI MPoC solution is the assembled thing a merchant actually uses, and it's validated as such by an assessor qualified under the MPoC program against the current requirements in the PCI SSC document library. Validated components reduce the work without finishing it.

The gap is in the joins. Your integration code and your key injection process sit between the validated pieces, and neither of them inherited anyone else's listing. If nobody has assessed the way you connected a listed vendor's software to a listed processing host, you have two compliant components and an unvalidated deployment.

Map rollout dependencies

Before architecture is frozen, build a dependency map that records, for every component, what was validated and by whom. Add the supported device and operating system matrix and the change control process that governs them. It's dull work and it saves quarters.

Unclear boundaries produce four predictable outcomes, and all of them cost delivery time. Design uncertainty stalls engineering while people argue about who implements a control. Retesting arrives when an assumption turns out to be undocumented. Approvals slip because evidence has to be reconstructed after the fact, and engineering rework lands when a dependency nobody mapped turns out to be mandatory.

Version drift deserves its own line in the map. Google publishes monthly Android security bulletins and a new platform release every year, and your supported-environment statement ages against both. If your vendor's validated environment stops at an operating system version your merchant base has already moved past, you'll discover it through declined transactions rather than through a planning meeting.

Assign South African responsibilities

Responsibility matrices only work when someone signs them. The split below is one plausible arrangement for a South African deployment, and it needs adjusting to your contracts and whatever the South African Reserve Bank's payments oversight and the payment system body rules require of your specific role in the national payment system. Nothing here is a universal regulatory treatment.

  • Acquirer: owns the complete solution claim and the decision to go live or hold.

  • Payment service provider: owns merchant onboarding and first-line operational support.

  • Software vendor: owns the acceptance application and its validated listing and version.

  • Service providers: own attestation and the service-level commitments that say how fast they tell you something is wrong.

  • Merchants: own device custody and reporting a lost or compromised handset.

  • Engineering partner: owns integration design and the technical evidence pack handed to the assessor.

  • Assessor: owns the independent judgment on whether the assembled solution meets the requirements.

Two duties get orphaned more than any others. The first is who watches monitoring alerts at 02:00 on a Sunday. The second is who updates the evidence set when a component version changes, because evidence that describes last quarter's build is worth nothing in an assessment.

Start building your financial platform?

Speak with EGS engineers about open banking, payment infrastructure, cloud systems, and enterprise software.

Get in Touch →

Check supplier evidence

Procurement timelines reward whoever answers fastest, and in mobile acceptance the fastest answer is the vaguest one. Test supplier claims before architecture and delivery commitments are signed. PCI MPoC certification language in a sales deck is a starting point for questions.

MPoC certification claims

Ask for the exact entry on the Council's listings, then open the listing yourself and confirm it matches the build you'll receive. Ask which listing type it is, because each listing type carries different weight in your architecture. Ask for the attestation document and the scope description that sits behind it.

There's a real difference between informal "certified" language and formal validation evidence. A vendor saying it's PCI MPoC certification compliant or built to the standard is describing intent. A listing entry with a current validation status and a matching attestation is a fact you can build on, and the gap between the two has derailed more than one African mobile acceptance launch.

Environment and dependency evidence

Get the supported environment in writing and check it against the handsets your merchants actually own.

The questions worth forcing an answer to:

  • Which device models and chipsets are approved, and which are explicitly excluded?

  • Which Android versions and API levels are covered, and what happens to support when a new release lands?

  • Which back-end services must be present, and are they the vendor's own or a third party's?

  • Which integrations were in scope during assessment, and which were not?

  • What operational controls does the vendor assume you'll run, and where is that assumption documented?

  • What are the stated exclusions, in the vendor's own words?

Exclusions are the most useful page in any evidence pack. They tell you precisely what you've just become responsible for.

Change and monitoring ownership

Mobile acceptance is a live security posture, so the ownership questions that matter are about motion. Who detects a new attack technique against the acceptance application, and how fast does that reach you? Who maintains each component, and who refreshes the evidence afterward?

Push hard on the incident path. If a merchant's device is compromised, name the party that disables it and the party that notifies the schemes. Then ask the same question for a mandatory operating system upgrade and for an integration change on your side, because PCI MPoC certification holds only while the assessed conditions still describe reality.

Turn scope into delivery

Scope documents don't process transactions. Somewhere between the signed vendor contract and the first live merchant, someone has to map the dependencies into a real design and prove the whole thing works under load and under failure.

That's the work EGS does. The team maps component dependencies against your acceptance model and builds the test workflows that exercise the awkward paths. Production support and the preparation of technical evidence for assessment sit in the same engagement, which keeps the documentation attached to the system it describes.

Separate engineering and validation

EGS supports implementation readiness and evidence preparation. It doesn't replace the qualified assessor, and it has no part in the Council's validation decision. Those are deliberately independent roles and conflating them helps nobody.

Bring the assessor in earlier than feels comfortable. The right moment is when the architecture is drafted and before integration work starts, because an assessor's view on scope boundaries at that point costs a meeting, while the same view after delivery costs a rebuild. Keep them informed through major design changes and schedule the formal assessment against a frozen, versioned build.

Confirm rollout readiness

Before you approve the go-live, run one gate and accept a hold if any line fails. The MPoC standard rewards discipline at exactly this point, because every unresolved item here becomes an incident later.

  1. The acceptance model is documented and signed off by the business.

  2. Every supplier claim is backed by a listing entry and an attestation you've read, with PCI MPoC certification status confirmed as current rather than pending.

  3. The responsibility matrix is accepted in writing by each named party and covers the orphan duties.

  4. Supported devices and operating system versions match your real merchant base.

  5. Testing covers failure and tamper detection.

  6. Monitoring has a named owner and a tested escalation path.

  7. Change control defines who re-validates what when a component version moves.

  8. Unresolved dependencies are listed with an owner and a date, and none of them sit on the critical path.

Anything you can't answer today becomes an assessor's question later, under worse conditions. Write the gaps down and assign them now.

Discuss your rollout

Mobile acceptance across African markets succeeds or fails on delivery detail. Bring your mobile acceptance architecture to EGS to discuss scope and rollout readiness. Tell us the acceptance model you've chosen and the delivery questions you haven't resolved yet. Book a call with our engineering team to turn PCI MPoC scope into a plan you can ship.

Start building your financial platform?

Speak with EGS engineers about open banking, payment infrastructure, cloud systems, and enterprise software.

Get in Touch →

Request the exact PCI Security Standards Council listing, current validation status, attestation, scope description, supported devices, operating systems, and exclusions. Compare those details with the build and merchant devices you plan to deploy before signing delivery commitments.

An Android update can move devices outside the environment covered by a supplier's assessment. Track supported versions against monthly security patches and annual platform releases, then define who tests, approves, or pauses an update before merchants receive it.

The responsibility matrix must name the party that disables a compromised device and the party that reports the event to relevant payment schemes. Define detection thresholds, notification times, replacement procedures, and evidence retention before production, then test the escalation path.

No. A component listing confirms that one part was assessed, but it doesn't validate your integrations, key injection process, service configuration, or operational controls. The assembled deployment needs review as a complete solution under its actual architecture and declared environment.

Involve the qualified assessor after drafting the architecture and before integration begins. EGS can prepare the technical evidence and readiness plan, while the independent assessor confirms scope and validation. Book a call with EGS if you need to resolve boundaries before delivery work starts.

Schedule a Meeting

Book a time that works best for you

You Might Also Like

Discover more insights and articles

A project manager in business casual attire discusses a document intake process with a team in a modern office, focusing on a large monitor.

Bank document intake workflow: A readiness checklist

This article gives you a checkpoint-by-checkpoint method for testing a document intake process before you turn it on. It includes a worksheet structure you can copy into a spreadsheet and the evidence each control needs to produce.

Two business partners collaborate on configuring a POS terminal in a modern office, surrounded by payment devices and colleagues.

EthioPay for Ethiopian Banks: Turn Readiness into a Delivery Plan

This article explains how an Ethiopian bank moves from "we want to participate" to a dated, costed integration plan for the country's domestic card scheme and instant payment rails. It covers service selection and a phased release sequence.

A modern smartphone displaying a mobile banking app lies on a wooden desk, surrounded by abstract payment cards and a notebook.

AfriGO Card Readiness: Plan Your Nigerian Bank’s Rollout

This article is a readiness guide for moving from "we're considering it" to a controlled pilot on Nigeria's domestic card rails. It covers role definition and launch scope, then maps the transaction flow so you can assess systems and assign requirement ownership through the workstream matrix that holds the whole program together.

A professional seated at a desk uses a smartphone and payment card, engaged in online banking in a bright, modern office.

G2P Payments in Africa: Build Reliable Social Payment Infrastructure

This article traces the full lifecycle of a government social payment in Africa, from eligibility approval through to reconciliation and investigation evidence. It assigns operational ownership at each system boundary and sets out how to control exceptions and assisted access.