Payment Gateway Enhancements

Profile Selection

Previously, if multiple profiles were in play, the user would be asked to select one. This step is now skipped. When the Payment Page loads it will be pre-populated using the Contact Profile. If there is no Contact Profile, the Guest Profile will be used.

Add Deposit

After processing a successful payment, a deposit will automatically be added to the booking if the booking is NOT Resident, Cancelled or Checked-out. Historically the user would be presented with a pop-up asking them if they wanted the deposit to be added. The deposit is added using the new Payment Type Mapping that's part of the new implementation

Payment Type Mapping

Due to the automation of adding the deposit, the selection of the payment type to be used is automated based on the configuration with Pay Config.

Payment Page

The Payment page is simplified. Fewer steps, no need to select the card type and the UI renders the inputs of the Card Pan in a way that is easier to see.

Display of Tokens

Token information now displays on the Guarantee page and the user no longer needs to click on a token to see the detail.

Merchant Initiated Transactions

Otherwise known as MITs. When a payment is taken from existing token, the user must now supply a Merchant Initiated Transaction Reason. This process will help to reduce chargebacks.

Suspended Transactions

Occasionally when taking a payment it can be successful, but transition immediately to ‘Suspended’. The user will now be informed of this.

Gateway Portal URL

The Token in the new grid is a hyperlink allowing access to the relevant portals gateway. If the user is already logged into the portal it will load the specific token results. The plan is to remove the gateway url from the Rezlynx Home Page.

Taking further Payments

Taking further payments is now restricted to parent transactions only. Child Payments, taken from an original Credential on File (CoF) transaction will have the ‘Take Payment’ feature suppressed. This should help with approval rates.

Group Bookings

Account Checks performed at Group Level now display in the picked up bookings so they can be used for taking deposit payments.

Transaction Security

Users will be given a visual clue as the security of a transaction. This is based on the Billing Premise, Postcode and CVV. If the data supplied does not match with the information held by the Card Issuer, this information will be flagged to the user within the grid.

Within the legacy implementation it was possible to view the transaction details in a pop-up within Rezlynx and then print these. Research showed that this feature was rarely used and therefore has not been implemented as part of these changes.

Guarantee

The legacy implementation had support for; ‘Account Check’, ‘Guarantee Only’ & ‘Take Payment’. Research showed that ‘Guarantee Only’ was only used for £1 Auths on sites where the Acquirer does not support ‘Account Check’. Usage of ‘Guarantee Only’ for values greater than £1 was almost non-existent. For sites that don’t have access to the official ‘Account Check’ feature, this will be handled in the background and a £1 Suspended Auth will be informed.

Copy to Clipboard

The ability to ‘Copy’ to clipboard as not been included in the new implementation.

Gateway URL on Homepage

This is more of a change than a loss. The url to the gateway will now be accessible from the tokens, rather than the homepage.

Copy Reservation

Tokens will no longer copy as part of the reservation copy process. (They may appear to temporarily due to the way data is sync’d back into Rezlynx during the phased cross over period).