1. Virtual Event Platform
  2. Features
  3. Evidence Center
Feature · Evidence Center

Evidence Center

Keep payment provider evidence and supporting files against each event and verify them.

OverviewUnverified Payment Evidence
Virtual Event Platform · Evidence Center

Unverified Payment Evidence

Payment evidence

New
ParentProvider event IDTypeAmount USDOccurred atProvider reference
EVN-99922PEI-251Authorization44010 OctPR-905
EVN-47740PEI-271Capture58007 OctPR-948
EVN-32051PEI-155Refund17025 OctPR-442
EVN-45449PEI-526Void45017 OctPR-939
EVN-36479PEI-516Authorization38024 OctPR-370
6 of 6 records
PEI-251Payment evidence · PE-13641
Authorization
ParentEVN-99922
Amount USD440
Occurred at10 Oct
Provider referencePR-905
Example screen with sample data

What you can do

Keep the proof with the event

Two kinds of evidence sit against each event. Payment evidence records what the payment provider reported for paid tickets: authorizations, captures, refunds and voids, with the provider’s event ID, reference, amount and time. Supporting files record what the team relied on: run sheets, speaker confirmations, sponsor agreements and session outlines, each with a title, evidence type, uploader, upload time and visibility of Internal or Shared.

The Finance Coordinator verifies each piece of payment evidence. Only a verified capture lets a paid attendee be admitted, and refunds on cancellation are prepared only against verified captures.

How the work is organized

  • Payment evidence as received. The provider event ID is kept once, so a repeated notification is recognized.
  • Verification by finance. The Finance Coordinator checks evidence against the provider dashboard and marks it verified.
  • Files by type and visibility. Evidence types help reviewers find the right file; Shared files may go to speakers and sponsors.

What to agree during setup

Agree which events are paid and which provider you use. Decide who verifies payment evidence and how often in the days before an event. Agree the refund policy for cancellations. List the evidence types you use for files and which may be shared outside the team.

Check the handoff on an actual case

A training company sells tickets to a paid online workshop at $149. A buyer purchases three seats for her team. The provider sends an authorization and a capture of $447, each stored with its provider reference. The Finance Coordinator checks the capture and marks it verified, and the three registrations can be admitted on the day.

Another buyer’s capture arrives twice because of a provider retry. The second notification carries the same provider event ID and is recognized, so one capture is kept. Before the event, the Event Coordinator attaches the trainer’s slide deck as an Internal file and the attendee workbook as a Shared file.

What your team sees

  • Unverified Payment Evidence — Provider events waiting for the Finance Coordinator to check.
  • Evidence Files — Files attached to each event, with type, visibility and uploader.

Follow the work through

Plan the payment connection before selling tickets.

What it keeps track of

Data model
Payment evidence
Provider authorization, capture, refund and void evidence for event payments.
Record attachments
Uploaded evidence files attached to an event with a visibility scope.
Events
Virtual events moving through draft, review, approval, open and completion.
Team members
Authenticated platform identities with an operational role inside an organization.

Who uses it

Permissions
Finance Coordinator
, Event Coordinator, Program Manager.
The Finance Coordinator verifies payment evidence.
The Event Coordinator and Program Manager attach supporting files.

Set up Virtual Event Platform your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started