PCI PIN Security: Close Engineering Gaps in African Acquiring

Content authorBy EGSPublished onReading time10 min read
A security specialist types on a laptop in a bright office, surrounded by multiple monitors displaying code and analytics, with a city view.

This article is a working method for checking whether your PCI PIN scope matches the environment you actually run. It uses a hypothetical Nigerian acquirer to trace a PIN transaction end to end, then gives you a worksheet and an evidence checklist you can complete with your own architecture and operations teams.

Why PCI PIN scope slips

PCI PIN scope slips quietly, and almost never through negligence. A network diagram drawn for the last assessment still gets handed over, while the switch behind it has been re-platformed and a new third-party processor has been onboarded.

The gap opens in three places. Dependencies nobody documented, because the engineer who built the integration left. Operations outsourced to a terminal service provider whose contract describes a service level but not a control boundary. And procedures written to describe how key loading should work rather than how it works on a Tuesday night in Lagos.

The result is weak evidence and implementation risk that surfaces during assessment instead of before it. You fix that by mapping boundaries first and arguing about controls second.

Separate the PCI standards

Infographic section illustrating PCI DSS compliance processes with modular blocks, curved arrows, and flat vector financial icons on a pale-blue gradient.

Before you draw a single boundary, be precise about which standard you are drawing it for. Teams with solid PCI knowledge still collapse a PIN assessment and a data security assessment into one mental category that also includes a device approval. They answer different questions, and evidence for one proves nothing about the other.

PCI PIN Security covers the PIN and the keys that protect it. PCI DSS covers account data. A device approval covers a product as the laboratory tested it, in a configuration you have since changed.

PCI PIN security requirements

The PCI PIN Security Requirements organize controls into seven objectives that cover PIN processing and cryptographic key management across the full lifecycle. Those objectives also cover secure cryptographic devices and physical facilities, with the operational procedures around all of it. Version 3.1 has been current since March 2021, and the key block phase-in dates have all passed. Phase 3 extended key block protection to all merchant hosts, POS devices and ATMs on 1 January 2025.

One requirement worth checking against your own device estate is 32-9 on encrypted key loading. The PCI SSC revised its implementation dates and narrowed applicability from POI v3 and higher to POI v5 and higher in a November 2020 bulletin, which means your remediation plan depends on which terminal generations you actually deploy.

Treat everything above as a pointer. Confirm the current version in the PCI SSC document library and check what the Central Bank of Nigeria and your local switch require on top of your card brand program rules. Visa sunset its own PIN Security Program on 1 October 2023, and compliance with the PCI PIN Security Requirements remained mandatory afterward, validated through a Qualified PIN Assessor (QPA).

PCI DSS scope

Your cardholder data environment and your PIN environment overlap on the same hardware more often than the documentation admits. The switch that routes an authorization message handles the Primary Account Number (PAN) and the encrypted PIN block in the same transaction. That does not merge the two scopes.

PCI DSS v4.0.1 is the version assessed today, and the 51 future-dated requirements introduced in v4.x became mandatory on 31 March 2025. A Qualified Security Assessor evaluates that work. A QPA evaluates your PIN controls, and the two produce separate reports with separate evidence trails.

Where this bites in practice is sampling. A QSA accepting your segmentation evidence tells a PCI PIN assessor nothing about custodian separation or whether your key ceremony logs name two people who were genuinely in the room.

Start building your financial platform?

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

Get in Touch →

HSM product approval

An approved HSM is a prerequisite. The PCI SSC published PTS HSM v4.0 in December 2021, which added an evaluation module and approval class for cloud-based HSMs used in HSM-as-a-service offerings, and the council moved on again with PTS HSM v5.0 in May 2026, which removes TDES for device security purposes and adds modules for key transfer and remote administration. Check your firmware version against the listing, because approvals are version-specific. The deadline for new v4 device approvals was extended to 30 June 2027.

What the listing does not cover is everything you did after unboxing. How the device is configured and how your switch authenticates to it sit outside that listing. Which host commands you left enabled and who holds the key components sit in the same gap, as does whether the room it sits in meets the facility controls. The PIN standard assesses the acquiring entity. For related implementation considerations, see HSM certification.

Map a Nigerian environment

Take a hypothetical Lagos-based acquirer with a merchant POS estate and a deployed ATM fleet. The PIN is entered on an approved POI device, encrypted under a DUKPT key injected at a key injection facility operated by a licensed Payment Terminal Service Provider. The acquirer never touches that terminal physically, yet the keys inside it sit squarely inside its PCI PIN Security Requirements scope.

From the terminal, the encrypted PIN block travels through the PTSP's connectivity to NIBSS, which acts as the Payment Terminal Service Aggregator and is the only entity permitted to operate a terminal management system in Nigeria. CBN rules add a hard geographic constraint, since all domestic POS and ATM transactions must be switched locally and shall not be routed outside Nigeria. That constraint shapes where your protection domains sit.

The message then reaches the acquirer's switch, where the PIN block is translated under an HSM-held zone key before it goes onward to the issuer or a third-party processor. Onward connections now include AfriGO, launched by the CBN with NIBSS on 26 January 2023 as Africa's first central-bank-led domestic card scheme, alongside Verve and the international brands. Each onward connection is a separate key relationship with its own exchange procedure and its own evidence. The switch's role is also covered in this guide to payment switch engineering.

Volume makes the boundary question urgent rather than academic. The CBN recorded 2,935,765 POS terminals deployed in the first half of 2024, up 20 percent from the preceding half-year. Supervision adds pressure from a second direction, because the CBN's risk-based framework requires institutions to carry out continuous monitoring of the PSP's compliance status and collect the supporting documentation.

