Bug fix·Mon Sep 07·2026-09-07

Account credit top-ups are recorded and credited again

A client who added money to their account balance paid but received no credit, no receipt and no sales row. Top-ups now complete, and a stuck one is completed by the hourly repair job.

When a client added money to their account balance with a card or MobilePay, the payment reached your Stripe account but Booking Bible never finished the purchase: the client's balance stayed at zero, no receipt went out, and the sale was missing from Daily Sales and the client's Billing tab.

Two defects caused it. The payment confirmation handed the finaliser a trimmed copy of the payment's details, which the finaliser then rejected as "not matching"; and the hourly repair job that exists for exactly this case called its database step with a misspelled parameter, so it failed every hour and recorded only "[object Object]" as the reason.

Both are fixed. New top-ups complete immediately. A top-up that was already stuck is completed by the hourly repair job once its two-hour payment window has closed (about three hours at most): the client's balance is credited, the payment appears in Daily Sales and Billing, and the receipt is sent. If a payment is ever refused again, the recorded reason now names exactly which detail did not match.

Alongside this, a scheduled Flexible allowance change now keeps the platform transaction fee and the venue as merchant of record on every billing phase; nothing changes for existing memberships.

Next update

Set pausing and notice periods on the membership itself

A Choose-your-classes membership can now allow or block pausing, set its own pause limits, and carry its own notice period — without changing the rules for everyone else at your venue.

When a client added money to their account balance with a card or MobilePay, the payment reached your Stripe account but Booking Bible never finished the purchase: the client's balance stayed at zero, no receipt went out, and the sale was missing from Daily Sales and the client's Billing tab. Two defects caused it. The payment confirmation handed the finaliser a trimmed copy of the payment's details, which the finaliser then rejected as "not matching"; and the hourly repair job that exists for exactly this case called its database step with a misspelled parameter, so it failed every hour and recorded only "[object Object]" as the reason. Both are fixed. New top-ups complete immediately. A top-up that was already stuck is completed by the hourly repair job once its two-hour payment window has closed (about three hours at most): the client's balance is credited, the payment appears in Daily Sales and Billing, and the receipt is sent. If a payment is ever refused again, the recorded reason now names exactly which detail did not match. Alongside this, a scheduled Flexible allowance change now keeps the platform transaction fee and the venue as merchant of record on every billing phase; nothing changes for existing memberships.

All updates