GuestPay Hub

The GuestPay Hub has been designed as a one-stop shop for all things payment related. Bringing together payment activities and building on these to offer additional visibility for a smoother user journey.

The Hub is located as a new tab within the Rezlynx PMS Homepage.

Elements of the Hub will display based on other user access rights. For example…

• a user must be a member of the ADMINS user group in order to access the configuration areas.
• a user must have access to PayLinks Overview in order to see PayLink information
• a user must have access to Payments Reconciliation in order to see reconciliation and chargeback reporting

What's included in the GuestPay Hub?

• Actions required
• Configuration
• PayLinks
• Pre-Auth management
• Reporting
  • Funding Reconciliation
  • Chargeback notifications
  • Adjustments
• Payment Issues
• Link to MySt Portal
• Transaction Search - Reduces the need to access MyST

Action Required Section

Suspended Payments
When processing a payment these are classified as an AUTH and will typically have a status of PENDING, until they are SETTLED. However, if an AUTH has a status of SUSPENDED, this will not result in a payment. A SUSPENDED AUTH is essentially a pre-authorisation. The funds are being held, but will not result in a payment unless completed (moved to PENDING).

What can result in an AUTH becoming SUSPENDED?
Currently for MOTO & ECOM transactions we don't have any flows where we would intentionally leave an AUTH in a SUSPENDED state. With that in mind, there are only 2 flows to be aware of:

Logic on the Trust Payments side changes the status of the AUTH to SUSPENDED. This could be caused by:

• A rule configured to do so based on a criteria - i.e. PostCode does not match
• Trust Payments Fraud Check System - A transaction is suspended if it reaches a Fraud Score of 5 or above

A broken DBM Booking. The process in DBM is that when a Payment is taken, DBM requests Pay to create a SUSPENDED AUTH. Once the booking is sent to Distribution and Distribution confirms it is successfully received, then DBM requests for the AUTH the be completed (moved from SUSPENDED to PENDING). If Distribution is unable to confirm the booking, for example there is no longer availability, then DBM should request for the AUTH to be CANCELLED. On very rare occasions this may not happen.

Overdue PayLinks

Any PayLink that is UNPAID and the Due Date is in the past will display in these results.

Unreleased Pre-Auths
This will display a count and list of any pre-auths on Checked-out bookings that have NOT been released.

Payment Failures that may require re-processing
This typically shows any bookings from Distribution where the booking was successful, but the Card Tokenisation failed.

Chargeback Notification Onboarding
Users with access to Payments Reconciliation will also be informed if the site has not yet provided an email address for notifications. Once provided, when chargeback or fraud notifications are received, they will automatically be sent to the site.

Notification Email Settings
We have a new system for sending Chargeback and Fraud notifications. Users will be informed if we're not holding an email address for these. Once supplied we will automatically send these notifications to the supplied address. For a while this may mean you receive duplicate notifications from both the old and new system.