Refunds
The hotel decides to refund and does it from the panel, with the cap calculated and visible, without going into the payment gateway.
What it solves
Automatic refunds already existed: on cancellation, or when a charge half-failed. What was missing was the most human case — the hotel decides to give something back, for whatever reason — and for that you had to go into the gateway's own dashboard, which is where the expensive mistakes happen.
You notice it in things like these
- To refund $500 you have to log into a system that is not the hotel's.
- You type an amount and the gateway rejects it without saying what the maximum was.
How it works
The cap is shown before you type
The refundable maximum is calculated on the backend and shown on screen. An empty box that does not say how much can be refunded always ends in a rejected amount and a phone call.
Guarantees do not count
A card held as a guarantee never moved money, so there is nothing to refund from it. And what has already been refunded is subtracted from the cap: the same money cannot go back twice.
Not just anyone signs it
Refunding belongs to whoever charges the guest: admin, management and finance. The front desk handles bookings; it does not sign refunds.
And it subtracts where it should
A refund on a booking charged within the yaReserva ecosystem subtracts from what is owed to the hotel with the same breakdown, proportional to what went back. A closed month is never reopened: the refund subtracts in the month it happens.
Where it lives in the panel
- Reservations & stays
- Reservations
- Reservations
Done from the booking page, next to the payment timeline.
What it needs first
A payment actually executed on that booking.
Automatic charging
Carry on here
Shall we walk through it with your hotel on screen?
Half an hour, your rooms and your rates, and whatever questions you have. No commitment and no card.