The ban plus renewal example is a distributed systems problem wearing a creator tooling costume. Two services holding authority over the same state, membership, with no coordination between them. The fix you landed on is the right one: a single owner of re-admission, with an operator reviewing exceptions. That principle holds whether the tools are two Telegram bots or two microservices.

Also good catch that a payment retry must not extend the paid period twice. That is idempotency keyed on the payment, and it is the detail that quietly separates tooling you can trust from tooling you babysit.