How QCMM Finalizes a Meeting Booking After Payment

Explain the transaction-safe handoff from paid/free checkout into the authoritative booking, subscription, billing, and calendar state so payment and appointment inventory stay consistent.

Finalization Is a Verified Handoff

QCMM does not treat a browser return alone as proof of a purchased appointment. Finalization verifies the billing record, customer, subscription, protected Meeting Time hold, Plan relationship, capacity, and payment evidence required by the payment path.

Paid PayPal Checkout

For a captured PayPal payment, QCMM requires the completed capture event to bind to the same billing/customer/subscription relationship and verifies the captured amount and currency against the billing record. Local free or account-credit checkout instead requires a fully paid local billing record with no balance due.

Atomic Booking Creation

Inside the finalization transaction, QCMM locks the customer and relevant records, confirms exactly one protected Meeting Time, rechecks the Scheduling-enabled Plan/Host assignment, customer conflicts, provider entitlement snapshot where applicable, and remaining capacity. It then creates the confirmed booking linked to the hold, billing record, subscription, payment evidence, Host, Plan, Meeting Time, and attendee count.

Subscription and History

The scheduled subscription end is recalculated from the authoritative Meeting end plus the Plan's entitlement grace. QCMM writes booking history with a purchase-confirmed action and marks the hold consumed.

Retry Safety

The billing ID acts as the durable purchase-level idempotency key. If a safe retry reaches finalization after the booking already exists, QCMM returns the same matching booking rather than creating a duplicate appointment. Ambiguous capacity or relationship failures stop automatic finalization for review instead of guessing.

Community Discussion

Want to compare scheduling workflows or share practical QCMM tips? Visit the QC Memberships & Meetings Community. For private support, bug reports, account-specific entitlement or billing problems, or feature requests, use the QuantaCade support system.