GNM_SLM_WorldPay_Integration_TS

• 1. .Introduction

     1. Purpose

The document GNM_RCS_System_Interfaces_FS.docx is the functional specification that describes what business functions RCS supports in relation to its interfaces with other GNM systems as well as any external integration.

This document is one of a set of technical specifications that provide details of how those functions are implemented in RCS.

• 1. Scope

This document focusses on the WorldPay interface whereby credit/debit card payments can be taken from syndication customers. Separate documents deal with all other inter-system interfaces that pass data between RCS/SLM and other systems.

This document is intended as a high-level technical document outlining how the relevant business functions are implemented in terms of software modules.

Importantly, this document does not aim to provide the level of detail that would be required in a programming specification in areas such as program structure, detailed business rules, data integrity, validation, locking considerations, data security, and calls to/from other software modules, performance considerations, and so forth.

For details of program logic and coding, the reader should refer to the program files themselves.

• 1. .WorldPay interface

     1. WorldPay processing

        1. Business requirement

GNM's credit terms are such that a client is supposed to pay for their first licence in advance in order to be allowed to pay in arrears in future. Advance payments can be taken as debit/credit card payments, cheques, or bank transfers.

If payment is taken in advance then this must be recorded on the request details, and then be recorded on the invoice instruction that is sent to Oracle AR to ensure it is processed in Oracle AR as a prepaid invoice i.e. no more money is requested from ther customer.

WorldPay is the 3rd party software that has been integrated into SLM to take the debit/credit card payments. It is important that it is tightly integrated into the SLM application (in accordance with WorldPay’s guidelines) so that the key details of any payment processing are fully recorded in SLM for each transaction, along with a log of all activity.

• 1. Solution design

The licence processing screens in SLM have a “Prepayment” button which enables a prepayment to be recorded. Once this button is pressed the window below opens:

For cheque payments the details of the cheque are entered into the relevant fields.

For Bank transfers the user presses the “Email AR” button which causes an email to be sent to Accounts Receivable asking that they look out for the payment, and provide the bank reference when it arrives. The user then enters this value in the above Receipt number / Bank advice field.

To take a debit/credit card payment the user presses the “WorldPay” button shown above and this initiates the payment process.

• 1. Confirm details to be sent to WorldPay

Firstly a new browser tab or window opens showing the details of the transaction to WorldPay.

This page is launched by invoking a database packaged procedure worldpay.take_payment that generates an HTML page using the standard Oracle package HTP.

Invoking the database packaged procedure requires mod_plsql to be configured on the webserver.

.

• 1. Take credit card payment

Pressing the “Send details to WorldPay” button initiates the standard WorldPay processing:

The WorldPay response is processed by WorldPay invoking a database package procedure that displays the result itself, and also records the details of the WorldPay transaction. For successful payments WorldPay invokes worldpay_callback.resultY and for failed payments it invokes worldpay_callback.resultC Each of these procedures utilises the Oracle standard package HTP to generate an HTML page that shows the results to the user in the browser window. The procedures also update the database with the result and the activity is logged.

Once the user has closed this window and returns to SLM the request screen waits for a response from WorldPay to be posted to the RCS database. The user has the option of continuing to wait if the result is not recorded in a few seconds, or they can just continue with their work.

.

• 1. WorldPay configuration

There are several parameters needed to configure WorldPay in SLM, and as such these parameters are grouped together in their own screen. The screen is accessed from the menu option: Syndication → General configuration → WorldPay parameters

This opens the Oracle Form rcs_cpar_010_pc.fmb

.

• 1. WorldPay call-back messages

All of the call-back messages from WorldPay are recorded in a table in SLM, and can be reviewed in a screen. The screen is accessed from the menu option: Syndication → AR interface → WorldPay call-back messages

This opens the Oracle Form rcs_wcme_010_pc.fmb

.

• 1. WorldPay activity/error log

A log of all activity and errors associated with WorldPay is kept in SLM. This log can be reviewed in an SLM screen. The screen is accessed from the menu option: Syndication → AR interface → WorldPay log

This opens the Oracle Form rcs_wlog_010_pc.fmb

End of Document