1. Wedding Planning Platform
  2. Features
  3. Payment Evidence
Feature · Payment Evidence

Payment Evidence

Keep the payment provider's authorizations, captures, refunds and voids against each event and verify them.

OverviewUnverified Payment Evidence
Wedding Planning Platform · Payment Evidence

Unverified Payment Evidence

Payment evidence

New
ParentProvider event IDTypeAmount USDOccurred atProvider reference
EVN-92376PEI-911Authorization92024 OctPR-687
EVN-71496PEI-395Capture41022 OctPR-477
EVN-55218PEI-844Refund40026 OctPR-358
EVN-62478PEI-699Void65006 OctPR-320
EVN-30063PEI-324Authorization81013 OctPR-282
6 of 6 records
PEI-911Payment evidence · PE-27315
Authorization
ParentEVN-92376
Amount USD920
Occurred at24 Oct
Provider referencePR-687
Example screen with sample data

What you can do

Act only on payments the provider has confirmed

When guests pay for an event, such as a ticketed welcome party or an excursion, the payment provider sends events: an authorization when the card is approved, a capture when the money is taken, a refund or a void when it is returned or cancelled. Each one is kept as payment evidence against the event, with the provider’s event identifier, reference, amount and time.

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

How the work is organized

  • Evidence stored as received. The provider’s event identifier and reference stay on the record, so the same notification arriving twice is recognized.
  • Verification by finance. The Finance Coordinator checks the evidence against the provider dashboard and marks it verified.
  • Reconciliation at close. When an event closes, admitted guests are reconciled against verified captures.

What to agree during setup

Agree which events take payments and which provider you use. Decide who checks evidence against the provider and how often. Agree the refund policy for cancellations, and who approves a refund. Plan the connection that sends provider notifications into the payment evidence list.

Check the handoff on an actual case

A destination wedding offers guests a paid boat trip the day before the ceremony at $95 a person. A guest pays for two. The provider sends an authorization and then a capture of $190, each stored with its provider reference. The Finance Coordinator checks the capture against the provider dashboard and marks it verified. The Guest Services Coordinator then holds two places on the boat trip, with the provider receipt on the reservation.

A storm cancels the trip. The event is cancelled, the unused places are released, and refunds are prepared against each verified capture for approval. The provider’s refund evidence arrives and is verified, so the trip’s payment record shows each capture and its matching refund.

What your team sees

  • Unverified Payment Evidence — Provider events waiting for the Finance Coordinator to check.
  • Payment Evidence by Type — Authorizations, captures, refunds and voids by event, with amount and verification.

Follow the work through

Plan the payment connection before taking guest payments.

What it keeps track of

Data model
Payment evidence
Provider payment authorizations, captures, refunds and voids
Events
Wedding events with capacity, lifecycle and venue
Admissions
Guest admissions and RSVP reservations for an event

Who uses it

Permissions
Finance Coordinator
, Planning Director, Guest Services Coordinator.
The Finance Coordinator verifies evidence and prepares refunds.
The Planning Director approves refunds on cancellation.
The Guest Services Coordinator holds paid places once a capture is verified.

Set up Wedding Planning Platform your way.

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

How to get started