How do you process payment card transactions?
This is application question 107 of 121 on the Munich Re MRS Insurance Application Cyber Risk. It is a control question and reaches 7 controls. The wording is the carrier's, quoted verbatim.
Held from the Insurance Application - Cyber Risk (UK) (read 2026-10-11), jurisdiction United Kingdom. All Munich Re questions.
Facets: control: How do you process payment card transactions?; population: transactions
What this question reaches
- ISO 27001:2022 A.8.24: Use of cryptography (direct)
Establishes the card-payment control asked about; it does not establish card-data compliance in place of a merchant assessment.
Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment - ISO 27001:2022 A.5.15: Access control (supporting)
Establishes the card-payment control asked about; it does not establish card-data compliance in place of a merchant assessment.
Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment - SOC 2 CC6.1: Logical access security over protected information assets (direct)
Establishes the card-payment control asked about; it does not establish card-data compliance in place of a merchant assessment.
Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment - SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal (supporting)
Establishes the card-payment control asked about; it does not establish card-data compliance in place of a merchant assessment.
Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment - NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected (direct)
Establishes the card-payment control asked about; it does not establish card-data compliance in place of a merchant assessment.
Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment - PCI DSS 4.0 Requirement 3: Protect Stored Account Data (direct)
Establishes the card-payment control asked about; it does not establish card-data compliance in place of a merchant assessment.
Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment - PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks (supporting)
Establishes the card-payment control asked about; it does not establish card-data compliance in place of a merchant assessment.
Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment
Subject: payment_cards. Owner a broker routes it to: Payments and compliance owner.
The same control on other applications
Coalition Q3, Coalition Q4, Chubb Q7, Chubb Q9, Hiscox Q3, Hiscox Q5, Hiscox Q7, Hiscox Q8, Hiscox Q24, Hiscox Q59, Hiscox Q60, Hiscox Q61.
Map your own answers in the tool. See the Munich Re page, the controls index, the island and the answers.