New Report Available: Payment Gateway Transactions report

A new report was added to the report type 3 - Customer Financial Reports called Payment Gateway Transactions Report

This report is an invaluable tool for customers using a payment gateway integrated with the Dolphin platform.  It provides a list of payment gateway transactions (receipts and refunds) processed via BMM/RM. (If you wish to know more about the payment gateways that are integrated in the Dolphin platform, click on this link.)

This report serves as a useful resource for verifying the success or failure of transactions before users resubmit payments.

Below is an example of the Payment Gateway Transactions Report:

As per standard functionality, users can double click on the folder number to open the folder that includes the transaction displayed in the report. This allows users to check the folder if required.

The Branch column shows the folder branch where the transaction was issued.

The Folder No column shows the folder number where the transaction was issued.

The Payment Session Date shows the date that the payment was processed with the payment gateway.

The Staff column shows the three-letter code of the staff that processed the transaction in the BMM.

The Transaction No column shows the BMM transaction number. This is the BMM receipt or refund number.   If there is no transaction number, it means the transaction was not recorded in BMM.

The Type column shows whether the transaction in the BMM is a Receipt or a Refund. Records described with a type of None means the transaction was not recorded in BMM.  

The Description column shows the type of transaction processed by the payment gateway. Each payment gateway might display different labels in this columns. Some of the options that display in this column are:

• Pre Auth: only applicable to transactions triggered from the reservation module. This is when a small amount is authorised before the full transaction amount is processed.
• Full Auth: this could take place after a Pre-Auth or as a standard sale transaction.
• Refund: this indicates that a refund was processed.
• Token Purchase: this indicates a transaction that used a tokenised card.
• Unknown: this does not happen very often. This description is caused when the payment gateway does not provide any information on the transaction. 

The Authorised column indicates whether a transaction was successful or not.

• A Yes in the Authorised column indicates that the transaction was successfully processed by the payment gateway
• A No in the Authorised column indicates that the transaction was not successfully processed by the payment gateway 

The Amount column shows the transaction amount. 

Scenarios that require investigation:

A transaction can be considered successful when the report record contains a transaction number in the Transaction No column and Authorised = Yes.  

All other scenarios require investigation.

For example: 

If  no transaction number exists, but Authorised = Yes, the transaction has been authorised by the payment gateway, but not recorded in BMM.

If a transaction number exists, but Authorised = No, BMM has recorded a transaction but nothing was processed by the payment gateway.

In both scenarios, users should log into the Payment Gateway portal and review the transactions.

The Subtotals allow users to organise the content of the report into sections based on user-defined criteria. 

Finally, the Payment Gateway Transactions Report can be scheduled to be emailed regularly (e.g.: daily) to one or more designated email addresses. This will allow users to promptly address any issues. For more information on how to schedule a report, check this article.