
To track offline payments, give every one of them a booking reference, a payment status and a method, then reconcile that list against your processor’s reports and your bank deposits on a fixed schedule. “Offline” covers two different things: card payments taken while a device had no connection, and money that never passed through your online checkout, such as cash at the front desk. Both need a record the same day, and the card kind also has a hard clock on it.
TL;DR
- Offline card payments are usually stored on the device and authorised later, so they can be declined after the customer has already played. Upload them quickly, within 24 hours where you can.
- Cash and other off-platform payments need a same-day record tied to a specific booking, split from card sales.
- Use four statuses (pending, paid, declined, refunded) and review anything not “paid” every day.
- Reconcile weekly: bookings against processor reports against bank deposits.
- Keep receipts and deposit records organised by year, and know the federal rule for cash over $10,000.
Table of Contents
- What “offline payment” actually means
- Why offline payments go missing
- The deadlines and liability for offline card payments
- A simple system for tracking offline payments
- Tracking cash and other off-platform payments
- The records worth keeping
- Using payment statuses and reports to cut missed payments
- A worked example
- Our perspective
- Bring payments and bookings into one place
- FAQ
- Sources
What “offline payment” actually means
The term gets used loosely, so pin it down before building a process around it.
Card payments accepted while disconnected. A card reader or POS app loses Wi-Fi or mobile data. It still takes the card, stores the transaction securely on the device, and sends it for authorisation once the connection returns. The Federal Reserve describes these as hybrid offline payments: accepted while disconnected, stored locally and authorised later. It also notes that products branded as offline still rely on the internet for final clearing and settlement.
Payments taken outside your online checkout. A group pays cash at the door. A corporate client pays by cheque or bank transfer. A player buys a top-up on the spot. None of these touch your booking page, so nothing updates automatically unless you record it.
The difference matters because the risks differ. The first is a timing and liability problem. The second is a bookkeeping problem. A venue that runs events, pop-ups or a lobby with patchy signal usually has both.

