12-12-2020, 12:15 AM
Dear Zakers,
in the latest releases we have introduced new payment gateways that can be integrated on the Online Reception.
These payment gateways can also be used for another purpose: to request for each booking, regardless of whether it was entered manually, from the channel manager, via booking engine, a payment confirmation.
Now, we are working on improving things further. The project is called rShield. It's not about sending a probe to saturn or some dynamite innovation.
Quite simply, the goal is to provide powerful and simple tools to manage less or not guaranteed reservations. In order to make your work easier and safer.
The credit card itself, due to the PSD2, is already a very little reliable protection.
So how do we want to proceed?
Easy:
1. Allow you to flexibly define your booking guarantee policies
2. At this point, make the guarantee request just a click away
3. Issue warnings to notify you about upcoming bookings without sufficient guarantees
4. Then automate things, so that Zak can automatically make decisions
In addition to payment, we will introduce the "validation" of credit cards. It means asking the user, when he leaves his card as a guarantee, for his permission to subsequent charges. Which is not the pre-authorization: it seems that the way of the pre-authorization is very limited in the hotel sector: the amount is freezed for one or two weeks (and therefore very advanced bookings are completely uncovered) and refund practices are difficult and slow.
We are writing these few lines for a public discussion.
We are relatively sure that this path will gain importance in the next weeks and months. And that a direct confrontation with you can only improve the shot, as usual!
Nancy (aka Ginger)
in the latest releases we have introduced new payment gateways that can be integrated on the Online Reception.
These payment gateways can also be used for another purpose: to request for each booking, regardless of whether it was entered manually, from the channel manager, via booking engine, a payment confirmation.
Now, we are working on improving things further. The project is called rShield. It's not about sending a probe to saturn or some dynamite innovation.
Quite simply, the goal is to provide powerful and simple tools to manage less or not guaranteed reservations. In order to make your work easier and safer.
The credit card itself, due to the PSD2, is already a very little reliable protection.
So how do we want to proceed?
Easy:
1. Allow you to flexibly define your booking guarantee policies
2. At this point, make the guarantee request just a click away
3. Issue warnings to notify you about upcoming bookings without sufficient guarantees
4. Then automate things, so that Zak can automatically make decisions
In addition to payment, we will introduce the "validation" of credit cards. It means asking the user, when he leaves his card as a guarantee, for his permission to subsequent charges. Which is not the pre-authorization: it seems that the way of the pre-authorization is very limited in the hotel sector: the amount is freezed for one or two weeks (and therefore very advanced bookings are completely uncovered) and refund practices are difficult and slow.
We are writing these few lines for a public discussion.
We are relatively sure that this path will gain importance in the next weeks and months. And that a direct confrontation with you can only improve the shot, as usual!
Nancy (aka Ginger)