Skip to main content
—
Framework library
Framework module · pci-pin-security-3-1

PCI PIN Security Requirements

PCI SSC's requirements for the secure management, processing, and transmission of personal identification number (PIN) data during payment transactions.

v3.1 · PCI Security Standards Council — PIN Security · published 2021-03-12

Standing today
Directory entry

00Answer

from the registry record
What is PCI PIN Security Requirements?
PCI SSC's requirements for the secure management, processing, and transmission of personal identification number (PIN) data during payment transactions.
Who does PCI PIN Security Requirements apply to?
PCI PIN Security Requirements applies to payments, global, per PCI Security Standards Council — PIN Security.
What is the current version of PCI PIN Security Requirements?
The current edition is v3.1, issued by PCI Security Standards Council — PIN Security and published 2021-03-12. Source: https://www.pcisecuritystandards.org/standards/pin-security/.
What does an assessment under PCI PIN Security Requirements require?
No control catalog has been ingested for PCI PIN Security Requirements yet — the registry tracks it as planned (Tracked metadata: we name the regime and monitor its issuing authority. No control or requirement model is implemented), so an assessment under this framework currently requires the authority's own catalog rather than a ControlFrame-parsed one.

01Standing

Directory entry

Authority and version facts, with a parsed public catalog when available; no tenant blueprint or executable evidence method is activated.

PCI PIN Security Requirements is tracked in the registry — authority, version ledger, verification — and nothing else is modelled for it yet. Import its catalog to begin.

Freely downloadable from PCI SSC; PCI SSC's terms permit identifiers and structure, not verbatim requirement text, without a separate license.

Request this frameworkAuthority source (opens in a new tab)

02Registry record

checked 2026-09-06
Registry status
Planned · namedTracked metadata: we name the regime and monitor its issuing authority. No control or requirement model is implemented.
Control units
Not on record — no catalog ingested and no authority-published count cited.
Control families
PIN processing · Key management · Device security · Personnel management
Applies to
payments · global
Verification
Secondary — corroborated across independent sources; the authority blocks automated fetch or does not state it plainly. checked 2026-09-06

03Version ledger

2 editions
v3.0Supersededdate not published
v3.1Current edition · supersedes v3.02021-03-12

05Change history

Full tracker
  1. 2021-03-12
    PCI PIN Security Requirements v3.1 supersedes v3.0 and is the current edition.

06Related frameworks

scored from registry facts
  1. PCI Card Production and Provisioningv3.0

    Also applies to payments · PCI SSC's physical- and logical-security requirements for card production and provisioning facilities (two companion documents under one program).

  2. PCI Contactless Payments on COTS (CPoC)v1.0

    Also applies to payments · PCI SSC's standard for accepting contactless card payments on a commercial off-the-shelf mobile device without a separate secure card reader. In its formal sunset window now, with MPoC as the designated successor.

  3. PCI Point-to-Point Encryptionv3.2

    Also applies to payments · PCI SSC's standard for validated point-to-point encryption solutions that can reduce a merchant's PCI DSS scope. Part of the payments family beyond bare PCI DSS.

  4. PCI Software-based PIN Entry on COTS (SPoC)v1.1

    Also applies to payments · PCI SSC's standard for accepting PINs on commercial off-the-shelf mobile devices via a software-based PIN-entry application. In its formal sunset window now, with MPoC as the designated successor.

See control-level overlap in the Control Atlas
PCI PIN Security Requirements | ControlFrame