Tap Pay
Troubleshooting
Troubleshooting
Common issues
| Symptom | Likely cause |
|---|---|
| Tablet doesn't open when the merchant uses the item | lb-phone not started, or the items.lua entry's client.export doesn't equal 'suty-billing.useTablet' |
| Notification "No tienes un negocio para usar esto" | Player's job isn't allowed by Config.AllowedJobs (or is in Config.ExcludeJobs). If you use origen_masterjob, qb-management, esx_society, or any SQL-backed dynamic job system, set Config.TrustPlayerJob = true — see Configuration → TrustPlayerJob. |
| Customer's app says "No hay terminal de pago cerca" | No merchant within Config.TerminalRange (default 2 m) has an active terminal — or the merchant is on a different routing bucket |
| Customer's bank doesn't change after payment | Confirm qbx_core / qb-core / es_extended is actually started and detected. Check the F8 / server console — should print [suty-billing] Bridge initialized — framework: ... at boot. |
attempt to index a nil value (global 'QBCore') |
Your framework resource isn't ensured before suty-billing in server.cfg |
Console prints Bridge: no supported framework detected |
None of qbx_core / qb-core / es_extended was started before suty-billing |
ESX + 'all' mode rejects every job |
Your ESX build doesn't expose ESX.GetJobs() — switch Config.AllowedJobs to the manual array form |
Bridge: Config.Framework = "qbx" but "qbx_core" is not started |
You forced a framework that isn't running. Either start the matching framework or set Config.Framework = 'auto' |
Verifying the install
Run these checks in order — each one should print the expected line in F8 / server console after a clean restart of suty-billing:
Bridge boot
[suty-billing] Bridge initialized — framework: qbx (auto)Means the framework was found and the resource is ready.
Item use
(merchant uses payment_tablet → tablet appears in hand, terminal NUI opens)lb-phone app present The Tap Pay icon shows on the phone home screen. If it doesn't, lb-phone was started after suty-billing — restart suty-billing.
Reporting a bug
If something's still broken after the checks above, open a ticket in our Discord with:
- Your server framework and version (QBX vs QB vs ESX, plus build number)
- The first 20 lines printed by suty-billing on resource start
- Whether
lb-phoneandox_inventoryare started before suty-billing inserver.cfg - Exact reproduction steps
