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.
- Community Event Platform
- Features
- Payment and closeout
Payment and closeout
Check provider evidence and admission before completing or cancelling an event.
OverviewPayment verification×
Community Event Platform · Payment and closeout
New
Payment verification
Payment evidence
| Parent | Type | Amount USD | Occurred at | Provider event ID | Verified | |
|---|---|---|---|---|---|---|
| CE-69066 | Authorization | 590 | 24 Oct | PEI-104 | Yes | |
| CE-31469 | Capture | 750 | 20 Oct | PEI-438 | Yes | |
| CE-10774 | Refund | 780 | 12 Oct | PEI-287 | Yes | |
| CE-57563 | Void | 660 | 25 Oct | PEI-688 | Yes | |
| CE-18904 | Authorization | 160 | 03 Oct | PEI-235 | Yes |
6 of 6 records
PEI-104Payment evidence · PE-36176
AuthorizationParentCE-69066
Amount USD590
Occurred at24 Oct
VerifiedYes
What you can do
Keep the operating record clear
Payment evidence records a provider event, type, amount, provider reference and verification state against the parent event. The Reconciliation Lead compares those records with admission lines and operation receipts. A verified capture supports a completed reservation; a prepared refund remains a proposed effect until the provider outcome is verified.
How the work is organized
- Read provider evidence. Match the event, provider identity, type and verification state before treating a capture as confirmed.
- Compare local effects. Check admitted quantity against verified captures and the receipt’s linked effects.
- Resolve before closure. Leave a discrepancy in needs review; close actual completed work or cancel eligible scope after the relevant checks.
What to agree during setup
Agree which provider supplies authoritative capture, refund and void events, and how its identifiers map to local evidence. Name the person who checks discrepancies and the reviewer for a compensating action. Rehearse a matched capture, an unmatched operation and a cancellation with admitted history.
Check the handoff on an actual case
After a workshop, the lead compares admitted quantity with verified capture records. An operation with an external reference is checked against its authoritative source. A mismatch goes to review with the discrepancy recorded. Once the effects agree, the event owner can close actual completed work. If the event is cancelled instead, unused admission scope is released while admitted history stays intact.
Rehearse an event with admitted participants and a provider capture whose event identity and verified amount match the local admission effect. Then use a second receipt with a missing or conflicting provider outcome. The Reconciliation Lead should keep that receipt in needs review with a concrete failure reason and check the authoritative source when an external reference exists. Do not repeat the original external execution during this check. If a cancellation needs a refund, preserve admitted history and route the proposed compensation for independent review. Only a verified provider refund is reported as money moved.
What your team sees
- Payment verification — Verified provider events linked to the selected event for comparison with admission.
- Operations needing review — Receipts with unresolved local or external effects and a recorded reason.
Follow the work through
- Event approval connects the draft and reviewer decision.
- Registration to admission follows the participant request and capacity.
- Event closeout reconciles admission and provider evidence.
Check the record definitions before importing active work.
What it keeps track of
Data model- Payment evidence
- Provider payment authorizations, captures, refunds and voids.
- Operation runs
- Idempotent receipts for guarded operations with expected revision and result state.
- Community events
- Programs, events and sessions with capacity, lifecycle and revision.
- Event RSV ps
- Reserved and admitted admission lines for an event.
- Review decisions
- Independent reviewer decisions recorded against a source revision.
Who uses it
Permissions- Reconciliation Lead
- Compares effects and investigates discrepancies.
- Event Owner
- Completes or cancels the event.
- Independent Reviewer
- Decides compensation for executed scope.
- Admin
- Manages access.
Set up Community Event Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.