Notify methods

The Card Transaction Processing interface provides a single interface to access different Payment Gateways which enables users to change gateways easier than if they had reimplemented the native interface of a new payment gateway. The Card Transaction Processing Module aims to hide many specifics of each gateway

If a client (e.g. an eShop) of the Card Transaction Processing module needs to be PCI compliant, they will have to either be PCI certified or use a so called, ”payment page” which is supplied by a Payment Gateway.

A “payment page” is a web application hosted by the “Payment Gateway” which the eShop has to link to. The “payment page” is the place where shoppers enter their credit card details. The result is that neither the shop nor the Card Transaction Processing Module has been given any Credit Card details. The only details that the eShop has contact to is masked credit card data and ids needed to capture the payment.

The information which is sent back to the eShop from the “payment page” is needed by the DSB back office systems (AVS/3, VHS/3 …) to be able to process the payment further (step 1). The following methods provide an interface to send the data received from the “Payment Page” to DSB. A DSB transaction id is then generated and sent back in the response (step 2). This transaction ID should be then included within the relevant order (subscription or mail order) request so that the systems can associate the payment with the Order (step 3).

You can find further information about how to connect to a ”Payment Page” from the documentation of the relevant Payment Gateway