Payment of insufficient amount to pay service subscription is unused

[Sandplum]

Payment of insufficient amount to pay service subscription is unused

When a member makes a payment with an amount less than the service subscription, the transaction is unused, and the subscription remains unpaid.

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.


The Users log shows the payment, but does not include the comment shown only in the bank transaction "Amount insufficient to pay service Jäsenpalvelu Extra tila".

[tswfi]

And what do you suggest should be done?

[Sandplum]

Possible solutions:

When a payment is insufficient, 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. (a comment is already added to the new bank transaction)

It would be clever if Mulysa could do some math and apply a below-min payment to add some days to the subscription. I can imagine how this would get complicated fast and create new problems, especially with subscriptions that allow a variable amount to be paid.

For the quickest solution, I suggest improving communication, in order to reduce the time an admin invests in order to find and repair the transaction.

[kengu2]

I think starting with the user log part (if possible) would be a good start.

create a log entry in the Users Log that both the member and the admin staff can read.

[braaar]

I think the user page should definitely show the user that their payment was not accepted. A red banner on top of the page could be good

Something of this nature? The button could be a mailto link to the board or something else. I'm not 100% sure what we actually want the member to do in a situation like this. Just pay more? Whatever it is, it should be clearly asked of them.

Still, email notification would be best.

[Sandplum]

The steps that the member or the admin need to take to address this error (insufficient amount) depend on the situation that caused the error. Let's look back at the example in my first post in this thread, shown in the images. This member was attempting to pay for two different subscriptions that have different reference numbers. A room rental and a door access TKO. The member used the correct reference to pay 40e for the room rental. But they also incorrectly used the same reference number to pay 15e for the TKO. Mulysa posted the 40e payment to the ExtraTila subscription (which has a min value setting of 40e) by matching the reference number to the subscription. Mulysa matched the 15e payment to the same subscription (because it has the same reference number), found that it was below the min value, and left the payment unused.

In this specific situation, what we want is for the member to learn that they have two reference numbers, and need to use the correct number on the associated payment. This would prevent the error from re-occuring and save admin time. In addition, we want to alert the admin that the payment failed. The admin can look at the User Details page in Mulysa and see that the reference number is wrong and make the correction. If Mulysa would create a User Log entry when this type of error occurs, then the admin could spot it quickly in the Users Logs.

---

'

---

This Users Logs page shows the 15e payment, but doesn't mention why it failed. It could, though. That would help the admin NOTICE and then fix the broken payments.