Wellness pop-up uncertain terminal-status sheet
Track the actual attempt independently from ticket attendance.
No signup. Enter reference codes, add records and download a CSV. Entries stay in the browser tab. Filled fields do not establish completion, approval or compliance.
| Event reference | Ticket reference | Device and account reference | Attempt identity | Verified provider state | Permitted next action | Event owner role |
|---|---|---|---|---|---|---|
| Pop-up-example-9 | Workshop-ticket-example | Approved-device-reference | Offline-attempt-example | 80 unresolved, illustrative | Event-coordinator-role |
- Starting records are fictional examples, not merchant evidence.
- Keep private documents and actual contacts in your approved business system. Use internal reference codes here.
- Missing required fields indicate an unresolved record. Filled fields do not prove authorization, completion, compatibility or compliance.
- Export to approved business storage. Browser edits are cleared on reload.

At a wellness pop-up, a terminal saying payment was recorded is not always proof that the collection was approved and available. Check the provider’s actual state before retrying or reporting event income. Keep ticket attendance separate from the payment outcome. And when an attempt is uncertain, your office needs an assigned exception record. Don’t charge again just because connectivity made the first result unclear.
Use with this guide
wellness event payment setup checklist
The wellness event payment setup checklist reviews supported methods and venue readiness before collection.
workshop cancellation cash worksheet
The workshop cancellation cash worksheet separates actual refund funding from retained event expenses.
Browse the complete wellness center guides and worksheets.
Test the actual event setup before collection
Identify the terminal, merchant account and supported connection method. Then check the actual venue environment and the provider’s instructions for that device. A terminal working at your studio doesn’t mean the same setup will work off-site. Before the event, confirm the accepted customer price and what collection action is allowed. Keep registration and payment records linked with stable internal references.
Check which offline methods your account supports, and how to save pending attempts before uploading them later. Square documents supported hardware and methods, but its merchant risk terms for offline transactions don’t mean every terminal supports them. Use the current procedure for the account you’ll use at the event. Don’t use an assumed upload deadline. The wellness event payment setup checklist reviews supported methods and venue readiness before collection.
Sources for this section: Square: supported offline payments, risks and device limits · Square: troubleshoot failed payments and pending charges
Record attendance and collection as different events
Get the event ticket or accepted booking reference, plus the identity of the actual payment attempt. Someone showing up for class doesn’t prove their card payment went through. And a provider payout may arrive separately from the event. Keep gross collections, refunds, fees, and available funds separate in your accounting review. The attendance list isn’t an income statement.
The terminal-status sheet records the event and ticket references, device and account references, attempt identity, verified provider state, permitted next action, and owner. Use fictional codes, never card credentials or health details. The sheet doesn’t approve payments, upload an offline queue, or determine attendance rights. Filled fields organize the exception; source records establish what actually happened.
Handle a fictional uncertain attempt once
Suppose a fictional $80 workshop payment is recorded on a disconnected device, while the account-specific approval outcome remains unresolved. The office should track one uncertain attempt, not $80 of verified collected income. It should not charge another $80 without checking the first state through the supported procedure. This example does not promise that offline payments are always accepted or final.
If the provider reports a failure later, get the next supported collection step and the customer’s permission. Keep the failed attempt in the history. Do not reset or clear a device in a way the provider warns could lose pending records. The supported response depends on the actual hardware and account. Staff shouldn’t improvise an undocumented recovery sequence from a blog example.
Reconcile the event after the supported outcome
Match verified collections to accepted ticket references. Review unresolved attempts in the terminal-status sheet separately from the verified collected income for the event. For the next commercial question, verify the appropriate contact method. Don’t ask for card numbers or related details in a regular message. Check that the completed provider payment was recorded separately from cash available to the studio or instructor.
Go back to the test case that failed and update the relevant setup checks. Log duplicate attempts and unresolved balances under the right owner in your office. Your owner wants verified event income, accurate attendance figures, and a way to handle provider-state questions. Do not mislead people into believing that all offline terminals pay, that all alternate methods are free or that another reminder campaign will fix a provider-state question. The workshop cancellation cash worksheet separates actual refund funding from retained event expenses.
Primary sources
BlueFinch last reviewed these sources on October 4, 2026. Payment rules and state requirements can change.
- Square: supported offline payments, risks and device limits
- Square: troubleshoot failed payments and pending charges
Use this page for general business information. It is not legal, tax, or accounting advice.