You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've ended up with a partially paid invoice (the person paid less than half). WooCommerce doesn't show the partial payment. When I click on the pay button it creates a new BTCPay which doesn't recognize the previously paid amount (which is in an older BTCPay invoice).
The original payment is from 20 days ago, so the customer obviously gave up.
Is something misconfigured? Or is this a bug?
The text was updated successfully, but these errors were encountered:
Hey sorry for the late reply, missed the notifications like always ...
You are right that use case is not covered. Partial payments are only tracked on the current invoice but if the customer tries to pay again after the partial invoice expired it will create a new invoice and the old one would not be taken into account in that case. You should still see the partial payment in the orders custom fields
So far nobody had that case it seems (or they worked around it by customer directly contacting them) but yes this case is not covered properly. It is a bit tricky though and would require breaking changes, meaning a new major release as I would need to change the custom field data structure and maybe some rely on the current structure for accounting.
Note to self what needs to be done:
track multiple invoices
not only track multiple paymens, but track multiple payments by invoice id
keep additionally track of fiat amounts as we have different exchange rates on different invoices
I've ended up with a partially paid invoice (the person paid less than half). WooCommerce doesn't show the partial payment. When I click on the pay button it creates a new BTCPay which doesn't recognize the previously paid amount (which is in an older BTCPay invoice).
The original payment is from 20 days ago, so the customer obviously gave up.
Is something misconfigured? Or is this a bug?
The text was updated successfully, but these errors were encountered: