Payment for suspended TKO subscription is unused

[Sandplum]

Payment for suspended TKO subscription is unused

When a member makes a payment with the TKO reference number while the TKO is suspended, the transaction is unused, the subscription remains Suspended, and the member and admin staff are unaware.

While suspended subscriptions should require an admin to authorize and restart the subscription, communication could be improved.

This is what the member can see on their User page (*redactions added by author) -->

---

`

'

---

---

`

---

The Bank transactions page in Django admin shows the transaction is unused.

---

`

'

---

---

'

---

[Sandplum]

Possible solutions:

When a TKO subscription is in the Suspended state, and a new payment for that reference number is received, send an email to the member. This email could be similar to the Door Access Denied email. Also, create a log entry in the Users Log that both the member and the admin staff can read. And add a comment to a new bank transaction that is unused due to Suspended TKO.

As a prevention measure, send an email to the member when a subscription changes from Active or Overdue, to Suspended.

[kengu2]

I would think, it could just backfill the payments of the suspended service, i.e. map to correct person and service. It would not change the status but instead of service being 45 days overdue it would then only be 15 days.

I am not sure what is the initial logic of dropping the processing of suspended service payment.

Why would we create extra work to map payments?

AND
surely the member should be made aware of payments lagging behind.

[braaar]

I think at the very least, the user should be told in very clear terms what is going on and why their membership/service isn't active despite them having made a payment. A big red banner, like what I commented in #511 (comment) would be good.

[braaar]

I agree that email notification would be best here. People probably don't hop into mulysa to check stuff on their own initiative.