These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Theme Park Management
- Features
- Payments and refunds
Payments and refunds
Provider payment events verified against events.
OverviewPayment evidence log×
Theme Park Management · Payments and refunds
New
Payment evidence log
Payment evidence
| Id | Parent | Type | Amount USD | Occurred at | Verified | |
|---|---|---|---|---|---|---|
| IDD-961 | EVN-18022 | Authorization | 200 | 03 Oct | ||
| IDD-463 | EVN-90588 | Capture | 680 | 23 Oct | ||
| IDD-555 | EVN-96096 | Refund | 650 | 25 Oct | ||
| IDD-343 | EVN-34873 | Void | 50 | 25 Oct | ||
| IDD-440 | EVN-91897 | Authorization | 140 | 23 Oct |
6 of 6 records
IDD-961Payment evidence · PE-45426
AuthorizationParentEVN-18022
Amount USD200
Occurred at03 Oct
Verified✓
What you can do
Count money only when the provider confirms it
Payment events come from your payment provider and are recorded against the event: authorizations, captures, refunds and voids, each with the provider’s event identifier, reference, amount and time. An event is marked verified once it has been confirmed. Admissions are settled only by verified captures.
Refunds follow the same rule in the other direction. When an event is cancelled or a guest is refunded, the refund is recorded as its own event when the provider confirms it. Until then it is not shown as done, which means guest services never tells a customer their money is back before it is.
How the work is organized
The payments clerk records and verifies; the operations manager reconciles at close.
- Verified before counted. Only verified captures settle tickets.
- Refunds confirmed. A refund counts only when the provider confirms it.
- Duplicates recognised. The provider’s event identifier stops a payment counting twice.
What to agree during setup
Agree how payment events arrive from your provider and how they are verified. Agree your refund rules for cancellations, weather closures and guest complaints. Card processing stays with your provider. Prepare examples of a normal capture, a failed capture, a partial refund and a voided authorization.
Check the handoff on an actual case
A thunderstorm closes the park at 15:00 and the day’s night event is cancelled. Refunds are requested for every night-event ticket. The payments clerk records each refund as the provider confirms it. Guest services can tell customers exactly which refunds have been confirmed and which are still pending with the provider.
At the end of the following week, the clerk checks for refunds still waiting on the provider and follows them up, so no guest is left without an answer.
The same applies to weather days that do not close the park. If a ride closes for the afternoon and guests are offered a partial refund, each refund is still recorded only when the provider confirms it.
What your team sees
- Payment evidence log — Authorizations, captures, refunds and voids per event.
Follow the work through
- Admission and payment: How payments settle admissions.
- Event close and reconciliation: Reconciling the day.
Plan integrations with your payment provider.
What it keeps track of
Data model- Payment evidence
- Provider payment events reconciled against event admissions.
- Events
- Park operating events with capacity, lifecycle and revision control.
- Admissions
- Guest admission lines reserved and admitted against an event.
Who uses it
Permissions- Payments Clerk
- , Park Operations Manager.
- The clerk verifies payments; the manager reconciles at close.
Set up Theme Park Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.