Refunds now confirm the original card payment before completing
Refunds for paid recurring invoices can no longer appear complete unless the exact original Stripe payment is identified and the refund is sent to it.
Some paid recurring invoices did not save the Stripe payment reference needed for a later refund. In that situation, a refund could previously be marked complete in BookingBible even though no money was sent back through Stripe. Refunding to the original payment method now verifies the paid invoice, amount, currency, Stripe account, and charge before any refund is started. If those details cannot be proved, the refund stops with an error and does not change the payment or tell the client it succeeded. Paid-invoice recording now performs the same check when Stripe sends an invoice event, including when Stripe leaves the payment details out of the event itself. For affected historical records, Finance has a guarded, preview-first reconciliation operation. It can link an independently confirmed Stripe refund to exactly one matching local refund without repeating credits, access changes, receipts, or accounting effects. Ambiguous records remain blocked for review.
Private-session clients now hear about edits, roster changes and payment links
Editing a confirmed private session can now tell the client what changed, adding or removing a participant emails them automatically, and you can send a secure payment link by email or text straight from the booking's Payment tab.