Membership
Membership billing, run on the same payment layer as everything else.
A member profile with a tokenized card on file. Charge it for one-off incidentals — damages, overages, post-charges — or run operator-triggered recurring dues, monthly fees, and club subscriptions against the same saved card. One payment layer, one identity, full operator control.
Why it works
One place to save a card. One place to charge it.
One payment layer, not two
Most membership and recurring-charge tools run on their own billing engine, separate from the POS. That gap is where failed charges and un-billed incidentals hide. Vitabyte runs member charges through the same payment layer that runs every other transaction.
Built around the customer profile
A saved card is attached to a customer — not a standalone subscription object. That means the same card that covers membership dues can also cover a post-charge after the member leaves, with both posting under the same identity.
Operator-run, not black-box
Each charge is triggered from the customer profile — by an operator or by an external scheduler hitting the API. There is no automated dunning engine or retry logic hidden underneath. That means full control, and full visibility into what was charged, when, and by whom.
Capabilities
Everything you need to save a card and charge it later.
Card on File
Save a guest's card once. The card is tokenized through the Vitabyte payment layer and stored against the customer profile — ready to be charged any time, for any amount.
One-Off Charges
From the customer profile, charge any saved card for any amount — damages, overages, event fees, post-charges after a member leaves, invoice items. The operator enters amount, tip, tax, and an invoice reference.
Recurring Use
The same saved card powers operator-run recurring billing — monthly dues, club fees, subscription services. Each cycle is posted by the operator or an external scheduler against the stored token.
Customer Identity
Each saved card lives on a customer profile looked up by phone or email. Every charge rolls up under the same profile, alongside transactional history.
Tokenized, Not Stored
Card data never sits on the operator's system. The saved card is a token — the real PAN lives only with the payment processor.
Fit
Built for where the guest isn't transactional.
Private clubs. Golf and country clubs. Gym and wellness memberships at resorts. Residence clubs. Loyalty tiers at hospitality groups. Anywhere the relationship with the guest is ongoing — not just the transaction in front of you.