How does restaurant software integrate a tax API?
When the POS closes a bill, it sends the invoice to the tax API with the restaurant’s authority header. The gateway files it and returns a fiscal number and QR to print on the receipt, usually in well under a second. Branches in different provinces route to PRA, SRB or KPRA automatically.
Bill-to-receipt flow
Waiter closes the bill
↓
POS builds the invoice
↓
POST to TaxBridge
↓
Route to PRA/SRB/KPRA/FBR
↓
Fiscal number + QR
↓
Receipt prints
Implementation steps
Hook the settlement event
Call the API when a bill is finalised, not when it is opened.
Set the branch authority
Configure each branch’s authority so routing is automatic.
Print the QR
Render the returned qrCode on the thermal receipt.
Retry safely
Send an Idempotency-Key so a reprint or network retry never double-files.
Dine-in, takeaway and delivery
All order types file the same way. For KP restaurants on RIMS, your POS applies the reduced rate and TaxBridge files it as calculated. See the restaurant POS integration page.
Frequently asked questions
Which authority does a restaurant use?
PRA in Punjab, SRB in Sindh, KPRA in KP — configured per branch.
Is it fast enough for a busy counter?
Yes — fiscalisation is typically sub-second, and idempotency keeps retries safe under load.
Does it handle reprints?
Yes — store the submissionId and reprint the same QR; an idempotent resubmission returns the stored result.