Skip to content
Verrin

Product

One workspace for everyrefund investigation.

Review the claim, order history, previous refunds, evidence and risk signals in one investigation — then record the decision and reasoning.
View pricing

How Verrin works

How a refund investigation works

Investigation · RC-20931Demo data

  1. Claim

    Item not received · Order #4821 · £184.00

  2. Order + history

  3. Risk signals

  4. Evidence

  5. Reviewer decision

  1. 01

    Refund claim enters review

    A suspicious refund request is opened for investigation.

  2. 02

    Verrin assembles the context

    The order, previous refunds, account context and relevant history are brought together.

  3. 03

    Risk signals are explained

    Verrin calculates a risk score and shows the individual signals that contributed to it.

  4. 04

    Evidence is reviewed

    Supporting evidence, reviewer notes and investigation events stay together in the timeline.

  5. 05

    The merchant decides

    The reviewer records the outcome and reasoning. Verrin does not automatically approve, reject or issue the refund.

Explainable risk scoring

See what movedthe score.

Review each contributing signal and its context. The score supports review; it does not decide the refund outcome.

Risk score · example

Illustrative

68 / 100

  • Repeat refund activity

    4 refund claims in the last 90 days

    +25

  • Recent account

    Customer account created 11 days before order

    +18

  • Claim pattern

    Same claim reason as 2 previous requests

    +15

  • Order context

    High-value order, delivered with carrier scan

    +10

Audit timeline

Know what was reviewed,and why.

See when the claim arrived, evidence was uploaded, notes were added and a decision was recorded.

  1. 01

    Claim received

  2. 02

    Signals computed

  3. 03

    Evidence uploaded

  4. 04

    Reviewer note

  5. 05

    Decision recorded

Repeat claimant analytics

Patterns across claims, not just one.

A single refund request may look ordinary. Previous claims can provide context that the current request does not.

Refund claim volume · 12 months

Demo data

Bars: claims per month · Line: refund value trend

Repeat claimant activity

Demo data

4 claims

Same customer, 90 days, across 3 orders. Repeat activity is context for review, not proof of fraud.

Claim type distribution

Demo data
  • Not received41%
  • Damaged27%
  • Not as described19%
  • Other13%

Capabilities

Everything relevant to the claim. In one place.

  • Order and refund history

    Review the order, line items and previous refund activity alongside the current claim.

  • Evidence management

    Attach supporting files and keep them with the investigation. New uploads are stored privately and malware-scanned before use.

  • Refund audit dashboard

    Track open, reviewed and recorded investigations across your store.

  • PDF and CSV exports

    Export investigation records and refund data for reporting and internal review. Growth plan and above.

  • Custom risk rules

    Choose which investigation signals matter to your store and how much they contribute. Growth plan and above.

  • Team workflows

    Assign reviewers and control who can review investigations and record decisions. Advanced roles on Scale.

Give every suspicious refunda proper investigation.

Review the history, evidence and risk signals before deciding what happens next.

View pricing View the investigation workspace