Customer balance in multi currency shops

Hi seyi, I hope all is well :).

I'm facing an issue regarding "AwoCoupon's Customer Balance" when switching currency.

My base currency is Swedish SEK (kr).

I have enabled the "Customer Balance" module and it shows up nicely on my checkout page (Rupostel OPC).

I can apply my remaining balance by clicking the "Apply" button :

But when another currency is used... it's no longer giving the correct value.

For example, 1 Swedish SEK equals around $1.13 USD, but this is not what is shown in case the customer have selected USD :

This is obviously a big problem - am I missing something? Is AwoCoupon not yet supposed to work with multi currency shops? :/. Please let me know what's going on :).

Thanks!

Best regards

Peter

Hi, unfortunately no change - opc is disabled (and protostar enabled, even)

1. customer has 10 (swedish crowns) in store credit. before applying the credit, the total is 138 kr (SEK / Swedish Crowns)

2. Customer apply credit. New total is 128 kr (correct, obviosuly)

3. But if instead I select "USD" as my currency, the discount given is still only $0.12 USD (less than one Swedish Crown) :

Please advise :)

Thank you

Best Regards

Peter

---

Think I might have found the issue - a conflicting plugin, as usual :). Please let me investigate further and I'll report back what happens :) Thanks

---

Hi again, although disabling the conflicting extension solved some js problems, the awocoupon currency issue is still there.

Same results with OPC disabled.

As a test I have created two coupons.

Coupon "hertsi" is created in awocoupon and is worth 43 Swedish Crowns.

Coupon "hertsi2" is created as a native vm coupon and also worth 43 Swedish Crowns.

I apply "hertsi" while my currency is SEK and it works fine :

Coupon "hertsi" gives wrong value once I switch from SEK to USD :

while "hertsi2", the native vm coupon works fine regardless of currency

I suspect this is highly related to why the "customer balance" isn't working for me either.

Please advise. Thank you!

Ok, please get latest, 3.5.6.0.  I believe this issue is fixed there.

Hi seyi, I only had time to take a quick look this morning but it looks like it works now. Thanks for taking care of it so quick, I truly appreciate it :)