Decision ReceiptTransaction DecisionDR-K7M9-2P4Q
Verified- Decision
- Approved by Risk Committee
- Policy
- Third-party risk — Tier 1, v7
- Evidence
- 3 attestations, 2 documents
- Integrity
sha256:0xdead…beef
Use casesAML decisions
Fraud and AML decisions you cannot prove.
Every day, millions of AML decisions are made. When asked to explain them, most organisations can't produce a verifiable Decision Receipt.
MeshQu changes that.
Signals
Transaction data
Customer profile
Risk signals
Watchlists
Device / IP
Decision
AML decision at execution
Approve · Block · Escalate
Proof
Decision Receipt
Verified
01The moment
A decision is made.
A rule triggers. A model produces a score. An analyst reviews the case.
A decision is made: Approve, Block, or Escalate.
Transaction flagged
Payment to new payee
- Amount
- £12,540.00
- Customer
- John D.
- Rating
- 87 High risk
ApproveBlockEscalate
02The failure
You are asked to explain it later.
Why was this transaction allowed? What rules fired? What signals were considered?
The answer is reconstructed from logs, dashboards, model outputs, case notes. It takes time. Sometimes hours. Sometimes days.
Reconstructing the decision…
- Search logs45 min
- Check rule outcomes30 min
- Review model output20 min
- Pull case notes30 min
- Build explanation60+ min
That's not proof.
03The reason
It was never captured at execution time.
AML systems are built to detect and act — not to produce a verifiable record of the decision itself. No Decision Receipt is produced.
The decision happens. The proof doesn't.
Signals received
Logs written
The gap
No verifiable proof captured
04The shift
Decisions should produce proof.
Not reports. Not narratives. Not reconstructed timelines.
A decision should leave behind a verifiable record at the moment it is made.
Signals received
Logs written
Decision + Proof
At execution
05At execution
Captured as it happens.
Most AML systems capture decisions after they happen.
MeshQu captures them at execution time.
After the fact is audit. At execution is control.
TRCUWA
MeshQu Decision Layer
Decision Receipt
Verified
06The receipt
Every decision produces a receipt.
A Decision Receipt contains the inputs, the policy applied, the rules that fired, the outcome, and the actor.
Signed. Verifiable. Replayable. No reconstruction required.
07A new layer
It works with what you already use.
Transaction monitoring. Fraud engines. Case management systems. MeshQu doesn't replace them.
Your systems decide. MeshQu proves.
TM
Fraud
Case mgmt
Watchlists
MeshQu
— receipt
decisionblock
policyAML-v4.1
actoranalyst
sealverified ◎
08Consistency
Every path produces the same proof.
Automated screening. Analyst review. Model-assisted disposition. It doesn't matter — every decision produces the same receipt.
Screen → review → disposition. The steps hash-link as they happen and seal when the case closes. A chain proves the workflow.
Automated decision
Rule + model
Analyst review
Case worker
Model-assisted
Score + override
Same receipt, every time.
09The result
You can answer while the question is fresh.
The receipt resolves in seconds — what happened, why, under which policy, with what inputs. Verifiable.
Asked
Why was this transaction allowed?
RCP-01H7M12B7G6SNP2 VerifiedResolved in 2.1 seconds
Does this replace our transaction monitoring or case management?
No. MeshQu captures the decision your TM and case-management systems already produce.
10Close
You already make these decisions.
The question is — can you prove them?
Decision AssuranceCapture every decision. Prove every time.