Common Errors

Common Errors | Quasar Store

Run this in the server console. It reports which of the four access routes is shut for that player and why — it does not guess:

lua

qs-billing:checkadmin <server id>

If the server already has an admin on record, the access screen is no longer offered to everyone. Open it with /billingadmin.

If you are setting up a brand new server and missed the code, restart the resource — the one-time code is printed at boot whenever no admin exists yet.

The wrong framework or inventory was detected

Read the boot summary in the console — it prints one line per integration with what was chosen. Two candidates running at once means the first in the priority order wins.

Set the value explicitly in config/shared/config.lua and it will be reported as (manual):

lua

Config.Inventory = 'ox_inventory'
Config.Framework = 'qb'

The other cause is load order: the adapters resolve when billing starts, so a resource that starts after it is never seen. Make sure your framework, inventory and target all ensure before qs-billing.

The app is nowhere on the phone

On both phones it is App Store only, by design — a player who never gets an invoice should not carry the icon. Open the phone's App Store and install Billing from there.

If it is not in the store either, the phone never accepted it. The server console says which:

bash

[qs-billing-app] Custom app registered
[lb-billing-app] Custom app registered

And check you started the right one: qs-billing-app is for qs-smartphone and lb-billing-app is for lb-phone. Each waits forever for a phone that is not running, quietly.

The console prints addCustomApp failed

The phone refused the registration and the line carries its own reason. The usual causes, in order:

The phone resource is not named qs-smartphone or lb-phone. The app reaches its phone by that exact name.
Another custom app already registered the id qs_billing.
Both apps are running at once. Install only the one for the phone you use.
The phone is an older build without the custom-app API.

Restarting the phone is safe to try: the app registers itself again on every phone start, because a phone forgets its custom apps when it restarts.

The app draws over the game instead of inside the phone

Only lb-billing-app can do this, and only if its files were edited. lb-phone needs the app to declare a ui_page, which is also a full-screen layer loaded from the moment the resource starts. Two things keep it invisible — a rule in ui/build/index.html that hides the page, and the app rendering only once lb-phone tells it to.

Reinstall the resource from the download rather than patching it. qs-billing-app has no ui_page at all, and adding one to it would cause exactly the same thing.

The app opens but every screen is empty

The app holds no data of its own — every screen asks qs-billing. An empty app almost always means billing is not answering:

qs-billing is stopped, errored on start, or named something else.
ox_lib is not started. Both apps reach billing through ox_lib callbacks.
Billing is still booting. Give it a moment and reopen — it reloads every time the app is opened.

Players complain the app charges more than the terminal

It does, and that is the electronic payment fee working as intended: paying from the phone is a remote payment, exactly like paying from the tablet, and the terminal is the one place the fee is not charged. The app names the fee on the paying screen and the button shows the real total, so nobody is charged a number they did not see.

If you do not want that trade-off, turn the fee off in Creator → General. If you do want it, make sure there are terminals to walk to — a fee with no cheaper alternative is just a price rise.

Nobody can create an invoice

No job and grade has the issue permission yet. Open Creator → Jobs, add the job, and tick Issue on the grades that should be able to bill.

If the permission is set and it still refuses, check whether on-duty is required — an off-duty employee is told so in the Create view.

Invoices vanish into an approval queue

They are drafts, not lost. The amount is over that grade's approval threshold, so it waits for somebody with the Approve permission to sign it — the customer never saw it.

Raise the threshold in Creator → Jobs, or give somebody the Approve flag. The company view shows the queue, and the Admin panel warns when drafts have been waiting more than a day.

Blocked services are not blocking anything

Billing does not enforce it — your resources ask. Adding garage to a collection stage only records that the service is blocked for that player. Your garage has to check:

lua

if exports['qs-billing']:IsServiceBlocked(identifier, 'garage') then return end

The name you check must match the one you typed into the stage, exactly.

Players are being charged a fee they cannot avoid

The electronic payment fee is on and there is no terminal anywhere to walk to. The fee exists to reward paying in person, so without a single machine it is just a tax on everybody.

Place at least one terminal, or turn the fee off in Admin → Features. The Admin panel flags this exact combination in its Needs you list.

Money is being taken from players without warning

The seizure collection stage is enabled. It ships disabled for exactly this reason: it takes what is owed out of a bank account the next time the player connects, and players experience that as theft unless your server told them it exists.

Turn it off in Creator → Collections, or keep it and announce it. Every collection action is logged to the dunning webhook, which is the channel to watch for a week after changing these settings.

Key	Means
`error.booting`	Billing has not finished loading its settings. Retry in a moment.
`error.no_lines`	The invoice had no valid line items. Check your `lines` table.
`error.amount_too_low`	Below the minimum invoice set in the Creator.
`error.amount_too_high`	Above the maximum invoice, or above that grade's limit.
`error.no_permission`	The job and grade are not allowed to do that.
`error.permit_required`	This server licenses billing and the player holds no permit. Only appears with Creator → Permits turned on.
`error.player_too_far`	Proximity is required and the target is out of range.
`error.invalid_interval`	A recurring interval outside 1 to 8760 hours.
`error.feature_disabled`	That feature is switched off in Admin → Features.
`error.rate_limited`	Too many calls too quickly. Every callback is rate limited.

Installation and Access#

Common Errors

Common Errors

Installation and Access#

Items and Paperwork#

The Phone Apps#

Billing and Collections#

Error Keys#