The compliance layer for UK–Africa money transfers · UK–Nigeria first
Vervet watches your counterparties on the FCA Financial Services Register — agents, appointed representatives, partner firms — every night, and keeps an append-only record of every check, every change, and every quiet night in between. When your settlement bank asks “prove you were watching,” the answer is a document, not a scramble.
02:15 UTC · counterparties checked across 13 Register services · 1 critical, 1 medium · 27 quiet nights recorded · 1 missed run — shown, never hidden
Design laws, not features
Detection is a deterministic diff between Register snapshots — never a model's guess. Where AI drafts an impact note on a new regulation, it is labelled, held for review, and can never create a detection.
Append-only, including the quiet nights. “No change” is a result, and a night we failed to run is recorded as our gap — because evidence you can't trust in both directions isn't evidence.
The Register refreshes overnight. We report changes same-day and every record shows when it was fetched — we never claim to be faster than the source, because nobody can be.
What arrives, and when
A permission removed, a new appointed representative, a status change — detected nightly across 13 Register services per firm, batched into one dated email, worst first. No alert fatigue: that's the incumbent failure mode we exist to end, not reproduce.
Every Monday, whether or not anything changed: N counterparties checked on M of 7 nights, and what moved. A quiet week is a deliverable — it's the one your bank reviewer actually wants to see.
A print-ready document generated from the audit log: every night of the period, every change, every regulator publication, and the basis on which it was all recorded. Made to be filed in a board pack and handed to a de-risking review, unedited.
FCA publications and CBN circulars, checked nightly. New items get an AI-drafted impact note — relevance-graded, caveated, and clearly marked as advisory — so Monday's reading pile arrives triaged, not decided.
| Detected | Firm | What changed | Severity |
|---|---|---|---|
| 14 Aug · 02:31 | Example Payments Ltd FRN 000001 | Permission removed: money remittance | critical |
| 14 Aug · 02:31 | Example FX Ltd FRN 000002 | New appointed representative | high |
| 13 Aug · 02:29 | Example FX Ltd FRN 000002 | Firm status: Authorised → Authorised (restrictions apply) | medium |
Sample layout, illustrative firms. Every real entry links to the underlying Register record.
If you carry the liability
Your evidence burden doesn't pause on quiet weeks. Vervet turns “we keep an eye on the Register” into a dated, append-only record you can put in front of an auditor, a partner bank, or your own board — with the checks you didn't have to act on counted, not discarded.
If you carry the stack
One API key. A JSON API for the watchlist and change feed, email your compliance team already reads, and nothing to host. Onboarding is a pasted list of FRNs; your counterparties are baselined by the second night.
The pilot
90 days on your own counterparty list, cancel anytime. Your firms are baselined from the first night; alerts, the weekly digest, and the month-end record follow from your data, not a demo's.
opeyemi@vervethq.com