Hi,

We are using Mycred credits to book appointments on Amelia. Using "Mycred Amelia Plugin".

We charge 10 credits for an appointment.

If a user has 10 or more credits in their account then they are able to book more appointments than their actual balance. 

This is only happening with recurring bookings (Services) and it only happens when a user has the balance for the first appointment.

For example, A user has 10 credits. We charge 10 credits for an appointment. While making bookings the user clicks on repeat appointment and choose 5 more time slots. So the total cost is 60. The booking form simply allows the booking and the user's balance goes in minus (-50 credits).

I have checked a similar ticket on this platform for which I am sharing the link:

https://tmsplugins.ticksy.com//ticket/2956129/

In this ticket, you have provided a script for service which is as follows:

<script>
window.beforeConfirmBookingLoaded = function (reservation, bookable, employee, location) {
var totalPrice = bookable.aggregatedPrice ? reservation.bookings[0].persons * bookable.price : bookable.price;
console.log(totalPrice);
}
</script>

This script is used in the Mycred Amelia plugin as well. However this script prints only the first appointment's price and not the total price. We have tried multiple times. That is why the mycred plugin is not able to stop the multiple booking because it is only comparing credit balance with the first appointment's price and not the "Total cost" which includes recurring appointments price.

Sharing screen shot for the same:

Could you please check with your developer team if the following script is supposed to print "Total cost" or "Just the first appointment cost" when making multiple/recurring bookings for Services?

Looking forward to hearing from you guys asap.

Hi Uroš

Thank you for the update. Could you please check if there is a temporary fix available? 

By when should I expect the updated version?

I'll be looking forward to the next update.

Hi Uroš,

We have updated to the latest released version but this issue is still there. We cleared the cache as well. Could you please check why it is still happening?