United Scripts

United Fraud (Card Cloning & Check Fraud (ESX, QBCore, QBox)

United Fraud (Card Cloning & Check Fraud (ESX, QBCore, QBox)

This item is free.

Add to Basket

A full fraud career, not a menu with a progress bar.

Your player buys the gear off a dealer, sets it down on a desk, and works a

laptop that looks and behaves like a real machine. Every step costs stock, takes

time, and leaves something behind for the police to find. The money at the end

is decided by how well the job was done — never by the client.

THE JOB

1. BUY THE KIT

**A fence sells the laptop, a 5G hotspot, an MSR writer, a check printer, an**

**emboss press, USB drives, blank plastic and blank check stock. Rolling**

**purchase limits stop one player buying out the shop.**

2. SET IT UP

**Gear is placed physically with an arrow-key placement menu — the ghost**

**follows whatever surface is under it, so a laptop slides from the floor onto**

**a desk and stays there. It is a real prop in the world: anyone can see it,**

**and police can seize it.**

3. GET ONLINE

**The hotspot is the only way to a connection, and it is the weak link. Trace**

**climbs while it carries work and cools when it is idle. Let it top out and**

**it calls the police to its own location.**

4. PULL A BATCH

**A browser on the laptop downloads stolen card dumps onto a USB drive. One**

**batch per drive: a fresh pull wipes what was on it.**

5. CRACK A DUMP

**A minigame turns a dump into an identity — a name, a bank, a balance. How**

**cleanly it is cracked decides the tier of card it can produce.**

6. MAKE SOMETHING

**Write a card on the MSR and raise the digits in the emboss press (a flat**

**card gets eaten by the first machine that reads it), or print a blank check**

**on the printer. Both are minigames; a bad run ruins the stock.**

7. CASH OUT

**A card goes in an ATM. A check is written at a bank counter, in front of a**

**teller, for an amount you choose against the account behind it. Either can**

**be declined, kept, and called in.**

WHAT MAKES IT DIFFERENT

** THE SERVER DECIDES EVERYTHING. Each timed job is two calls with a one-shot**

token and the server's own clock. The progress bar on screen is cosmetic.
** THE MINIGAMES ARE SCORED ON THE SERVER. The server deals the board; the page**

only reports what the player did and the server replays it. Posting a

perfect score gets you a ruined blank, not a platinum card.

** CARDS AND CHECKS ARE HANDLES. Every value lives server-side. The item is a**

claim on it, so a card can be handed to a mule and used by them — possession

is what the ATM and the teller go by.

** ONE POT. A card and a check drawn on the same identity spend the same money.**

Drain it with plastic, and the paper is worth nothing.

** HEAT IS PER CHARACTER. It climbs with every risky action, decays while you**

are quiet, and the higher it sits, the more often a machine refuses, and an

alarm goes out. At the top, the whole job locks you out.

** POLICE HAVE SOMETHING TO DO. Alerts carry a code, a location, and a reason.**

Gear left out can be seized into an evidence stash, and the cards that laptop

wrote can be burned with it.

THE LAPTOP

Not a list menu — a desktop. Lock screen, menu bar, dock, windows you can drag,

stack, minimise and zoom, five wallpapers and five accent colours saved to the

character. Apps: a browser for pulling batches, a decrypt terminal, the card

writer, the check forge, a wallet, the USB drive, the signal/trace panel, a heat

readout and settings. Battery drains while the lid is open.

DISCORD LOGS

Five channels — money, production, gear, police and security — each with its own

webhook or all on one. Queued, batched, and rate-limit safe, so a busy server does

not silently lose lines. Every entry names the player, the character, and who made

the card. The security channel catches refused requests and exploit attempts.

/scamwebhook sends a test line and prints exactly what Discord answered.

COMPATIBILITY

Framework ESX, QBCore, QBox, or standalone. Anything else through a config

         **adapter — no file edits.**

Inventory:    ox_inventory, qb-inventory, qs-inventory, codem, origen, tgiann,

         **core\_inventory, the framework's own, or a built-in JSON fallback.**

Target ox_target, qb-target, or a plain [E] prompt with no target resource

         **at all.**

Dispatch ps-dispatch, cd_dispatch, qs-dispatch, linden_outlawalert,

         **core\_dispatch, rcore\_dispatch, origen\_police, ak4y-dispatch,**

         **0r\_dispatch, wasabi\_police, emergencydispatch, lb-phone,**

         **united\_dispatch — plus a custom function hook. With none of them**

         **installed, officers still get a notification and a blip.**

Notify ox_lib, or your own notification resource through one config hook.

WHAT IS INCLUDED

** The resource, with every setting in one commented config file.**

** Item definitions ready to paste for ox_inventory, qb-core, qs-inventory, and**

ESX SQL.
** Ten inventory images.**

** Three streamed props (the blank card, the MSR reader, the 5G hotspot) with**

stock GTA fallbacks for everything else, so it works on a stock server.

REQUIREMENTS

** ox_lib**

** A framework (ESX / QBCore / QBox) or standalone**

** An inventory with per-slot metadata is recommended — ox_inventory, qs, qb,**

codem, origen, or tgiann. Plain ESX works, with one limitation: the console

tells you about on startup.

OPEN AND LOCKED

Escrowed. Open for you to edit: the config, the Discord webhook file, the item

definitions and images, and the save folder. Everything else is protected.

SUPPORT

Discord: https://discord.gg/VvSnXeUxTR

Preview: [ YOUTUBE LINK ]

Back to category