For platforms with coins, gifts and payouts
When the authority asks, answer from the pack — not from memory.
Government and police requests across countries, answered consistently, with a trail: who asked, what ran, how many rows, who approved the release. Then the daily brief, from rules your team signs.
- 1 table
- day × country tag × pattern — every figure in the brief is a projection of it
- illustrative
- 0 rows
- leave your warehouse — the case file is built inside it; only a receipt reaches us
- illustrative
- Your rules
- country list, thresholds and windows are elections a named person signs
- illustrative
What we heard
Two jobs, one deadline
Pain point 1
Government and police requests
Pain point 2
Activity in higher-risk corridors
The gap
Every report is rebuilt by hand, from SQL to spreadsheet to prose, with no trail back to the source.
It costs analyst hours, invites inconsistency between countries, and moves sensitive data into files that are hard to control.
Our core principle
Your data never leaves your warehouse. We bring the logic to it.
Read-only, always
Your rows never leave
No model computes a number
What we will not do. Decide which transactions are money laundering or suspicious, or which countries are high-risk — your rules, your list, a named person's sign-off. We do not decide what must be disclosed to an authority or under what instrument; that is counsel's. We compute, trace and explain; we do not judge.
Step 1 · map once
We map your warehouse to a compliance model
| Your tables (examples) | Mapped to | Used for |
|---|---|---|
| coin_purchases, payment_events | Money in | source of funds, card and rail checks |
| gift_events, transfers | Value movement | who sent what to whom, and how fast |
| payouts, withdrawals | Money out | cash-out speed and destinations |
| users, devices, kyc | People and links | linked accounts behind one actor |
| country, corridor | Country tag | thresholds and filing windows per country |
Mapping lives as reviewable definitions in your environment. When a table changes, we update the map, not the reports.
Step 2 · the flow
From your tables to the figure, every step on the record
Step 01
Request
Step 02
Query
Step 03
Case file
Step 04
Receipt
Step 05
Roll-up
Rulebooks and elections
Each figure is judged by the rule that asks for it
No regime has been verified for this use case. Every basis below is to be confirmed with your team — the first questions we ask.
Which authority, under what
Who receives the daily and weekly reports in each country, and whether the obligation is a statute, a licence condition, an agreement or internal policy.
No regime verified for this item — the first question we ask.
Legal basis for disclosure
What instrument accompanies a request, and whether a vendor's software may produce the unmasked case file at all — a question for your counsel.
No regime verified for this item — the first question we ask.
Where the data lives, and where it may go
Which warehouse, which region, which residency rules bind each country's data. Our agent runs where the data is.
No regime verified for this item — the first question we ask.
If a subsidiary is a licensed money transmitter
Then the quarterly Call Report applies to it, on the same daily series — the money-transmitter page covers that.
CSBS — Money Transmission Modernization Act § 7.01 (MODEL)
What we look for
Line items, patterns and the traps underneath them
Pattern kinds we can compute. Which apply, with which thresholds, is your election.
| Pattern | What it looks like in the data |
|---|---|
| Top-up, fast cash-out | Coins bought and value paid out through a linked account within an elected number of hours. |
| Gifting loops | Value circling among accounts that share devices, cards or payout destinations. |
| Structuring | Repeated amounts sitting just under a review or verification threshold you set. |
| Many-to-one funnels | Many small senders concentrating value on one recipient in a corridor you list. |
| New corridor | First activity on a corridor within an elected lookback. |
Step 3 · the output
Every line arrives with its trail
Short sentences instead of query output. Every figure links back to the rows in your warehouse that produced it, the rule it maps to, and the person who signed the interpretation.
- 2026-09-22 · US → NG · Top-up, fast cash-out · 14 of 2,310 · $61,300 — rule R-01, elected by A. Example (Head of Financial Crimes)
- 2026-09-22 · US → KE · Many-to-one funnel · 6 of 870 · $8,940
- 2026-09-22 · LB → US · Structuring · fewer than 3 of 412 · withheld (small cell)
- Week of 22 Sep · 3 requests received, 3 responded · refs R-091…R-093 · hashes attached
Step 4 · your team decides
The system drafts. People approve.
Head of Financial Crimes
Which countries, which thresholds, which windows — and who signs them
General Counsel
Who may approve a release to an authority, and what the receipt records
Data platform owner
Which systems hold the rows, and where the case file may be written
Counsel and the BSA Officer
Masked or unmasked case file — an election with a named sign-off
Nothing reaches a regulator or an authority without human approval. Every release records who asked, what was shared, who approved it, and when.
Security and control
Built for data that cannot move
Read-only, always
Your rows never leave
No model computes a number
A person confirms every mapping
Where the rules disagree, we say so
Proposed pilot
Eight weeks, measured by hours and traceability
Weeks 1–2
Weeks 3–6
Weeks 7–8
How we will measure it
- · Time from transaction to flag, and from request to approved release
- · Analyst hours per country report and per request
- · Share of reported figures traced to source rows
Pilot terms: the pilot fee is credited against a first year signed within 30 days. Every pack carries its own caveats on its cover; nothing is suppressed to make a figure look cleaner.
Talk to us
Answer the request from the pack
If this is on your desk, tell us what you are dealing with and we will reply within one to two business days.