Consent and Payment Evidence

Front Desk prepares the supporting material needed for confirmation, including consent evidence under the salon’s agreed document convention. Attached files retain their booking link, title and uploader. Payment Reviewer checks the provider events associated with the same booking so the confirmation discussion uses an identifiable payment reference.

Payment evidence distinguishes Authorization, Capture, Refund and Void. Each event records its amount in US dollars and whether it is verified. Keeping those event types visible helps the reviewer explain what the provider evidence represents before the team applies the configured deposit rule to the held booking.

• Consent material. Front Desk attaches the relevant file and records its evidence type. The title should help the reviewer recognize the document without opening unrelated material from another appointment.
• Provider context. Payment Reviewer checks the event identity, provider reference and verified state. A capture and an authorization carry different meanings, so the review retains the event type alongside the amount.
• Confirmation handoff. Front Desk runs the confirmation action after the required consent and deposit evidence is available. The action moves an eligible Held booking to Confirmed and records its outcome.

Agree which evidence type identifies consent and what the reviewer must check before confirmation. Define who can read Internal and Shared attachments under the salon’s access settings. A visibility label should have a clear operating meaning for the people handling the files.

Set up the payment-provider connection and establish how its verified events are linked to the intended booking. Agree which event types and amounts satisfy the deposit policy. Use the booking’s quoted amount and the provider amount consistently in US dollars when reviewing that rule. If effective exchange rates are needed for a connected process, agree the conversion method with the source owner before using a converted result.

For a rehearsal, choose a held booking quoted at USD 120 and configure a deposit requirement of a verified USD 30 capture plus the required consent file. Payment Reviewer compares a USD 30 Authorization event with a USD 30 Capture event. Under this example policy, the authorization alone does not satisfy the deposit requirement. Check that the verified capture belongs to the intended booking.

Repeat with the required consent absent or the capture unverified. Confirm that the appointment remains unconfirmed. Complete the evidence through the agreed source process, then follow the supported retry path. Keep the earlier outcome available. Front Desk should be able to locate the specific consent file and Payment Reviewer should identify the provider event supporting confirmation, including its amount and type.

• Payment Event Review — Inspect provider event types, verified state and amounts against the parent booking.
• Booking Attachments — Locate supporting files with their evidence type, visibility and uploader.
• Held Bookings — Follow appointments awaiting the confirmation handoff.

Use Booking request to confirmation for the evidence rehearsal. Agree source mappings in Integrations.