External review package4 checks remaining
Reviewing- Policy in force
- Evaluating
- Supporting evidence
- Queued
- Accountable authority
- Queued
- Decision history
- Queued
Less time piecing the case together.
Bring policy, evidence and checks together around payments that need review, so people can focus on the judgement.
Give the reviewer a better decision to make.
Bring the evidence together
See the relevant policy, payment context and evidence without reconstructing the case across systems.
Automate repeatable checks
Apply approved requirements consistently while exceptions and ambiguity stay with people.
Keep the outcome explainable
Record what was assessed, what required judgement and who had authority to decide.
One payment, from review to outcome.
A fictional payment has been held because the normal path cannot settle the case.
- Payment submitted for releasePayments system
- Evidence assembledCase context
- Approved checks appliedPolicy criteria
- Human judgement requiredOperations analyst
- Authorised outcome recordedDelegated authority
- Decision Receipt createdPolicy and evidence linked
Start manual. Add automation where it helps.
Manual
People gather evidence and decide.
Assisted
Agents prepare the case.
Connected
Systems provide evidence and repeatable checks run automatically.
Agentic
Routine decisions operate within explicit authority; exceptions go to people.
The policy, evidence and authority remain explicit as the process changes.
A decision that really matters.
APP fraud review
APP fraud reviews bring policy, evidence and judgement together. We have used synthetic cases to explore how checks, findings and outcomes can be recorded and revisited. This work has not measured customer outcomes.
Keep the evidence behind the decision.
A Decision Receipt keeps the policy version, supplied evidence, assessment and recorded outcome together so the team can return to the decision later.
Related receipts can be linked across a review, giving people and agents a connected history rather than isolated log entries.
4 checks remaining
Signed authorised push payment (APP) fraud exampleInspect the decision recordOpen the identifiers, signing key and transparency record behind a synthetic fraud review.+
Signed sandbox exampleIllustrative payment release
Synthetic payment-release example; no customer data.
See what a Decision Receipt records- Receipt ID
- 747a7983-6b8b-45fc-a8b8-ebfb64edfd53
- Decision
- ALLOW
- Policy snapshot ID
- 2e3d955d-6fc8-4cdc-b2c7-6161e942e752
- Timestamp
- 2026-08-13T06:17:48.482Z
- Rules evaluated
- 4
- Signature kid
- meshqu-sandbox-2026-06 · ed25519
- Transparency anchor
- rekor.sigstore.dev · log 2447666518
Map a decision with 
Ready when you are
Tell Qu about one decision that matters.
Bring one payment decision.
Show us one approval, hold, exception or reimbursement decision where the answer is spread across systems or requires judgement.
We’ll show you how MeshQu can put policy, evidence and authority around it.
