HTML sitemap
Every file, in one place.
Direct links to the complete static site. No search script is required.
Home
Playbooks
- Safeguarding: build the evidence, not just the policy.
- Map the service before you choose the permission.
- An API application should describe a business that can operate.
- Consumer Duty: put the customer outcome in the board pack.
- Choose the payment rail. Then check the actual limit.
- Crypto regulation: keep today’s perimeter separate from tomorrow’s.
- A supervisory visit starts with a file someone else can follow.
- Test the service, not the disaster-recovery slide.
- Oversee the representative you actually have.
- A financial crime control needs an owner and a working test.
- Ten operating playbooks for UK payment firms
Wire
- Safeguarding reform: distinguish the regime from the implementation file.
- A monthly return needs a daily evidence trail.
- APP reimbursement starts with the scope of the claim.
- What to extract from a payment-infrastructure notice.
- A firm name is the beginning of a register check.
- Read the period, the requirement and the finding.
- The Wire: source notes on UK payment regulation
- FCA source desk
- PSR source desk
- BoE source desk
- HMT source desk
- Enforcement source desk
Tracker
Calendar
Tools
Register Check
Explainers
Enforcement
Glossary
- Safeguarding explained
- Relevant funds explained
- Reconciliation explained
- Resolution pack explained
- REP027 explained
- Authorised payment institution explained
- Small payment institution explained
- Electronic money institution explained
- Consumer Duty explained
- Fair value assessment explained
- Important business service explained
- Impact tolerance explained
- Severe but plausible scenario explained
- Appointed representative explained
- Financial Services Register explained
- Faster Payments explained
- CHAPS explained
- Bacs explained
- APP fraud explained
- Final notice explained
- UK payments compliance glossary