HKMA Issues PCICSO Code of Practice for Designated Payment System Operators
The HKMAHong Kong Monetary Authority issued a sectoral code on 10 June 2026 for payment system infrastructure operators designated as critical infrastructure operators under the PCICSO. Breaching the code is not itself an offence, but breaching a direction based on it is.
What happened
The Hong Kong Monetary Authority issued a code of practice dated 10 June 2026 under section 8(1)(b) of the Protection of Critical Infrastructures (Computer Systems) Ordinance. It applies to payment system infrastructure operators that the Monetary Authority designates as critical infrastructure operators. It covers category 1 and category 2 obligations. For category 3, operators go to section 7 of the Commissioner’s generic code.
What it changes
Section 1.1.5 says the code is not subsidiary legislation and that failing to follow it is not in itself an offence. The Monetary Authority may issue written directions where compliance is missing or defective, with reference to the code, and failing to comply with a direction is an offence.
- Section 5.3: the computer-system security management unit and its supervising employee need not be based in Hong Kong.
- Section 6.2: the security management plan is reviewed as circumstances require and at least once every two years.
- Section 6.3: the risk assessment covers all applications, hosts and network devices of the critical computer systems, and includes a vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. assessment and a penetration test.
- Section 6.4: an appointed assessor audits whether the plan is implemented and whether the controls comply with it.
Section 1.1.7 calls these baseline requirements and says operators should apply stronger measures in line with their risk.
Who is affected
Designated payment system infrastructure operators. The code does not name them, and we could not verify which operators are designated.
What to do now
- If you are designated, map your security management plan against sections 5 and 6.
- Check that your risk assessment scope covers all applications, hosts and network devices.
- Include a vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. assessment and a penetration test in that assessment.
- Appoint an assessor for the security audit, and keep the plan’s review date within two years.
Security Architecture Review
We would run the risk assessment across your critical computer systems, covering applications, hosts and network devices, and document the risks, tolerance levels and mitigation that section 6.3 asks for.
