Custom Payment Gateway Event Handlers

You can add custom event handlers to add functionality to the Payment Service, such as to change the message content, log an action, or trigger other functionality. Custom event handlers can be triggered when sending or receiving messages to or from a third-party payment gateway at specific points in a transaction life cycle.

Transaction Life Cycle Events

The transaction life cycle of a payment operation starts when it is received by the Payment Service from MATRIXX Engine. Then it is transformed to a vendor specific message, is sent to the third party server, and a response is received and transformed to MDC format. The life cycle ends when the message is returned to MATRIXX Engine. Event Handler Trigger Points describes the points (or events) in this life cycle where you can implement a custom event handler.

Table 1. Event Handler Trigger Points
Event Description
Before sending to the payment gateway This is the point at which a vendor-specific message has been created and is just about to be sent to the third party payment gateway servers. In this event, is it possible to make changes to the message before it is sent or trigger other functions.
Response from the payment gateway This is the point at which a vendor-specific response has been received and transformed back into a Payment Service response. At this point, you have access to both the received response and the response which is returned to MATRIXX Engine. This event can be used to capture additional information from the response which is not used by default, or to make changes to the default mapping logic.