Build the scope worksheet

The worksheet below is deliberately boring. Fill it in a room with architecture and operations present at the same time as security and compliance, because every disagreement you surface there is a finding you avoid later. Keep it descriptive and avoid recording configuration detail that would be useful to an attacker.

Trace PIN data

Start with the encrypted PIN block and follow it. Record each point where it enters your environment and each organizational boundary it crosses. Record each cryptographic boundary where it is translated from one protection domain into another and the point where it leaves your control entirely.

For the hypothetical acquirer, that trace produces at least four handoffs on the POS path alone and a different set on the ATM path, where the encrypting PIN pad and the ATM managed service provider belong to someone else's operations team, as does the remote key loading process. Write down who performs each step, not just which system does.

Start building your financial platform?

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

Get in Touch →

Inventory systems and services

List what exists, at the level of component and service, and stop there. The inventory is a scope artifact, so it needs completeness rather than depth.

  • POI devices by model and approval class, with ATM encrypting PIN pads listed separately from attended POS

  • Switching and transaction processing components and HSMs with firmware versions

  • Facilities housing cryptographic devices and the networks carrying PIN traffic

  • Third-party services covering key injection and terminal management

Anything you cannot name an owner for goes on the list anyway, flagged. An unowned component is a finding you found yourself, which is the cheapest kind.

Assign control owners

Map every component and process to a named internal team, then to the contract or schedule that defines the service provider's obligations. Add the evidence source for each control, because a control nobody can evidence is indistinguishable from a control that does not exist. Document the key management responsibilities at the same time.

The valuable column is the last one: unresolved shared-responsibility questions. Who verifies tamper inspection on terminals a PTSP maintains? Who holds the custodian records for keys injected at a facility you do not operate? Leave those open and visible rather than resolving them optimistically.

Test evidence against reality

Documents drift. The test is whether the document describes the system you run. Pull each item below and compare it against interviews with the people doing the work and direct observation of a key ceremony or a terminal deployment.

  • Network and data flow diagrams and key inventories with current custodian assignments

  • Device approval records and firmware versions checked against the PCI SSC listings

  • Written procedures for key generation and exchange along with loading and destruction, plus the responsibility records that name who performs each step

  • Access evidence for HSM consoles and key management tooling, plus change records covering the period under review

  • Third-party attestations, including PIN Attestations of Compliance, which the PCI SSC lists as valid for two years from the date the assessor signs

When a document and an engineer disagree, the engineer is right, and the document is your remediation item. That comparison is what makes a PCI PIN Security Requirements readiness exercise worth doing before a QPA arrives rather than during.

Close PCI PIN gaps

Most gaps that surface from this exercise are engineering gaps wearing compliance clothing. A key hierarchy that grew by accretion. A switch-to-HSM integration that authenticates weakly because it was built before anyone asked. Host commands enabled during a 2019 migration and never disabled.

EGS works on exactly this layer. Our engineers have written about how banks manage keys across HSM fleets at scale and about the key management lifecycle from generation through rotation. They have also written about designing the software layer between a payment application and the hardware security module, where a misconfigured environment can hold a valid certification and still expose keys at runtime.

That last point is where this work gets genuinely technical. Investigating an integration gap means reading code paths and host command sets.

Structure the engagement

Keep the engineering work and the assessment work in separate hands. A QPA validates and attests, and the PCI SSC is explicit that enforcement of compliance programs sits with the payment brands, networks or acquirers rather than with the assessor. EGS does not perform that validation, and that separation protects you.

  1. Architecture review against the completed worksheet, with the PIN trace confirmed by observation rather than by diagram

  2. Responsibility mapping across internal teams and service providers, with every open shared-responsibility question written down

  3. Remediation planning sequenced by dependency, because key hierarchy changes gate most of the other work

  4. Implementation and testing, coordinated with your QPA so evidence is produced in a form the assessment can use

Run the sequence before the assessment window. Remediation under assessment pressure costs more and produces thinner evidence against the PCI PIN Security Requirements.

Plan the next step

Scope slips because production changes faster than documentation, and because the boundary between your controls and your providers' controls was never drawn precisely in the first place. Map the trace and name the owners so you can test every document against what the systems actually do.

Closing what that exercise finds is engineering work, and it is where PCI PIN programs succeed or stall. Discuss your PIN-processing environment with EGS and identify the engineering work needed to support your compliance program. Book a call with the engineering team to plan the next step.

Start building your financial platform?

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

Get in Touch →

Treat the mismatch as a scope issue, not a documentation edit. Re-trace the encrypted PIN block, identify changed systems and providers, assign control owners, and record the evidence that confirms each boundary. This process keeps your pci pin scope aligned with the environment that actually processes transactions.

Review them whenever a provider, contract, terminal model, processing route, or key-loading process changes. Include the review in your change process and annual readiness work. Compare contract schedules with interviews and observed operations, then document who owns inspections, custodian records, incident handling, and evidence collection.

Not automatically. An approval applies to the listed device and firmware combination, while your configuration and integration remain your responsibility. Check the firmware against the PCI SSC listing, review enabled commands and administrative access, and retain the approval record, configuration review, and change evidence for assessment.

Retain the approved procedure, ceremony date, participants, custodian assignments, key components or key blocks handled, system records, and destruction confirmation. Add access logs and an observation record that shows the procedure matched production. Store the evidence with the related key inventory and service-provider responsibility records.

No. EGS can review architecture, map responsibilities, plan remediation, and prepare evidence, while a Qualified PIN Assessor performs the independent validation. Keeping those roles separate reduces conflicts and gives the assessor a clear record of what changed, who tested it, and how the environment operates.

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.