CipherComply
Your exchange's answer to customer loss complaints. One hosted intake. One compliance dashboard. Every serious complaint handled. One signed monthly record.
The one-breath pitch
CipherComply gives an exchange a complete customer-loss complaint function under the CipherBlade name. It goes live without a software implementation and gives the compliance team one auditable place to intake, track, handle, and report every complaint.
The buyer
Chief Compliance Officer, MLRO, Head of Financial Crime, COO, or General Counsel at a tier-2 or tier-3 exchange.
The pain
Loss complaints arrive through scattered support channels. Deadlines, investigation records, response letters, and board reporting are inconsistent or missing.
The close
Open the call inside the prospect's pre-built branded instance. Start with a hosted complaints page or forwarding alias. No engineering ticket.
The promise
Complaint handling, not fund recovery. CipherComply creates the competent, timely, auditable record. Full investigations are separately scoped.
What every customer gets
| SURFACE | FUNCTION |
|---|---|
| Customer intake | Exchange-branded guided loss complaint form and acknowledgment. |
| Compliance dashboard | Queue, statutory clocks, jurisdiction requirements, escalation state, and audit history. |
| Handled complaint file | Structured facts, screening, fair-investigation record, response letter, sources, and review signature. |
| Monthly record | Signed complaint and FIU operations report for management, board, and examiner use. |
| CipherBlade escalation | Optional deep trace, exchange outreach, freeze coordination, and evidence package under a separate scope. |
Regulation already created the job
UK FCA / DISP
Formal complaint handling, fixed response clocks, auditable investigation, fair response, and escalation rights.
EU MiCA
CASPs need published, accessible, timely, and documented complaint-handling procedures.
US FinCEN
MSB obligations and fraud-information-sharing make complaint intelligence operationally relevant.
The honest boundary
These regimes do not require an exchange to trace every loss. We sell defensible complaint handling. Tracing is an optional investigative escalation.
Start with the reachable wedge
| RING | ACCOUNTS | ROLE |
|---|---|---|
| Tier-2/3 centralized exchanges | 80–120 | Immediate ICP and proof market |
| CASPs, custodians, wallets, OTC desks, ramps | ~500–1,500 directional | Same complaint function, wider crypto perimeter |
| PSPs, neobanks, remitters, payment firms | Several thousand | Longer-term fiat expansion |
First research cohort: MEXC, KuCoin, Gate.io, WhiteBIT, Bitget, HTX, Luno, VALR, BitMart, CoinEx, LBank, Phemex, BingX, Bitrue, AscendEX, ProBit Global, XT.com, Deepcoin, CoinW, Biconomy. Validate fit and relationships before outreach.
One product, priced by scale
| BAND | DIRECTIONAL MONTHLY PRICE | PRODUCT |
|---|---|---|
| Small | $499 | Everything included, fair-use volume |
| Medium | $999 | Everything included, higher operating volume |
| Large / multi-jurisdiction | $1,999+ | Everything included, custom capacity and controls |
Internal pricing direction for validation. Not an approved public rate card. Full CipherBlade investigations remain separately scoped, generally $5K–$50K.
Run the meeting in 20 minutes
- 2 min: Confirm jurisdictions, monthly complaint volume, and present process.
- 5 min: Open their pre-built instance. Show intake, clocks, and audit record.
- 5 min: Run one fictional complaint through handling and open the signed monthly report.
- 3 min: Explain hosted day-one activation. No software implementation required.
- 3 min: Offer a design-partner activation and choose the operating owner.
- 2 min: Set the activation date and technical handoff.
Say exactly what is true
| DO | DO NOT |
|---|---|
| Sell complaint handling, clocks, records, and defensibility. | Claim every exchange is required to trace funds. |
| Describe CipherBlade as the named complaint and investigation partner. | Promise recovery, freezes, legal outcomes, or regulatory approval. |
| Use fictional demo data and a prospect-branded preview. | Expose another client, victim, wallet, or complaint. |
| Scope jurisdictions and data residency before production. | Hold CipherComply out as the exchange's MLRO of record. |
Chris's assignment
- Get Justin's 20 strongest exchange relationships, ranked.
- Select three friendly design-partner prospects.
- Identify the compliance lead, MLRO/CCO, and COO at each.
- Pre-build each branded instance before the call.
- Close the complaint function first. Let investigation work emerge from real complaints.