Skip to main content

Payment cards now work across managed profiles

· 3 min read

If you manage bookings on behalf of other members — for example, parents booking for their children — payment cards now work the way you'd expect.

What changed

Payment cards are now stored against your main account, not individual managed profiles. This means your saved cards are available whenever you book on behalf of anyone you manage, and charges always appear on the correct account.

What this means for you

One card, all profiles

Previously, cards added while viewing as a managed profile were stored against that profile only. This meant cards weren't shared between your main account and the profiles you manage. Now, cards belong to the account holder and are available across all managed profiles.

Charges go to the right place

When you book a paid session, purchase a membership, or buy a pass on behalf of a managed profile, the charge is taken from the account holder's saved card. Receipts show the account holder as the payer, which matches what appears on the card statement.

Auto-renewals keep working

Memberships and passes purchased on behalf of a managed profile now record the account holder as the payer. When auto-renewal fires, it charges the account holder's default card — not the profile's. This ensures renewals continue to work as managed profiles become more widely used.

Existing renewals are unaffected

Memberships and passes purchased before this update continue to auto-renew exactly as they do today. No action is required.

If you can't see your card

If you previously added a card while viewing as a managed profile, you may need to re-add it to your main account. Switch back to your own profile and add the card there — it will then be available for all bookings.

What's next

This fix is the foundation for two features we're building next:

  1. Book multiple members at once — select several members and book them all into a session in a single flow, instead of repeating the process for each member.
  2. One payment for multiple sessions — book a member into several sessions and pay once, instead of processing a separate transaction for each.

Both will speed up the booking process and reduce payment processing fees — a direct saving for your club.

Behind the scenes

This update covers every payment path in ClubPal:

  • Session bookings (paid and unpaid)
  • Membership purchases and auto-renewals
  • Pass purchases and auto-renewals
  • Store orders
  • Facility hire bookings
  • Ad-hoc payments

All flows now resolve payments against the account holder, regardless of which profile is active at the time of booking.