Hello Jaffer,

Thank you for reaching out to us.

Can you please provide me with a screenshot of the issue that you are dealing with?

Looking forward to your reply.

Hello Jaffer.

It seems that you configured the service so the customers will have to pay for all appointments at once:

The recurring appointments logic is the same for the payments as it is for the creation of the appointments - they are separated.

What I mean is this:

A service that costs $20, and has a deposit of $10, which handles recurring payments by paying all at once multiplies the deposit by the number of appointments:

So, if a customer books a recurring appointment, they will not pay $10, but $30:

So, in the back-end, it's the same as in your video:

This is normal and in your case, the customer didn't pay $7.5 in total, but instead 3 x $7.5 = $22.5.

Thank you Jaffer.

I had to see it to believe it, but you're right - when WooCommerce is used, the deposit amount for recurring appointments is applied to all appointments.

I forwarded this to our developers, so they can work on it for one of our upcoming updates.

Sorry for the inconvenience and thank you for pointing this out!

You're welcome, Jaffer.

Our developers logged it as a bug and they started working on it.

I hope they'll have enough time to fix it for our next update, but I can't promise you that. It should be released in about 2 weeks, but they are still finishing up with previous tasks created for this update, so if they finish those on time, they'll most likely include the WooCommerce fix as well.

Hey Jaffer.

All issues with deposit payments and WooCommerce have been tested, and they will be included in Amelia 6.4 which should be released within a few days.

There are still a few more tasks that need to be tested, so once that done, we'll release the update.