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.
- Fitness Trainer Platform
- Features
- Payment evidence
Payment evidence
Keep provider-confirmed payment events linked to the training booking.
OverviewPayment Evidence List×
Fitness Trainer Platform · Payment evidence
New
Payment Evidence List
Payment evidence
| Name | Parent | Type | Amount USD | Provider event ID | Verified | |
|---|---|---|---|---|---|---|
| Evidence 456 | BKN-56688 | Authorization | 140 | PEI-417 | Unverified | |
| Evidence 509 | BKN-32384 | Capture | 640 | PEI-576 | Unverified | |
| Evidence 924 | BKN-11324 | Refund | 70 | PEI-947 | Unverified | |
| Evidence 452 | BKN-81203 | Void | 310 | PEI-386 | Unverified | |
| Evidence 745 | BKN-34791 | Authorization | 60 | PEI-934 | Unverified |
6 of 6 records
Evidence 456Payment evidence · PE-34501
AuthorizationParentBKN-56688
Amount USD140
Provider event IDPEI-417
VerifiedUnverified
What you can do
Read payment events in booking context
A booking carries a quoted amount. Payment evidence records a provider event against that booking, with an event identifier, reference, type, amount, occurrence time and verification state. Authorization, Capture, Refund and Void have different meanings; the team can read each event by type without treating them as the same cash movement. The evidence list lets a payment reviewer compare a booking’s commercial record with the provider events supplied for it.
The verification label distinguishes an event the team has checked from one still awaiting confirmation. A provider reference gives the reviewer a way to reconcile a local record with the connected payment provider. The platform stores that confirmation evidence; the provider handles the payment transaction. A coordinator can consult the evidence before confirming a booking where a deposit is required.
How the work is organized
- Booking holds the quote. The quoted amount remains on the training appointment.
- Provider event is linked. Each event points to the relevant booking and carries a stable provider identifier.
- Reviewer verifies context. The event type, amount and reference are checked before the team relies on it.
What to agree during setup
Identify the payment provider and decide how confirmed events enter the app. Agree who verifies incoming evidence, which event types are relevant to booking confirmation and how a refund is matched to the original booking. Record the provider reference in a consistent form so the reviewer can locate the source transaction. Set a rule for duplicate provider event identifiers; a replay should not create an additional financial conclusion.
Select a small rehearsal set: a deposit authorization, a captured payment, a cancellation with a refund and an event awaiting verification. Compare the event amount with the quoted amount, but preserve the distinction between quote, authorization and actual capture. If a provider event is delayed, the coordinator should leave the booking at the appropriate stage until the agreed evidence has arrived.
Check the handoff on an actual case
A client requests a private training appointment with a quoted amount. The coordinator holds the interval while the deposit condition is checked. The provider confirms an authorization and sends an event identifier and reference. The payment reviewer records the event against the booking and marks it Verified after checking the provider details. The coordinator can then inspect that evidence during confirmation.
Later the client cancels within the agreed window. A provider-confirmed refund arrives as a separate event on the same booking. The reviewer records it as Refund, retaining both the earlier authorization and the later refund. The team can read the sequence without overwriting the first event.
What your team sees
- Payment Evidence List — Provider event type, amount, verification and booking link.
- Bookings List — Quoted amount and booking status while the coordinator reviews payment context.
Follow the work through
Payment verification follows the event from provider reference to booking context. Completion evidence covers the final check.
What it keeps track of
Data model- Payment evidence
- Provider-confirmed payment events associated with bookings.
- Bookings
- Scheduled training bookings with guarded lifecycle and execution evidence.
- Operation receipts
- Idempotent receipts for guarded actions and their persisted effects.
Who uses it
Permissions- Payment Reviewer
- And Booking Coordinator.
- The reviewer verifies provider evidence; the coordinator checks it against the appointment.
Set up Fitness Trainer Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.