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 message saying a payment was recorded is not always proof the collection was approved and available. Retrieve the actual provider state before retrying or reporting event income. Keep ticket attendance separate from payment outcome. Your office needs an assigned exception record for an uncertain attempt, rather than charging again 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. Check the actual venue environment and provider instructions for the relevant device. A terminal working at the studio does not prove the same setup works off-site. Confirm the accepted customer price and permitted collection action before the event, keeping registration and payment records connected through stable internal references.
Ask what offline methods the account supports and how you can preserve and then later upload the pending attempts. The documentation for supported hardware and methods for Square as well as the terms for merchant risk for offline transactions does not imply that all terminals support offline transactions universally. Use the current procedure for the account that you are using for the event, not some 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
Retrieve the event ticket or accepted booking reference and the actual payment attempt identity. A person attending a class does not prove their card payment completed. A provider payout might also arrive separately from the event. Keep gross collections, refunds, fees and available funds distinct in the accounting review instead of treating the attendance list as an income statement.
The terminal-status sheet records the event reference, ticket reference, device and account reference, attempt identity, verified provider state, permitted next action and owner. Use fictional codes without card credentials or health details. It does not approve payments, upload an offline queue or determine attendance rights. Filled fields organize the exception while source records establish the actual outcomes.
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. The example provides no universal offline acceptance or payment-finality promise.
If the provider later reports failure, obtain the supported next collection action and the necessary customer 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, and staff should not improvise an undocumented recovery sequence from a blog example.
Reconcile the event after the supported outcome
Match verified collections to accepted ticket references, review the unresolved attempts in the terminal-status sheet separately from the verified collected income for the event. Verify the appropriate contact method for next commercial question, do not ask for card# etc in regular message. Verify that completed provider payment was recorded separately from cash available for studio/ instructor.
Go back to the test case that failed and update the relevant setup checks. Make sure any duplicate attempts or unresolved balances are logged under the correct owner in your office. Your owner wants verified event income, correct attendance figures and a way to handle provider-state related 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.