> ## Documentation Index
> Fetch the complete documentation index at: https://storekit.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Lightspeed Pay at Table
> Let guests scan a QR code, see their live Lightspeed K-Series bill and pay it from their phone — including partial and split payments, gift cards, and adding orders to an open bill.
With pay-at-table, a guest scans the QR code on the table, sees the open Lightspeed bill, and pays it (or part of it) from their phone. storekit takes the payment and reports it back to Lightspeed against the bill.
## How It Works
```
Guest scans the table QR code
↓
storekit fetches the open Lightspeed check for that table number
↓
Guest sees the live bill — items, service charge, discounts, amount due
↓
Guest pays all or part of it
↓
storekit reports the payment to Lightspeed against the check
↓
Lightspeed webhook confirms the payment → bill updated, closed when fully paid
```
The bill is kept in step with Lightspeed, so items added at the POS, payments taken on a POS terminal and changes to service charges or discounts are reflected on the guest's phone. Tax lines are synced with the check so the totals match the POS.
Pay-at-table needs the tables to match the POS. Import them first — see [Dine-in: Floor Plan & Tables](/docs/guides/integrations/pos/lightspeed/dine-in).
## Settings
On **Stores** → your store → **Settings** → **Integrations** → **Lightspeed K-Series**:
* **Payment Method PAT** — the Lightspeed payment method used for pay-at-table payments. If nothing is selected, storekit reports the payment as `APM`.
* **Gift Card Payment Method** — used instead of **Payment Method PAT** when the guest pays with a gift card or loyalty credit, so those settlements are reported separately in Lightspeed.
**Payment Method** (used for online orders) and **Payment Method PAT** are separate settings — keeping them as separate Lightspeed payment methods makes reconciliation much easier.
## Partial and Split Payments
Guests can pay part of the bill, and several guests can pay the same bill from their own phones. Each payment is reported to Lightspeed individually with its own reference and tip amount, and storekit closes the bill once the amount due reaches zero. Payments taken on the POS terminal in the meantime reduce what the guest is asked to pay.
If a payment fails, storekit marks it failed with the Lightspeed reason and flags the bill so staff can settle it on the POS.
## Adding Orders to an Open Bill
When **Add to bill batching for all orders** is on, in-store orders placed at a table in an area that accepts pay-at-table are added to that table's open Lightspeed check instead of creating a new order, and the **Add to Bill** account profile is used. Guests can then order several rounds and settle everything at once.
How storekit finds the bill:
* If storekit already has an open bill for the table, it confirms the check still matches in Lightspeed and adds the order to it. If the check has gone (settled at the POS), the stale bill is closed.
* If no bill exists yet, storekit waits briefly and re-checks Lightspeed so that two orders placed at the same moment go onto the same check rather than opening two.
Orders added to an existing bill are not retried if Lightspeed rejects them, and no payment is applied to the order itself — the balance is settled against the bill. Watch failed orders for these tables so a round doesn't go missing.
## Next Steps
Account profiles and order behaviour
Bill and payment problems
## Related topics
- [Lightspeed K-Series](/docs/guides/integrations/pos/lightspeed/overview.md)
- [Lightspeed Dine-in: Floor Plan & Tables](/docs/guides/integrations/pos/lightspeed/dine-in.md)
- [Pay at Table Overview](/docs/guides/pay-at-table/overview.md)
- [Toast Pay at Table](/docs/guides/integrations/pos/toast/pay-at-table.md)
- [Dine-In (Pay at Table)](/docs/getting-started/store-types/dine-in-pay-at-table.md)