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.
- Event Venue Management
- Features
- Payment evidence
Payment evidence
Tie provider authorizations, captures, refunds and voids to an event.
OverviewVerified payment effects×
Event Venue Management · Payment evidence
New
Verified payment effects
Payment evidence
| Parent | Type | Amount USD | Occurred at | Provider reference | Verified | |
|---|---|---|---|---|---|---|
| EVN-94353 | Authorization | 690 | 10 Oct | PR-975 | Yes | |
| EVN-75335 | Capture | 440 | 14 Oct | PR-147 | Yes | |
| EVN-83955 | Refund | 380 | 17 Oct | PR-341 | Yes | |
| EVN-62789 | Void | 560 | 03 Oct | PR-807 | Yes | |
| EVN-99569 | Authorization | 820 | 16 Oct | PR-381 | Yes |
6 of 6 records
PR-975Payment evidence · PE-38317
AuthorizationParentEVN-94353
Amount USD690
Occurred at10 Oct
VerifiedYes
What you can do
Separate provider effects from local requests
Payment evidence belongs to an event and carries a provider event identity, reference, type, amount, occurrence time and verified state. The type distinguishes authorization, capture, refund and void. Those distinctions matter to venue operations: an authorization is not a capture, and a prepared refund decision is not completed money movement.
Reservation and setup completion use verified capture evidence. The provider is the authority for its own transaction outcome. Operations Manager can inspect the provider reference and verification state before describing a reservation as complete or a venue setup as finished. A local operation receipt shows that a guarded action was attempted and what the local result was; it does not replace the provider’s confirmation.
How the work is organized
- Record the effect. Payment evidence identifies the provider event, type, amount and event parent.
- Verify the source. Operations Manager checks the provider reference before relying on a capture or refund.
- Reconcile. Admission quantity and payment effects are compared when an event is completed or cancelled.
What to agree during setup
Choose the payment provider and decide how its event identity and reference are brought into the event record. Define who checks that a provider effect is verified. Agree how a disputed or uncertain effect is investigated through the original reference. The event’s organization has a currency setting while the payment evidence amount is recorded in USD; Operations Manager should agree the operating treatment before using amounts across currencies.
Rehearse an authorization followed by a capture for the same event. Staff should identify the capture separately and base completion on the verified effect. Then rehearse an uncertain refund after a cancellation. Preserve the reviewed refund preparation and wait for provider evidence before reporting money returned.
Check the handoff on an actual case
Admission Staff request a reservation for an open event. A provider capture arrives with its own identity and reference. Operations Manager verifies the effect and the reservation can be treated as completed. Later, the event owner cancels unused scope while admitted history remains. Independent Reviewer approves any compensating action for executed scope. A refund record is then checked against the provider’s result before it is counted as completed.
If a provider callback repeats, investigate it by provider event identity. The same capture should not create a second admission reservation or a second completed operation. If the provider cannot confirm an effect, the operation remains for review with its failure reason and original reference.
What your team sees
- Verified payment effects — Inspect confirmed provider evidence by event and type.
- Operations needing review — Investigate uncertain local outcomes against their provider references.
Follow the work through
Read admission and closure for how captures affect reservation and completion. Read operation reconciliation for uncertain effects.
What it keeps track of
Data model- Payment evidence
- Provider payment authorizations, captures, refunds and voids.
- Events
- Events with a venue counterparty, capacity, lifecycle and revision. Venue booking includes setup and teardown intervals.
- Admissions
- Reserved and admitted admission lines for an event.
- Venue setups
- Venue setup records for a hall booking, submitted for review and completion. Venue booking includes setup and teardown intervals.
- Operation receipts
- Idempotent receipts for guarded operations with expected revision and result state.
- Review decisions
- Independent reviewer decisions recorded against a source revision.
Who uses it
Permissions- Operations Manager
- , Independent Reviewer, Admission Staff and Event Owner.
Set up Event Venue Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.