Take the payment where the customer already is.
Kshirapps builds the rail that reaches past the counter — to the table, the cage, the kiosk, the forecourt. It runs whatever checks that sale requires, then settles straight into your account.
Commerce software still assumes there's a counter.
Three things every operator has already felt, and none of them are solved by a better till.
The sale happens where the customer is
At a table, in a queue, beside a cage in the yard. The card machine is somewhere else — and so is a member of staff who could carry it there.
Regulated sales need checks before the money moves
Age, safety, allergens, deposits, exchange eligibility. A card reader takes payment. It doesn't ask a single question first.
Replacing a till is a two-year decision
Taking one more payment is a two-minute one. We built for the second, so nobody has to make the first.
Scan. Check. Settle. Signal.
Four stages, the same in every product. Step through them, or let it run.
Same spine underneath. Different rules on top.
A restaurant and a gas forecourt fail in completely different ways. The payment logic is shared; the rules that guard it are not.
Every table, a till.
Guests scan the code at the table, order and pay from their own phone. Service keeps moving, tables turn faster, and your existing till stays exactly where it is.
Every sale, safe and settled.
Off-till and kiosk sales for goods that come with rules attached. The checks, the deposit and the exchange are handled before payment — and the record comes out the other end.
Every payment tells you something.
Because the sale runs through the rail, you see it at the level it actually matters: the group, the site, the hour, the item, the member of staff. Not a monthly statement three weeks after you could have acted on it.
- Which sites are pulling the group up, and which are quietly leaking covers
- The hour your revenue actually peaks, against the hour you rostered for
- Baskets that were built and then abandoned before payment
- Checks completed, skipped or failed, per site and per shift
Tell us where your payments get stuck
Twenty minutes, screen share, no deck. We'll tell you honestly if neither product fits.
Book a demoOne rail. Four stages. Two very different rulebooks.
The page for whoever gets forwarded this by an operations manager who already likes it — the finance lead, the IT lead, the person who has to sign.
What every product inherits
Session binding
Rotating codes and single-use tokens tie a session to one place, one device and one window of time. A photograph of yesterday's code resolves to nothing.
Rules before authorisation
Checks run before the payment starts, not as a refund afterwards. If a condition fails, no money ever moves.
Direct settlement
Funds go to the merchant's own account. Card acquiring today; bank-to-bank as the UK's recurring payment rails open up.
Receipts that stand up
Correct VAT treatment per line, the right receipt format for the amount, sequential and gap-free numbering.
No customer app
Everything the customer touches runs in the browser they already have. Install rates are what quietly kills scan-to-pay.
Reporting as a first-class output
Sessions, exceptions, abandoned baskets and completed checks — per site, per hour, exportable.
We sit beside your POS, not on top of it.
Most scan-to-pay vendors arrive asking you to change your point of sale, retrain the floor and migrate the menu in the same fortnight. That's a project. This is a payment.
- No rip-and-replace. Your till keeps doing what it does.
- No hardware from us. Codes print or display on what you own.
- Integrations built per vertical — where they earn their keep, not promised generically.
- Exit is possible. Your data is yours and exportable. Lock-in isn't a business model.
What we deliberately don't do
We don't replace your till
If you want a new POS, buy a POS. We make the payment happen where the till can't reach.
We don't hold your money
Settlement is direct. There's no Kshirapps float sitting between a sale and your bank account.
We don't sell hardware
No terminals, no tablets, no five-year lease on a screen bolted to a wall.
Security and data
Card data –
Card details are handled by our regulated payment processor and never touch Kshirapps systems. We hold a reference to a transaction, not a card.
Customer identity +
Sessions are pseudonymous by default. We collect what the sale legally requires and nothing beyond it, so you aren't left holding a database of names you'd then have to protect.
Records of checks +
Where a sale requires a safety or eligibility check, the result is stored against the transaction for the period the relevant regulation requires, then removed.
Location and residency +
UK data residency. Obligations under UK GDPR are set out in the privacy notice.
Every table, a till.
Guests scan, order and pay from their own phone. Nobody queues at the bar holding a card, and nobody has to learn a new POS on a Friday night.
The rooms where the till is furthest from the money
Buffet
Covers charged per head, drinks added through the meal, one bill at the end with no queue at the counter.
Brunch and bottomless
Timed sessions, per-guest allowances and top-ups that nobody on the floor tracks reliably by hand.
Pubs
Table service without the walk. Rounds ordered and paid from the seat on a full Saturday.
Dine-in
Pay at table at the end of service, split however the table wants to split it.
What the guest actually does
Scans the code on the table
Opens in the browser. No download, no account, no email address demanded before they're allowed to look at a menu.
Orders, or just pays
Full ordering where the kitchen is connected; pay-only where the venue would rather keep taking orders the way it always has.
Splits the bill and tips
By item or evenly, across separate cards, without a member of staff standing there arbitrating.
Gets a VAT receipt
The right format for the amount — simplified below the threshold, full invoice above it — numbered sequentially.
What your venue gets
Staff app
Table state at a glance, open sessions, who ordered what, and the ability to add, void or move a table without walking back to the till. Built to be used one-handed, on a phone, in a dark room, at speed.
- Open, move and merge tables mid-service
- Allergen information at the point of order
- Item-level void with two-tap confirmation
- Session states that survive a dropped signal
Kitchen display
Orders land on screen routed by prep station, with recall for anything sent too early. Designed around how a pass actually works, rather than a printer queue redrawn in pixels.
- Station routing and separate prep views
- Recall with confirmation of where it goes back to
- Item-level void, not ticket-level
- Runs on a screen you already own
Admin console
Menus, prices, hours, staff access and reporting across sites. One set of numbers, so the figure in the daily report is the figure in the payout.
- Menu and price changes, scheduled ahead
- Sales, sessions and abandoned baskets by hour and site
- Tip allocation records built around the Employment (Allocation of Tips) Act 2023
- VAT treatment set per item, not guessed at month end
Staff rota
Build weekly rotas by role and site, publish them to staff phones and handle shift swaps without a group chat.
Authorisations
Decide who can approve voids, refunds, discounts and comps, with every approval recorded against the shift.
Reviews management
Collect feedback after payment and see ratings and comments by site, shift and table.
Analytics reports
Sales, covers, tips, payment mix and table turn time by site, ready to export for your accountant.
Priced around your venue.
A buffet, a brunch spot and a busy pub don't take payments the same way, so they shouldn't pay the same way either. Tell us how your venue runs and we'll come back with a price made for it.
What we'll ask you
- How many sites and tables you run
- Your service style: buffet, brunch, pub or dine-in
- Typical covers in a week
- How guests pay today, and the POS you use
Questions we actually get asked
Do guests have to download anything? +
No. It opens in the phone's browser straight from the code on the table.
What stops someone walking out without paying? +
Sessions can take payment before the order reaches the kitchen, or hold a card at the start of service. Which suits depends on your room, and we'll work through it rather than assume.
Can someone photograph the code and order from home? +
No. Codes rotate and sessions are bound to the venue, so an old code resolves to nothing at all.
Do we have to replace our POS? +
No. TableTurn runs alongside it, and switching it off breaks nothing else.
How do tips reach staff? +
Tips are recorded per session and allocated according to the policy you set, with a record of how each amount was shared.
What about allergens? +
Allergen information is attached to menu items, shown to the guest before they order and surfaced to staff at the point of order.
See it running on your own menu
Send us a menu and we'll build the guest journey for your venue, not a generic demo.
Book a demoEvery sale, safe and settled.
Selling something with rules attached, away from the till. Ember runs the checks, handles the deposit or the exchange, takes the payment, and leaves you holding the record.
For sales the till was never designed to handle
Stock held in a cage, a yard, a bunker or a locked cabinet. Items needing a competence or safety check first. Products carried on a deposit, or exchanged rather than bought outright.
Forecourts and convenience
Sales in the yard while the kiosk is three deep, without anyone leaving the counter.
Trade counters
Controlled stock sold to account and cash customers under two different sets of rules.
Garden centres and hardware
Bulk, seasonal and outdoor stock sold where it stands, not carried to a till.
Depots and dealers
Exchange, deposit and refill transactions that a standard EPOS records badly or not at all.
What Ember settles before the money moves
Safety and eligibility checks
The questions that legally or commercially have to be asked — asked consistently, recorded against the sale, and impossible to skip because it was busy.
Deposits and exchange
New purchase, refill and exchange are different transactions, with different prices, different deposit positions and different paperwork.
Customer type
Trade and retail see different prices, terms and checks from the same screen, without a manager override.
VAT, per line
Deposits, refills and goods can carry different treatment. Ember applies the right one and produces a receipt that stands up.
Two ways to run it
Kiosk
A screen where the stock is. The customer works through the checks and pays before anything is released.
Scan from a phone
A code on the cage or the pallet. The customer's own phone becomes the terminal — no screen for you to buy, mount or keep alive outdoors.
We started with LPG cylinders because they're the hardest case.
A cylinder sale contains every difficult thing at once: a safety check that must happen, a deposit that has to be tracked across visits, an exchange price that differs from a first purchase, and stock that lives in a cage twenty metres from the till.
Everything Ember does for cylinders it does for any other regulated or deposit-bearing product — which is why the product isn't named after gas.
Priced around what you sell.
Every regulated category carries different checks, deposits and rules, so Ember is priced for your products and your sites. Tell us what you sell and how it's regulated, and we'll come back with a price made for it.
What we'll ask you
- How many sites, counters or kiosks you run
- The products you sell and the checks each one needs
- Whether you take deposits or run exchanges
- The ERP or stock system the sales need to reach
Questions we actually get asked
Does this replace our EPOS? +
No. Ember handles the sales your EPOS handles badly, and reports back so the day still reconciles.
Who is responsible for the safety check? +
You are, exactly as you are today. Ember makes the check consistent, records it against the transaction, and gives you evidence that it happened.
How are deposits tracked? +
Per customer and per item, with the deposit position visible at the next transaction so exchanges price correctly.
Do we need to buy a kiosk? +
Not necessarily. The same flow runs from a printed code on the customer's own phone.
Can we use our own product data and branding? +
Yes. Products, prices and rules are yours; the screen is skinned to your brand or your supplier's.
Tell us what you sell and how it's regulated
We'll map the checks, the deposit logic and the VAT treatment before we talk about software at all.
Book a demoThe dashboard is the second product.
Every payment on the rail carries context — where, when, what, under which checks. Switch between the group, a single site and the floor. All figures below are illustrative sample data.
| Site | Net sales | Covers | vs last week |
|---|
What the numbers are actually for
Rostering against reality
The hour your revenue peaks against the hour you staffed for. Two weeks of this usually pays for itself before anything else does.
Finding the leak
Baskets built and abandoned before payment tell you where the journey breaks — a price, a wait, a menu section nobody scrolls to.
Comparing like for like
Six sites on one rail means one definition of a cover, a session and a net sale. Group comparisons stop being an argument about methodology.
Proving the checks happened
For Ember sites, completed, skipped and failed checks by shift — the evidence you'd otherwise be reconstructing from a paper log.
Item-level truth
What actually sells at 9pm on a Thursday, rather than what the menu assumes sells.
Exports that reconcile
The figure on the dashboard is the figure in the payout, and both export to whatever your accountant already uses.
We build the payment, not the counter.
Kshirapps Ltd (UK) builds payment infrastructure for businesses that sell away from the till. TableTurn and Ember are our products.
Why we exist
Twenty years of enterprise IT teaches you which problems are genuinely hard and which are just badly organised. Taking a payment twenty metres from the till is the second kind — and operators are still told the answer is a new point-of-sale system, a hardware lease and a migration.
It isn't. The answer is a rail that reaches the customer where they already are, runs whatever checks that sale requires, and settles straight into the merchant's account. That's the whole company.
The Kshirapps family
Payment intent made possible without physical infrastructure.
Every payment, a signal.
Every table, a till.
Every sale, safe and settled.
How we work
Bootstrapped
We answer to the people paying us to solve their problem. That shapes what gets built and how fast we're willing to promise it.
Built with operators
Every product started in a real venue with a real complaint, and every release goes back to those same people to be told what's still wrong.
Honest about fit
If neither product suits your site we'll say so on the first call. A bad deployment costs us more than a lost sale.
Company details
| Registered name | KSHIRAPPS LTD |
|---|---|
| Company type | Private limited company |
| Registered in | England and Wales, United Kingdom |
| Company number | 17424670 |
| Incorporated | August 2026 |
| Registered office | 116 Walsingham Gardens, Epsom, KT19 0ND, United Kingdom |
| Contact | sales@kshirapps.com |
Kshirapps Ltd is not authorised by the Financial Conduct Authority to hold or manage client money. Payments are processed by regulated payment providers. View on Companies House
Tell us where the payment gets stuck.
We reply within one working day. If neither product fits, we'll say that instead of booking you a demo.
Direct
- Sales and demos
- sales@kshirapps.com
Book a slot
Twenty minutes, screen share, no deck. Pick a product and we'll bring the right demo.
Already a customer?
Email us with your site name and a short description, and we'll pick it up.
sales@kshirapps.com
Privacy notice
How Kshirapps Ltd handles personal data across its products.
What we collect
For guests and customers using a Kshirapps product, we collect what the transaction requires: the items bought, the amount, the site, the time, and where a regulation requires it, the result of a check. Sessions are pseudonymous by default.
What we don't collect
We do not require an account, an email address or a phone number for a customer to complete a purchase. Card details are handled by our payment processor and do not reach our systems.
Retention
Transaction records are retained for the period required by tax and, where applicable, sector regulation. Check records are held for the retention period that regulation specifies and then removed.
Your rights
Under UK GDPR you may request access to, correction of, or erasure of your personal data. Requests go to sales@kshirapps.com.
Terms of service
The agreement between Kshirapps Ltd and merchants using our products.
The service
Kshirapps Ltd provides payment initiation, rule execution and reporting. Settlement is performed by our regulated payment partner directly to the merchant's nominated account.
Merchant responsibilities
The merchant remains responsible for the goods and services sold, for the accuracy of prices and product information, and for compliance with any regulation governing what they sell — including safety and age restrictions.
Fees
Fees are tailored to each merchant and set out in the merchant's order form.
Termination
Either party may terminate on notice as set out in the order form. On termination the merchant may export their data.
Cookies
What this website stores on your device, and the choice you have.
Your choice
We only set the cookie this site needs to work unless you agree to analytics. Rejecting analytics changes nothing about how the site works. You can change your mind at any time: .
Cookies on kshirapps.com
| Name | Purpose | Type | Expires |
|---|---|---|---|
| kshirapps_consent | Remembers whether you accepted or rejected analytics, so we don't ask on every visit. | Strictly necessary | 6 months |
| _ga | Google Analytics: tells one visit from another so we can count visitors. Set only if you accept analytics. | Analytics | 2 years |
| _ga_<ID> | Google Analytics: keeps track of the current visit. Set only if you accept analytics. | Analytics | 2 years |
Withdrawing consent
Turning analytics off in cookie settings stops Google Analytics from loading and deletes the analytics cookies it set on this site.
What we don't use
No advertising cookies, no cross-site tracking, no third-party marketing pixels.
Our products
TableTurn and Ember run on their own domains and use a session identifier that keeps a payment attached to the correct table or kiosk. Their own notices describe it.
Accessibility
Our commitment, and where we currently fall short.
Target
WCAG 2.2 AA across the guest-facing payment journey and the merchant console.
What we've done
Keyboard navigation throughout, visible focus states, text alternatives for every non-decorative image, and colour contrast checked against AA on all interface text. Motion respects the operating system's reduced-motion setting.
Known gaps
Listed here honestly once independent testing has been completed, with a date against each.
Tell us
If something on a Kshirapps product is unusable for you, email sales@kshirapps.com and we'll respond within five working days.