1. Salon Management System
  2. Features
  3. Payment Evidence
Feature · Payment Evidence

Payment Evidence

Read provider payment events against the booking without treating an authorization or quote as collected cash.

OverviewPayment Event Review
Salon Management System · Payment Evidence

Payment Event Review

Payment evidence

New
ParentProvider event IDTypeAmount USDOccurred atVerified
BKN-80672PEI-535Authorization57003 Oct
BKN-81581PEI-633Capture9015 Oct
BKN-18286PEI-479Refund93008 Oct
BKN-57673PEI-692Void62010 Oct
BKN-33825PEI-765Authorization55010 Oct
6 of 6 records
PEI-535Payment evidence · PE-59108
Authorization
ParentBKN-80672
Amount USD570
Occurred at03 Oct
Verified✓
Provider referencePR-139
Example screen with sample data

What you can do

Explain what the payment provider actually recorded

The booking carries a quoted USD amount, while payment evidence records events from the provider. Payment Reviewer examines the event type, amount, provider identity and verification state against the relevant booking. This makes it possible to discuss a deposit or later payment outcome using the provider’s evidence.

For a visit quoted at $85, the provider might first record a $20 authorization and later a $20 capture. Those events describe different stages of the payment. Adding both as though the salon collected $40 would misstate the result. The reviewer must distinguish event types and verify the supporting provider reference.

How the work is organized

  • Provider identity. Each event retains the provider event identity and reference. Use them to connect the payment evidence to the actual event and to identify repeated delivery of the same information.
  • Event meaning. Authorization, Capture, Refund and Void remain separate. Read the type before interpreting the amount or deciding whether the deposit policy has been satisfied.
  • Verified evidence. The verification state distinguishes evidence the team can rely on under its policy from an event still requiring investigation. An unverified external result should prompt review rather than an unsupported completion claim.

What to agree during setup

Choose the payment provider and agree how its events reach the booking. Define the evidence needed to verify the source and the meaning of each event. The provider connection needs its own identity mapping and error owner so reception knows who investigates a missing or conflicting result.

Booking Supervisor and Payment Reviewer should agree how the deposit policy uses verified evidence. Decide which event types satisfy the policy and how partial amounts are handled. Keep refund or void evidence separate from booking cancellation: changing the appointment state does not by itself establish that the provider moved money.

Check the handoff on an actual case

Prepare the $85 booking with the authorization and capture events for its deposit. Payment Reviewer confirms the event identities, types and provider references. Booking Coordinator uses the agreed verified evidence when checking whether the held appointment can be confirmed.

Repeat the rehearsal with an event that has not been verified and another delivered more than once. The team should be able to explain the unresolved item without counting it as additional money or assuming the booking is ready for confirmation. Investigate the provider source before changing the evidence’s meaning.

Next, cancel an eligible visit and examine any separate refund or void event from the provider. Preserve both the appointment history and the payment history. Reconciliation should identify the actual supported outcome and route any discrepancy for review. It should not issue a new payment operation merely because the original event is uncertain.

What your team sees

  • Payment Event Review — Provider events with their type, amount, reference and verification state.
  • Completed Bookings — Service outcomes and quoted values for comparison with the payment evidence.

Follow the work through

Use payment and outcome reconciliation and cancellation and correction to rehearse payment and appointment outcomes together.

What it keeps track of

Data model
Payment evidence
Provider payment events reconciled against a booking
Bookings
Salon appointment bookings with lifecycle, schedule and quoted amount
Operation receipts
Durable receipts for every guarded operation executed against a booking
Record attachments
Uploaded evidence files attached to a booking

Who uses it

Permissions
Payment Reviewer
Examines and reconciles provider evidence.
Booking Coordinator
Checks deposit readiness.
Booking Supervisor
Resolves policy questions.
Auditor
Reads the retained history.

Set up Salon Management System your way.

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

How to get started