A politically exposed person is anyone holding or having held a prominent public function, with the label extending to family members and close associates. For crypto teams the work is a five-step loop: identify who is in scope, screen them, tier the risk, monitor for change, and record the decisions. This hub maps the loop and links a guide for every stage.
The page reads in the order teams usually meet the problem. First what the term means and why regulators care, then the requirements at a glance, then how screening actually works in practice. Finally comes the full family of guides: seven pages that each take one stage deep, three neighboring hubs on this site, and four published explainers on the definitions behind it all. If you are building a program from zero, read top to bottom and open each guide as its stage becomes your problem. If you are answering one specific question today, the table of five steps and the family list below are the fastest way in.
What Is a Politically Exposed Person?
A politically exposed person is a natural person who is or has been entrusted with a prominent public function. The definition comes from FATF and covers senior roles: heads of state and government, ministers and members of parliament, senior judges, ambassadors, central bank board members, and directors of international organizations. It explicitly excludes middle-ranking and junior officials. The label is a risk classification, never an accusation.
The source text is FATF guidance on PEPs (Recommendations 12 and 22). Recommendation 12 defines the category and the duties financial institutions owe it; Recommendation 22 extends comparable expectations to other covered businesses. The FATF wording is careful on one point worth repeating inside any program document. The requirements are preventive in nature, not criminal, and should not be read as saying that politically exposed persons are involved in criminal activity.
Three types cover the field, foreign, domestic, and figures at international organizations, and how each one obliges you to act is the classification guide's ground. The scope then extends through relationships, family members and close associates, because assets controlled through those ties are a classic pattern in corruption cases.
Two boundary questions come up constantly. The first is seniority: the definition attaches to prominent functions and explicitly skips middle-ranking and junior officials, so a senior central bank board member counts while a desk officer at the same institution does not. The second is time: leaving office does not erase the status, and the EU keeps a former officeholder inside the risk scope for a window set at a minimum of 12 months. Influence and ill-gotten assets both outlast the title. Both boundaries are judgment areas, which is why the classification guide in the family below walks them with examples.
Jurisdictions color the definition differently at the edges. The European Union wrote domestic officials directly into its anti-money laundering directive, while other jurisdictions concentrate on foreign officials and treat domestic exposure as a risk-based call. How the types differ, and what each one obliges you to do, has its own guide in the family below. If you want the definitional layer in full, the four explainers listed under Related Guides cover the term, the definition, the three types, and how the major frameworks word it differently.
Why PEP Risk Matters in Crypto Compliance
The risk is position applied to money. Public office gives a person influence over contracts, budgets, and approvals, and where that influence meets weak controls, bribes and diverted state funds follow. Crypto inherits the same exposure with an extra layer: wallet addresses do not carry names, and funds can move across chains in minutes.
For a crypto business the exposure is concrete in both directions. A customer who is a politically exposed person brings source-of-wealth questions that pseudonymous onboarding does not answer by itself. And funds that originated in corruption can arrive at your platform already layered, which means the onboarding stage is often the only checkpoint you control cleanly.
Regulators have closed the distance between crypto and traditional expectations. FATF standards for virtual asset service providers pull VASPs into the same AML framework banks already operate under, PEP duties included, and licensing rules write those duties into their conditions. The practical translation: a crypto compliance team answers the same questions a bank compliance team answers, usually with fewer staff.
The label itself deserves one more sentence, because teams misread it in both directions. Calling someone a politically exposed person is not a claim that they are corrupt, and treating the label as an automatic refusal contradicts the preventive design of the rules. What the classification says is narrower and more useful: this person's position creates conditions where misuse could happen, so the relationship needs stronger checks than an ordinary customer file. The entire five-step loop exists to turn that one sentence into a repeatable process.
What happens when the answer is no program at all is easy to picture, because the failure mode is structural. Nothing determines whether customers are politically exposed, enhanced measures never reach the relationships that required them, and no records show who decided what. Where regulators find those gaps, the penalties are the visible part, and the operational aftermath usually costs more. Remediation programs arrive imposed from outside, licensing conditions tighten, and every future decision gets reviewed by someone who no longer trusts the file. Building the five-step loop before anyone demands it is the cheap version.
PEP Screening Requirements at a Glance
The duties stack into five steps, and each step has a dedicated guide in this family:
| Step | What it means | Guide |
|---|---|---|
| 1. Build a risk profile | Write down where PEP exposure concentrates in your customer base | PEP screening: the process |
| 2. Screen | Check each customer, beneficial owner, and business partner against PEP scope | How to run a PEP check |
| 3. Tier and respond | Confirm matches, assign a risk tier, apply the right measures | PEP risk tiers |
| 4. Monitor | Re-screen on a cycle and react when statuses change | PEP monitoring |
| 5. Record | Keep the judgment trail that answers a regulator | PEP screening requirements |
Step five deserves its own sentence, because it is where inspections are won or lost. The duties themselves, from senior management approval to source of funds checks, live in FATF Recommendation 12 and its national translations. The US customer due diligence rule treats PEP status as a risk factor inside four core requirements. US regulators confirmed in a 2020 joint statement that the rule does not itself require PEP screening; the status is handled through risk-based customer due diligence. What regulators test is rarely whether you screened. They test whether the file proves you screened, reasoned, and decided. The PEP screening requirements guide covers the duty set and the enhanced due diligence measures behind it, step by step.
One reading tip for the table: the steps are a loop, not a line. Step four feeds back into step two, because a re-screen is the same screen run again under new circumstances. Step five wraps the other four, because every step leaves the records that step five owns. Teams that treat the five steps as a one-time onboarding sequence are the teams that fail the re-screening question, because they stopped watching after the first pass.
The table also doubles as a staffing map. Step one and step three belong to policy owners, because they set rules the whole institution follows. Step two and step four belong to operations, because they run daily and their volume scales with the customer base. Step five belongs to whoever faces the examiner, usually the money laundering reporting officer. When a program feels understaffed, the table tells you which step is thin, and the guide behind that step tells you what the minimum defensible version looks like.