10 controls
10 frameworks share controls with it
Singapore (MAS)
verified against its source document
Every control below is one this framework asks for. The right hand column counts how
many other frameworks in our corpus carry the same control, which is the difference between
doing this work once and doing it again for the next standard.
There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.
What you already have
Frameworks whose controls overlap this one, most first. If you run any of them, the
count is roughly what you have already evidenced.
Every control
| Code | Control | Also in |
|---|
PSN02-1 | Customer due diligence | 0 |
PSN02-2 | Suspicious transaction reporting | 0 |
PSN02-3 | Record-keeping requirements | 0 |
PSN02-4 | Sanctions screening | 10 |
PSN02-5 | Internal policies and training | 0 |
SGPSA-1 | Licensing for Digital Payment Token Services | 0 |
SGPSA-2 | AML/CFT Risk Assessment and Customer Due Diligence | 0 |
SGPSA-3 | Travel Rule and Wire Transfer Information | 0 |
SGPSA-4 | Cybersecurity and Technology Risk for DPT Service Providers | 0 |
SGPSA-5 | Customer Protection, Disclosures, Marketing Restrictions | 0 |
Tell me when Singapore Payment Services Act (PSA) files something new
One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.
What this page is
A control-level reference for Singapore Payment Services Act (PSA), drawn from our framework corpus. Control codes and
titles are references to the standard, not reproductions of it. The overlap counts and the
auditor artefacts are our own work and are the part you will not find elsewhere.
Measure this against what you already run ·
All frameworks · Today's edition