Bookings Deposit Collection with Stripe

Overview

This flow secures revenue upfront for Microsoft Bookings. When an appointment for a deposit-required service is created, it creates a Stripe Checkout Session for the deposit, emails the customer a secure payment link with a deadline, holds the slot for the configured window, then re-checks payment: if paid it confirms; if unpaid it cancels the appointment via Microsoft Graph (releasing the slot) and notifies the customer.

Why it matters: Deposits dramatically reduce no-shows for high-value services. Automating the pay-link, the hold, and the release removes manual chasing and protects the schedule.

Build: single cloud flow, ships Off, Flow Checker 0 errors / 0 warnings.

Use Case

A business offering deposit-required Bookings services (consultations, premium sessions) wants deposits collected automatically with a hold-and-release policy, with zero manual follow-up. Finance secures revenue upfront; Operations keeps the calendar clean of unpaid holds.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Microsoft Bookings	shared_microsoftbookings	CreateAppointment
Office 365 Outlook	shared_office365	SendEmailV2

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Multiple deposit services

Swap the single-name gate for a comma-list env var and contains(split(...),','), ServiceName).

Dynamic deposit amount

Replace the fixed Price ID with price_data (amount as a % of the service price) in the Checkout Session body.

Apply deposit to the total

Store the Stripe payment_intent id (e.g. in Dataverse) and deduct it from the final invoice.

Auto-refund on timely cancellation

Add a Stripe POST /v1/refunds branch keyed off a cancellation trigger.

Real-time confirmation

Instead of the Delay + re-check, point a Stripe checkout.session.completed webhook at a companion Request-triggered flow to confirm the moment payment lands.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@equals(triggerBody()?['ServiceName'], variables('varDepositService'))

@addHours(utcNow(), int(parameters('EnvVar_DepositDeadlineHours')))

@{concat(variables('varStripeBase'),'/checkout/sessions')}

mode=payment&line_items[0][price]=@{parameters('EnvVar_StripeDepositPriceId')}&line_items[0][quantity]=1&customer_email=@{encodeUriComponent(triggerBody()?['CustomerEmail'])}

@equals(body('Get_Stripe_Checkout_Session')?['payment_status'], 'paid')

@{concat(variables('varGraphBase'),'/solutions/bookingBusinesses/',parameters('EnvVar_BookingsBusinessId'),'/appointments/',triggerBody()?['Id'],'/cancel')}

Customize & download