Related OR Support Case #: (#73748)
Background: We took a booking through VRBO- but we handle the credit card transactions (including local meals and rooms tax) via Bambora. This booking was for a date in the future (few months out). The client chose to pay 50% up front at time of booking, and then the balance as the date approached. They had to cancel their reservation, but far enough out where our policy would give them 97% back- and we agreed to refund them that (knowing we'd most likely rebook). Keep in mind- they had only paid 50% of the total.
When we went in to handle the cancellation/refund- the automated options to refund our configured 97%. However, when I looked a little closer- I noticed that the refund was going to amount to 97% of the total for the stay. That means the amount being queued up to refund to the cancelling renters wouldn't be correct. I believe the correct amount to refund would be the 97% of what had been collected at that point, and the rest could be made to disappear in the OR backend accounting.
Had I gone through with what OR was suggesting as part of the
At least I think that's how it should work as an option at leas.
Feature request: Take into account how much has been paid- and calculate refund % amount based on that number, or at least give a couple of different options on how to handle it when we get to the Cancellation screen. (ie. maybe add this option for 97% of amount collected *to date*).
Caveat: So I'm still waiting on 100% confirmation back from my credit card processor (Bambora), but I'm 99% sure the fee (~2.5%-3%) is taken on every credit card swipe. If that is indeed the case, then my feature request may be useful for people.
