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.
- Esports Team Management
- Features
- Payment evidence
Payment evidence
Trace verified provider events and their fixture context.
OverviewVerified provider events×
Esports Team Management · Payment evidence
New
Verified provider events
Payout evidence
| Parent | Provider event ID | Type | Amount USD | Occurred at | Provider reference | |
|---|---|---|---|---|---|---|
| FXT-18997 | PEI-477 | Authorization | 50 | 07 Oct | PR-641 | |
| FXT-32602 | PEI-899 | Capture | 780 | 08 Oct | PR-101 | |
| FXT-70148 | PEI-564 | Refund | 770 | 07 Oct | PR-871 | |
| FXT-16145 | PEI-111 | Void | 130 | 23 Oct | PR-873 | |
| FXT-32263 | PEI-323 | Authorization | 230 | 17 Oct | PR-810 |
6 of 6 records
PEI-477Payout evidence · PE-77691
AuthorizationParentFXT-18997
Amount USD50
Occurred at07 Oct
Provider referencePR-641
What you can do
Read payment evidence in its event context
Provider evidence records an event identifier, type, amount, occurrence time, verification state and provider reference against a fixture. Authorization, capture, refund and void are distinct event types. A capture marked verified can support admission or completion decisions; an authorization alone does not show that payment was captured. A refund record documents the provider event but should not be inferred from a local cancellation request.
Finance Reviewer checks the provider reference and verification state before using an event in reconciliation. Admissions Operator and Fixture Coordinator can compare the verified capture with the admission and closure context. The provider remains authoritative for actual money movement. The local operation receipt gives the team a stable key and linked effects for a guarded action.
How the work is organized
- Verification. Distinguish a provider-confirmed event from an unverified local record.
- Event type. Read authorization, capture, refund and void separately.
- Fixture link. Keep payment evidence attached to the same event as the related admissions and entries.
What to agree during setup
Agree which provider supplies authoritative results, who verifies them, and how the provider event identifier is matched to local work. Establish a review path for a disputed amount or duplicate event identifier. Decide who may see provider references and who can resolve receipts left pending after an uncertain response.
Check the handoff on an actual case
For an open fixture with reserved admission, inspect the provider evidence for the related event. A verified capture can support completion after capacity checks; a pending authorization cannot. If the fixture owner cancels after admission, retain the admitted history, obtain an independent decision on the compensating action and verify refund evidence before calling any money movement complete. Compare the refund provider reference with the original fixture and operation receipt. When reconciliation finds a mismatch, leave the receipt in review with its reason and do not issue the external action again.
A payment review should start from the fixture, then identify the admission or entry decision that depends on the event. Use the provider event identifier to avoid counting the same capture twice in a report. If a refund follows a cancellation, compare its amount and provider reference with the original capture and retain both events. The history should explain the net result without hiding the first transaction.
What your team sees
- Verified provider events — Review confirmed provider events by fixture, type and amount.
- Operation exceptions — Trace unsettled local action outcomes to their provider reference.
Follow the work through
See the operating process for the decision and evidence sequence.
What it keeps track of
Data model- Payout evidence
- Provider payment authorizations, captures, refunds and voids.
- Operation receipts
- Idempotent receipts for guarded operations with expected revision and result state.
- Fixtures
- Programs, events and sessions with capacity, lifecycle and revision.
- Match admissions
- Reserved and admitted admission lines for an event.
- Team entries
- Participant registration records submitted for review and completion.
Who uses it
Permissions- Finance Reviewer
- , Fixture Coordinator and Admissions Operator.
Set up Esports Team Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.