# APP reimbursement decisions

Canonical: https://www.meshqu.com/app-fraud

Connect policy, evidence and authorised human judgement around APP fraud reimbursement reviews. Make the basis for each decision easier to explain.

Build MeshQu into your reimbursement workflow to connect the policy applied, the evidence checked and the reviewer’s judgement. Keep a clear basis for explaining the decision.

## Clear checks. Accountable judgement.

Evaluate the case deterministically against the reimbursement policy in force. Make missing evidence and required human judgement explicit at decision time.

### Evaluate at decision time.

MeshQu applies deterministic rules against the policy version in force, returning a verdict and a signed record of the assessment.

### Keep judgement accountable.

Connect missing or contested evidence to an authorised reviewer. Keep their judgement and reasons alongside the policy assessment.

## A reported scam. A judgement to make.

A customer reports an £8,000 transfer to a caller posing as their bank. The evidence is incomplete. An authorised reviewer owns the reimbursement judgement.

Fictional example · no customer data

Policy: Reimbursement policy · fictional version 4.2

MeshQu policy assessment: Material facts incomplete; human review required

Decision authority: Authorised reimbursement reviewer

Evidence references: Customer report, payment event and contact evidence

Result: Unresolved in this illustrative scenario

The policy, finding and required authority stay connected. The reviewer’s judgement is recorded alongside when made.

This scenario is fictional and does not show a customer result.

MeshQu does not make a legal entitlement judgement.

Integration scope is agreed for the organisation’s workflow.

### Can we start with our existing policy?

That is the starting point: one policy and one decision workflow. We’ll explore how its requirements, responsibilities and evidence fit together.

### Can we build our own solution with MeshQu?

Yes. MeshQu is infrastructure your team can build on. A commercial agreement with MeshQu lets you implement it around your own workflows and user experience. We’ll scope the integration around how you intend to use it.

### How would MeshQu fit our current systems?

We’ll map where the decision happens and what needs to connect. The integration approach is scoped around your workflow.

### What happens when we get in touch?

We start with the review you want to improve, who owns it and what a useful first step would look like. You don’t need a finished brief.

## Decision Receipts: what the record contains

What is in a Decision Receipt, and what does it prove?

A Decision Receipt is a signed, replayable record of how a consequential decision was made, created at the moment it happens and verifiable afterwards with the necessary verification material and trusted keys.

It records the policy in force, relevant decision context, the outcome and integrity information needed to check later whether the signed record has changed.

It does not prove that the inputs were true, that the decision was correct or that the action was carried out.

Machine-readable: https://www.meshqu.com/knowledge/decision-receipts.json