Client cannot do partial refund

I have a clients site that doesn't allow her to do a partial refund using Paypal express

ZenCart version 1.3.9f

I enter the amount of the refund (which is less than the total)
Click the partial refund button
Egg timer comes on, and browser status bar says waiting

Then nothing...
Egg timer goes off, status bar showing waiting goes away.
Customer is not refunded. Checked in Paypal and check against order status in Zencart.

Order amount is £18 + £2.50 postage
Client is trying to refund £19

Does anyone know what this could be as it's got me baffled?

Might be a glitch in the old version you're using. I don't remember off the top of my head whether that was something fixed in 1.3.9g or 1.3.9h or maybe even later.

But a very simple workaround is to log into PayPal and do the refund there. And if there's a problem imposed by PayPal then PayPal will explain exactly why right there on-screen while they're looking at it.

Thanks for the reply.

I'd rather not go up the upgrade path unless absolutely necessary as this is a live and busy shop and I wouldn't want it down just whilst I apply a series of fixes, just to find out it still doesn't work.

paulcreedy:

I'd rather not go up the upgrade path unless absolutely necessary as this is a live and busy shop and I wouldn't want it down just whilst I apply a series of fixes, just to find out it still doesn't work.
If you're having no problems then maybe you don't need to fix anything. There were bugs, which were fixed, thus the new versions. But if you're having no problems and you're absolutely certain no bugs need fixing, then you can leave it as is. Granted, you came here posting about a problem, so that suggests maybe it's worth considering upgrading.
The development team doesn't issue releases for no reason.
Just my 2cents.

You have a workaround, if you choose to do nothing.

Point taken

As this is a busy clients website I have to way up the inconvenience and risk of the site being offline for too long with the glitches.

If I can confirm this was a recognised glitch that was fixed in update xxxx then I can reconsider the risk. Updates never seem to go 100% well in my experience and come with their own complications.

Better the devil you know sometimes :-)