← All games

01 / PROJECT STORY · DESIGNER DIARY

Fraud Score

Inspect returned goods, find the evidence, and decide who gets a refund. Your employer wants you to keep the money.

01Inspiration

When I joined a team that worked on refund abuse prevention, a colleague introduced us with a joke: “We are the Abuse team… Just kidding, we're the Abuse Prevention team.” Our job was to stop customers from abusing the company's refund system. Sometimes, though, I felt that we were abusing the same system ourselves, at the customer's expense.

Fraud Score grew out of that experience. You work as a refund reviewer at the fictional company Meridian, reading claims, inspecting returned items, gathering evidence, and deciding whether to issue a refund under company policy. The company says “Every customer matters,” but evaluates reviewers by how much money they save. I built that conflict into the rules and left the decisions to the player.

Title screen
Title screen
The company homepage displays its service motto, refund spending, and review performance.

02Inspecting the items

The first workbench was almost entirely text. Policies, customer statements, and evidence appeared together, while the product and its animations occupied a small area. Players mostly read and selected text, with very little they could do to the item itself.

Text-based evidence · Marcus's case
Text-based evidence · Marcus's case
Physical inspection · Marcus's case
Physical inspection · Marcus's case
The same mouse case in two versions. The old version supplies the inspection findings; the new version gives the item more space and requires players to inspect it for evidence.

At that point, warehouse records already contained the inspection results. Players only had to select and combine them. Taking a cue from the way The Operator asks players to find discrepancies in photos and documents, I replaced those ready-made conclusions with evidence players had to discover. Order details and customer statements remained the starting point for each inspection.

I began with Marcus's mouse case. He says the USB receiver is missing and the mouse will not connect. The player has to pick up the mouse, turn it over, and open the bottom cover to find the receiver inside. Inspecting it lets the player check the claim directly.

Before implementing the physical inspection, I planned the interaction in a five-scene prototype: read the customer's statement, examine the mouse, record facts, and compare them with the order and policy. The original prototype is below; its steps are clickable.

Mouse case interaction prototype ↓
This five-scene prototype planned the case opening, turning the mouse over and opening its cover, recording facts, comparing the packaging, and verification feedback. It still used three columns and dedicated action buttons.
Open prototype ↗

Initially, the mouse had dedicated “Flip” and “Open cover” buttons beneath it. Because only this item had those buttons, they gave away where a clue might be hidden. I changed this to dragging the item to rotate it and clicking the cover to open it. Other items use the same controls, with an outline highlighting parts that can be handled.

Finding the receiver originally produced one small line of text in the bottom-left corner, which was easy to miss. I added a brief comment from the reviewer and a discovery notice before adding the record to the workbench. The notice initially disappeared too quickly, so I made it stay until clicked, giving players time to read it.

Inspecting the mouse · 7.3 seconds · silent
Drag to turn the mouse over, open the bottom cover, and find the USB receiver.

03Unpacking and recording evidence

Adding physical inspections to other cases introduced unnecessary unpacking. Some packaging layers and parts offered no information and had no bearing on the refund decision. Several objects could also respond to a click at once, making it easy to select something behind the outer layer. I removed unnecessary packaging and made items selectable only after they were exposed.

In the first case, the customer was supposed to return a kitchen scale but sent a timer instead. The original model also used a timer box, so the packaging gave no indication that anything was wrong. I changed it to a kitchen scale box with a larger recess. The smaller timer now sits in a space it clearly does not fit, suggesting that the wrong product was returned.

Before · timer packaging
Before · timer packaging
After · kitchen scale packaging
After · kitchen scale packaging
Packaging prototypes. In the kitchen scale box, the size difference between the timer and the recess suggests that the wrong item was returned.

This case also produced duplicate records. Clicking the timer yielded “Timer in the kitchen scale recess,” while examining the recess yielded “S1 scale absent.” Both observations meant that the scale had not been returned, yet they were recorded as separate discoveries, and only one could be used for verification.

I combined them into a single “scale absent” record. “The item received is a T1 timer” remained a comment during inspection. This kept the feedback without making players guess which of two similar records was valid.

Revising the evidence records
Revising the evidence records
Both original discoveries meant that the kitchen scale had not been returned. Combining them produces one usable evidence card.

04Making a decision

Even after physical inspection was added, players could skip the Customer File, gather records, and repeatedly try combinations of evidence and policy. Incorrect attempts had little noticeable cost, so they could find an answer without understanding why the customer had returned the item.

I changed the order of operations. The customer's statement and order record appear in the center first. After they have been read, the file moves to the left and the inspection bench opens. The policy handbook remains available during inspection, but evidence cannot be paired yet.

Once players end the inspection and move to the decision stage, they can use only the records they have collected. They cannot return to look for more. Verification requires selecting a policy and then two supporting pieces of evidence; an incorrect pairing costs extra time. These constraints encourage players to notice what evidence a policy requires during inspection and check their grounds for denial before submitting them.

Decision flow and action budget
Decision flow and action budget
Reading and inspection do not use action time. Players cannot gather more evidence after ending inspection. Verification and closing a case use the budget.

The web demo contains seven cases from the first shift, sharing a 42-minute action budget. The full game extends beyond this shift. Reading, rotating objects, and thinking do not use the budget. Verification and closing a case do, with incorrect verification costing more. Players can take their time inspecting, but repeated unsuccessful submissions have a cost.

Reaching a Fraud Score of 100 means the company permits a denial. It does not prove that the customer is a fraudster. Maya sent back a complete, unused kettle, but a medical emergency involving her child delayed her return by fifteen minutes past the deadline. Players can deny it under policy or approve the refund after considering her circumstances.

The closing report lists the facts the player found, the policies used, and the final decision, stamped approved or denied.

Closing report
Closing report
The denial report for Marcus's case lists verified evidence and the grounds for the decision.

05Art direction

Early scenes used rough, worn surfaces to convey an oppressive atmosphere, but they looked more like trenches or a post-apocalyptic shelter. That did not fit the setting I had in mind. The story takes place in 2060, with the protagonist reviewing refunds for a tech giant. I imagined an office routine similar to the everyday working life in The Matrix: clean, respectable surroundings and the same tasks repeated each day.

A revision with orderly blue panels went too far toward ordinary office software. After comparing several art styles and trying them in the game, I chose a hand-drawn approach, keeping paper, clipboards, and an inspection mat. Slightly uneven lines and coloring give the surfaces their drawn texture. I later reduced the curvature of the outlines and the strength of the wear textures so objects would not look distorted or excessively dirty.

Blue panel version
Blue panel version
Hand-drawn workbench version
Hand-drawn workbench version
The later version replaces blue panels with paper, clipboards, and an inspection mat, with revised outlines and wear textures.

The magic wand case adds some absurd humor. The player can actually turn the packaging into a pigeon. The reviewer says only, “Seems like it works...” and continues recording evidence, selecting policy, and processing the refund.

Next projectJukeBox