Description
A handheld point-of-sale script: a merchant aims at the nearest player, enters an amount and a method, the customer accepts, and the money moves cash or bank with the revenue booked to the merchant's society account. Servers buy it because nearly every vendor and shop job wants a clean billing prompt, and a two-party accept flow keeps it abuse-resistant.
Prompt Template
You are writing a FiveM resource for esextended (stable, exports getSharedObject).
The full prompt template and its reference Lua are part of a one-time pack. Pick your depth — both are lifetime access, no subscription, ever.
- 60 prompts + syntax-validated reference Lua
- Lifetime access — pay once
- All 510 prompts — the full library
- Per-prompt profit/trend intelligence (CSV + playbook)
- Lifetime free updates — new niches as the market moves
$49 for 60 · $199 for all 510 + intelligence — one-time, no subscription.
Expected Output
The reference Lua at content/expected-outputs/business/10-pos-card-terminal.lua implements a nearest-player lookup by server id, a /charge command with a phone animation, a two-step charge - accept…
The full prompt template and its reference Lua are part of a one-time pack. Pick your depth — both are lifetime access, no subscription, ever.
- 60 prompts + syntax-validated reference Lua
- Lifetime access — pay once
- All 510 prompts — the full library
- Per-prompt profit/trend intelligence (CSV + playbook)
- Lifetime free updates — new niches as the market moves
$49 for 60 · $199 for all 510 + intelligence — one-time, no subscription.
Known Failure Modes & Corrective Prompt
- No accept step — charging on the merchant request alone drains nearby players. Require the
pos:acceptround-trip. - Client-trusted balance — re-read
getMoney()/getAccount('bank')on the server before moving money. - Wrong player id — use
GetPlayerServerId, not the raw client entity, to target the customer.
Corrective re-prompt: Split the flow into pos:charge (relay a bill to the customer) and pos:accept (the customer confirms); in the accept handler re-read the customer's cash or bank balance server-side and reject when amount > balance, then credit the merchant society.
Framework Integration
ESX: native — getMoney(), getAccount('bank').money, esx_addonaccount:getSharedAccount('society_'..job).
QBCore: swap to Player.Functions.RemoveMoney('cash'|'bank', n) and exports['qb-management']:AddMoney(job, n); resolve with GetPlayer(src).
QBox: identical to QBCore via exports.qbx_core:GetPlayer(src) and qbx_management for the society credit.
Profit Potential
$130–$1600/mo on Tebex (expected ~$420). [INFERRED] priced inside the $50-389 standalone-script band against the signal-scraper corpus (tebex_snapshot n=100, median seller $11.85K/mo) for a stable card-terminal niche.
Trend Signal
→ stable — inferred: Card-terminal billing is a common low-complexity add-on; demand inferred from banking-RP adoption.
Sales Angle
Position as the universal billing terminal: every shop, mechanic and vendor job drops it in for cash-or-card payment with society payout. Recommended Tebex price: $59.
Difficulty & Ship Time
beginner · ships in 2-4h.