COMPLIANCE PREVIEW — internal demonstration only. All data below is fictional. Not connected to real users, transactions, or accounts.
Compliance & monitoring

What the operator side is built to look like

A preview of the internal tooling a licensed BCXPesa would run day to day — transaction monitoring, an AML review queue, and audit exports. Every row here is fictional, built to demonstrate the shape of the system, not to report on anything real.

Transactions monitored
1,842
Last 30 days (sample)
Flagged for review
7
0.38% flag rate
KYC verified
96.4%
Within target range
Avg. review response
4.2h
Compliance officer SLA: 24h

Transaction monitoring

Sample feed — illustrative only
IDUserAssetAmountRiskStatusTime
TX-88213u_7f2a…b91cBTCKES 12,400LowCleared09:14
TX-88214u_c03e…1a4fUSDTKES 3,200LowCleared09:16
TX-88215u_44b1…7d2eBNBKES 89,000HighFlagged09:22
TX-88216u_9a8c…5f10LTCKES 6,750LowCleared09:25
TX-88217u_2e77…c60bBTCKES 41,300MediumPending09:31
TX-88218u_ab19…33e4USDTKES 2,000LowCleared09:33
TX-88219u_f501…88adBNBKES 118,500HighFlagged09:40

AML review queue

Flagged transactions awaiting a compliance decision
TX-88215 — KES 89,000 in BNB
u_44b1…7d2e · Reason: amount exceeds first-week threshold
TX-88219 — KES 118,500 in BNB
u_f501…88ad · Reason: velocity — 3 transactions in 10 minutes
TX-88190 — KES 54,200 in BTC
u_1cd9…f77a · Reason: new device, first transaction

Audit export

Seven-year retention, as required under the VASP Regulations, 2026

Generates a sample audit log export — the same shape a real export would take once this connects to actual transaction records.