Why offline payments go missing
Most discrepancies come from a handful of causes:
- A device reconnected, but nobody checked whether the stored payments went through.
- A payment was declined on upload, after the team had already run the game.
- Cash was taken and the booking still shows “unpaid” (or the reverse: marked paid, but no money in the till).
- A deposit was paid by transfer and never matched to a booking.
- Two staff members recorded the same payment in different places.
Every one of these is a mismatch between what the booking system says and what the money did. Tracking offline payments is mostly the work of closing that gap quickly.
The deadlines and liability for offline card payments
If you take cards on a reader that can work offline, learn the processor’s rules before you rely on it. The details differ by provider, but the pattern is consistent.
Upload windows
Square says that when a device reconnects it uploads and processes pending offline payments, and that you can then see which ones completed and which were declined. Its offline payments guide also says payments should be uploaded within 24 hours to reduce the risk of chargebacks or declines, and that pending payments expire after 72 hours and can’t be retrieved or reprocessed. Read that last point twice: a payment that expires is money you can’t recover from that transaction.
Who carries the loss
The same Square guide says merchants are responsible for expired, declined or disputed offline payments. Adyen’s offline payments documentation goes the same way: liability rests entirely with the merchant, and it recommends setting transaction floor limits to reduce exposure to chargebacks and failed captures.
In practice, a limit is a cap on how much you’ll accept offline on one transaction. For a venue where a typical group booking is a few hundred dollars, a low cap means a declined card costs you one small sale rather than a big group.
Card network rules
The card networks are stricter than most merchants expect. In the US, Visa’s acquirer guide describes an always-online environment where transactions are authorised online, and says offline chip approvals in the US don’t protect you against chargebacks.
Visa also requires a deferred authorisation indicator when authorisation is obtained after the transaction date because of connectivity problems, with authorisation expected within 24 hours for most merchant categories. And its dispute guide for merchants warns that processing offline without meeting authorisation requirements, or settling outside permitted timeframes, leaves you liable for authorisation disputes that proof of service can’t override.
The takeaway for a venue: treat offline card acceptance as a fallback for a bad hour, not a normal way of working. If your internet is unreliable at a location, fix the connection or add a backup (a mobile hotspot, a second network) rather than relying on stored transactions.
A simple system for tracking offline payments
You don’t need complicated software to do this well. You need consistent fields and a daily habit.
Step 1: Give every payment a booking reference
A payment without a booking reference is a payment you’ll spend an hour matching later. At the moment of payment, staff note the booking ID or the customer name plus game time. If your system supports it, record it in the booking itself rather than a notebook.
Step 2: Record the method
Use a short, fixed list: card online, card on reader, card on reader (offline), cash, bank transfer, gift voucher, other. The “offline” tag is what lets you filter later for the transactions that carry risk.
Step 3: Use four statuses
| Status | Meaning | What to do |
|---|---|---|
| Pending | Taken offline or promised, not confirmed | Check at close of day |
| Paid | Confirmed in processor report, till or bank | Nothing |
| Declined | Failed on upload or bounced | Contact customer same day |
| Refunded | Money returned | Record the reason and who approved it |
The point of the list is that “pending” is never a resting place. Anything pending at the end of the day gets looked at.
Step 4: Run a daily five-minute check
At close, one person does three things:
- Confirm every reader or tablet that was offline has reconnected and uploaded.
- Open the processor’s list of completed and declined payments and compare it to the day’s offline-tagged bookings.
- Count the till and compare it to cash-tagged bookings.
If you do only one thing from this article, do this.
Step 5: Reconcile weekly
Once a week, line up three lists: bookings with their payment status, the processor’s payout or transaction report, and your bank deposits. Differences fall into a few buckets: timing (a payout hasn’t landed yet), fees (the payout is net of fees), declines, and genuine errors. Only the last bucket needs investigation.
If you use Adyen, its documentation explains how to reconcile offline payments using webhooks that carry the PSP reference or the terminal-generated tender reference, and suggests adding the Store and Forward indicator to the Received payment details report. Other processors have equivalent filters; look for one that isolates offline or stored transactions.
Tracking cash and other off-platform payments
Cash is the most common offline payment at an escape room, and the easiest to lose track of.
Record it the day it’s received. The IRS recommends recording cash receipts daily and keeping separate summaries for cash and credit sales. That one habit solves most cash disputes, because you can see what the till should hold at any time.
Tie it to the booking. Mark the booking paid in cash with the amount, the date and the staff member who took it. If your front desk uses a physical drawer connected to a POS, make sure it’s wired reliably: something as small as a cash drawer data cable failing can leave sales rung up with no matching drawer record.
Deposit on a schedule. Bank cash at a regular interval and keep the deposit slip. The deposit then becomes the third leg of your weekly reconciliation.
Mind the large-cash rule. In the US, a business that receives more than $10,000 in cash in a single transaction or related transactions must file IRS Form 8300 within 15 days. This is rare for a typical escape room booking, but corporate events and buyouts can approach it. Related transactions count, so a deposit and a balance from the same client add up. For anything near that level, speak to your accountant.
![]()
The records worth keeping
Good records resolve disputes in minutes. The IRS tells businesses to keep supporting documents such as sales slips, receipts, cancelled cheques and deposit information, organised by year and by type of income or expense. It also says you can choose a system that suits your business, as long as it clearly shows income and expenses.
For offline payments, a sensible minimum is:
- The booking reference, date, amount and method.
- The processor’s confirmation (or decline) for each offline card payment.
- Cash count sheets and deposit slips.
- Notes on any refund, including who approved it.
- Copies of any Form 8300 filing, which the IRS says to retain for at least five years from the filing date, along with supporting documents.
For money you pay out in cash, the IRS says to obtain a receipt or, when one isn’t available, write an adequate explanation in your records at the time of payment.
Using payment statuses and reports to cut missed payments
The strongest protection against missing money is making the status visible where decisions are made. When a staff member opens tomorrow’s schedule, they should see at a glance which groups are paid, which have a deposit only, and which are pending. That changes behaviour: someone chases the pending booking the day before rather than after the group walks out.
Three reports are worth running regularly, whatever tool you use:
- Unpaid or part-paid upcoming bookings. Chase these before the game, not after.
- Declined or failed payments. Contact the customer within hours. Our payment failure recovery playbook walks through the sequence for venue managers.
- Revenue by payment method. A sudden rise in cash or offline-tagged sales at one location is a prompt to ask why, whether it’s a connectivity problem or a process gap.
Reminders help too. A booking confirmed with a deposit is far easier to protect than one with nothing paid, and automated SMS reminders give customers a prompt to settle a balance or confirm attendance. For an audit trail on who changed what, see our note on booking audit logs for managers.
A worked example
Say a venue with two sites has a weekend where the lobby’s Wi-Fi drops for three hours on Saturday afternoon. Staff keep the reader running in offline mode and take five card payments, $60, $95, $120, $180 and $240, on top of two cash bookings.
That evening, the closing manager:
- Confirms the reader reconnected and opens the processor’s report. Four payments show completed; the $120 one is declined.
- Updates the four to “paid” and the $120 to “declined”, then calls the customer, who has gone home. They agree to pay by link that night.
- Counts the till against the two cash bookings and finds it matches.
- Notes on Monday’s weekly reconciliation that the $120 is now paid via the link, and that the payout will arrive a couple of days later.
Total time: about fifteen minutes. Without the status and the daily check, that $120 would have surfaced weeks later as an unexplained gap, or not at all. A cap on offline transactions, say $150 per payment, would also have meant the $180 and $240 sales were taken another way, reducing the exposure on the day.
Our perspective
Venues rarely lose money to offline payments in one big hit. They lose it in small, untracked pieces: a declined card nobody chased, a cash booking marked unpaid, a transfer that never got matched.
That is why we built Riddlio around one idea: bookings, payments, customer messages and reporting should sit in the same place, so the status of a booking and the status of its money are never two separate stories. When staff can see who has paid and who hasn’t while looking at the day’s schedule, follow-up happens on time.
Our advice to any operator is to treat payment status as part of operations, not as something for the accountant at month end. Review it daily, reconcile it weekly, and keep offline acceptance for genuine emergencies.
Iosif Beraru
Bring payments and bookings into one place
If you’re tracking payments across a booking calendar, a card reader and a spreadsheet, you’re doing the reconciliation by hand. Riddlio is a booking and management platform built for escape room venues, with payment processing that connects to the major providers, reminders, waivers and reporting alongside. Plans are published on our pricing page: Starter is $29 per month, Pro is $79 per month and Unlimited is $199 per month, with Enterprise available on request.
If you take in-person payments at the front desk, our POS integration page explains how that fits with online bookings.
FAQ
How do I find missing offline transactions?
Start with the processor’s report of completed and declined payments for the days the device was offline, and compare it to the bookings you tagged as offline. Anything on your list but not in the report is either still pending or expired. Check Square’s guidance, which says pending payments expire after 72 hours, so act fast.
What is the difference between online and offline payments?
An online payment is authorised with the bank at the moment of purchase. An offline payment is accepted while the device is disconnected, stored, and authorised later when the connection returns. That delay is why the Federal Reserve describes these systems as hybrid, and why the merchant carries the risk of a later decline.
How should I track cash payments for bookings?
Record each cash payment against its booking on the day, with the amount and the staff member’s name, and keep cash and card sales in separate summaries. Count the till at close and match it to that list. Bank the cash on a regular schedule and keep the deposit slips.
How long should I keep payment records?
Keep receipts, deposit records and similar documents organised by year and type of income, as the IRS recommends. Form 8300 filings and their support must be held for at least five years. Your accountant can confirm the right period for everything else.
Sources
- Federal Reserve: Offline Payments, Implications for Reliability and Resiliency
- Square: Process offline payments
- Adyen: Offline payments
- Visa: VSDC and Visa payWave US Acquirer Implementation Guide
- Visa: Deferred Authorization Indicator Reminder
- Visa: Dispute Management Guide for Merchants
- IRS: Publication 583, Starting a Business and Keeping Records
- IRS: What kind of records should I keep
- IRS: E-file Form 8300, Reporting of large cash transactions
- IRS: Form 8300 reference guide
- APG CD-101A cash drawer data transfer cable
