Cancelling Unpaid Bookings

Nexudus now cancels unpaid bookings more accurately when up-front payment is required. Previously, the system cancelled any booking in a Processing state after the configured timeout — including Direct Debit payments that were legitimately being collected in the background. The cancellation logic now checks whether a payment is genuinely in progress before cancelling, so Direct Debit bookings are protected while abandoned card payments are still cleaned up automatically.

How cancellation works

When Require up-front payment for online bookings is enabled and the cancellation timeout is reached, Nexudus checks the status of the payment before taking action:

• Unpaid — the member did not attempt payment at all. The booking is cancelled and the invoice is voided.
• Processing (credit card) — the member opened the payment widget (for example, Stripe Checkout) but did not complete the transaction. The booking is cancelled and the invoice is voided.
• Processing (Direct Debit) — the member successfully entered their Direct Debit details and the payment is being collected in the background. The booking is not cancelled. The system continues to wait for the payment to clear.

Important to Note: The system determines the payment method from the invoice data and checks the status directly with the payment provider. You do not need to configure this per payment method.

Supported payment providers

The following payment providers are included in the payment status check:

• Stripe Checkout
• Stripe Direct Debit (BACS)
• GoCardless
• Forte
• Spreedly

For all other payment providers, the system falls back to the invoice paid status to determine whether to cancel.