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.
- Conference Management
- Features
- Payment evidence
Payment evidence
Keep provider payment events attached to the event for review and reconciliation.
OverviewVerified payment evidence×
Conference Management · Payment evidence
New
Verified payment evidence
Payment evidence
| Provider event ID | Parent | Type | Amount USD | Occurred at | Provider reference | |
|---|---|---|---|---|---|---|
| PEI-535 | EVN-52052 | Authorization | 810 | 16 Oct | PR-415 | |
| PEI-895 | EVN-47512 | Capture | 360 | 23 Oct | PR-651 | |
| PEI-471 | EVN-90255 | Refund | 710 | 19 Oct | PR-663 | |
| PEI-621 | EVN-17212 | Void | 880 | 27 Oct | PR-575 | |
| PEI-698 | EVN-93517 | Authorization | 850 | 06 Oct | PR-877 |
6 of 6 records
PEI-535Payment evidence · PE-95074
AuthorizationParentEVN-52052
Amount USD810
Occurred at16 Oct
Provider referencePR-415
What you can do
Check the provider event behind a result
Payment evidence records the provider event identifier, type, amount, occurrence time, verified state and provider reference. The event link gives Finance Reviewer the context for a capture, authorization, refund or void. A verified capture can support registration completion and admission reservation after the capacity effect is also persisted. An authorization alone is a different provider event and should remain distinguishable from a capture.
When an event is cancelled, refund evidence needs the same care. The close or cancel process prepares reviewed refund evidence while keeping admitted history intact. A prepared refund is a request for action; the provider event confirms what actually happened. Finance Reviewer reconciles the reference and amount before describing money movement as complete.
How the work is organized
- Provider identity. The provider event identifier and reference distinguish one payment event from another.
- Effect type. Authorization, capture, refund and void have different meanings for the event.
- Verification. The verified state records whether the team checked the event against its authoritative source.
What to agree during setup
Choose the payment provider connection and decide which external event is authoritative for each effect. Agree how a duplicate provider event identifier is handled and who may mark evidence verified. Because organization currency and payment evidence amount use different fields, the team must agree how to interpret payment amounts for its pilot event. Keep the provider reference available for a later dispute or correction.
The Event Owner and Finance Reviewer should also agree when a registration is considered complete. Approval alone does not settle payment, and capture alone does not establish available capacity. The admission and payment checks meet at completion, with an operation receipt preserving the attempted action and its result.
Check the handoff on an actual case
For an approved registration, Finance Reviewer inspects a provider capture linked to the correct event. They verify the provider identifier, reference, amount and occurrence time against the external source. Admissions Lead checks the persisted reservation separately. Only after both effects are present does the team treat the operation receipt as completed. If the provider event is duplicated, the same capture should not create another completed reservation.
Now rehearse a cancellation after some attendees were admitted. Keep the original capture and admission records. Review the unused reservation scope, prepare a refund with its source reference and await the provider’s refund evidence. The event’s cancellation does not erase the original financial history.
What your team sees
- Verified payment evidence — Review checked provider events by event, type and amount.
- Receipts needing review — Trace operations whose payment or capacity effects disagree.
- Admission lines — Compare payment evidence with reserved and admitted scope.
Follow the work through
Use admission to compare payment and capacity effects, and event close to review capture and refund evidence.
What it keeps track of
Data model- Payment evidence
- Provider payment authorizations, captures, refunds and voids.
- Events
- Programs, events and sessions with capacity, lifecycle and revision.
- Registrations
- Participant registration records submitted for review and completion.
- Admissions
- Reserved and admitted admission lines for an event.
- Operation receipts
- Idempotent receipts for guarded operations with expected revision and result state.
Who uses it
Permissions- Finance Reviewer
- , Admissions Lead, Registration Reviewer, Event Owner.
- Finance Reviewer
- Checks the provider event; other roles use the verified result in their own decisions.
Set up Conference Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.