Payment service providers must apply Strong Customer Authentication when a payer accesses a payment account online, initiates an electronic payment transaction, or carries out an action through a remote channel that may imply a risk of payment fraud.
This control maps to 2 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.