A recurring membership in the Business app now has a Subscription billing
screen, matching what staff already do on the web subscription editor. It
appears on the pass card for memberships only — clip cards and time passes
never show it.

Payment history: staff can see which billing period the membership is in, what
the next payment will be and when it is due, whether the membership is set to
stop at the end of the period, and the card on file. The last twelve payments
are listed with whether each one went through, and a failed one can be opened
in full.

Moving the next payment date: staff pick a new date and the next charge moves
to it. Nothing extra is charged or refunded for the shift. The date has to be
in the future and within a year, and the app says exactly why if it is not.

Changing the price: staff set a new amount and it applies from the next payment
onward. Earlier payments are untouched, and any agreed price already saved for
a specific period still wins for that period.

Comping or repricing individual payments: staff can set an agreed amount — or
zero, for a covered period — on the next few payments, or on every payment in a
date range. The screen shows the next six upcoming payments exactly as they
will be charged, so nobody has to work out the dates. A payment can be edited
or put back to the normal price, several can be changed at once, and once a
payment has actually been taken it is locked and clearly marked as such.

If a membership's billing has not started yet — a membership imported from a
previous system, or one waiting to resume — the screen says so and still saves
the adjustment. It applies automatically on the first charge once billing
resumes.

Switching membership type: staff pick another recurring membership the venue
offers, see exactly what will be charged or credited and when the change takes
effect, and then confirm. Upgrades take effect straight away; downgrades are
scheduled for the end of the paid period. The same change started on the web
cannot be applied twice from the app, or the other way round.

None of these actions contacts the client automatically. Every screen starts on
"Don't notify" and staff choose Email, SMS or Push per action; a channel a
particular client cannot receive is shown with the reason rather than failing
quietly.

Which staff can do what: reading the payment history needs the same permission
as managing passes. Every change — the date, the price, the per-payment
adjustments and the type switch — needs the billing permission, and sending a
notification needs the notification permission on top.