Model Bank

PAYMENTS – Pre-Sales Demo User Guide

Model Bank
PAYMENTS – Pre-Sales Demo User Guide

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means,
for any purpose, without the express written permission of TEMENOS HEADQUARTERS SA.

© 2018 Temenos Headquarters SA - all rights reserved.

Presales User Guide

Document History

Version Date Author Description

1.0 02-April-2019 Vignesh C Demo guide initial draft

2.0 24-April-2019 Vignesh C Changed NON-ESB Prerequisites

3.0 27-April-2019 Vignesh C Updated known issue

Presales User Guide

Table of Contents

1. Introduction ............................................................................................................................................ 4
2. General Guidelines ................................................................................................................................ 4
3. Non-ESB Setup ..................................................................................................................................... 4
3.1. Changes in Module.xml ................................................................................................................... 4
3.2. Set path in PP.IN.CHANNELS ........................................................................................................ 5
3.3. Set path in PP.CLEARING .............................................................................................................. 5
3.4. Set path in PP.SOURCE.SETTING ................................................................................................ 6
3.5. Set clearing frequency in PP.CLEARING.FREQUENCY ............................................................... 6
4. TSA.SERVICE to be started .................................................................................................................. 7
5. Folder used for the NON-ESB/ESB Payments...................................................................................... 7
6. Pre-Requisites Specific to Products ...................................................................................................... 8
6.1. SWIFT Payments ............................................................................................................................ 8
6.2. SEPA Payments .............................................................................................................................. 8
6.3. INSTANT Payments ...................................................................................................................... 10
6.4. Cheque .......................................................................................................................................... 10
7. ESB Solution ....................................................................................................................................... 10
8. Demo Scenarios in Model Bank .......................................................................................................... 11
9. Known Issue in the R19 ModelBank ................................................................................................... 12
9.1 Non-ESB: Pain.002 not generated for SEPA ................................................................................. 12
9.2 IIB Scenario (ESB): Outward SCT messages are not generated due to IIB Inbound Adapter
connectivity issue ................................................................................................................................. 13
10. Standalone - TPH ................................................................................................................................. 13
10.1 INTRODUCTION .......................................................................................................................... 13
10.2 Functionality ................................................................................................................................. 13
10.3 Products in Standalone ................................................................................................................ 13
10.4 T24 Users with Standalone Menu: ............................................................................................... 14
10.5 Pre-requisites to process the Standalone SWIFT Payments ....................................................... 14
10.6 Services required ......................................................................................................................... 15
10.7 Processing of Standalone SWIFT Message MT103 .................................................................... 15
10.8 List of Scenarios in STANDALONE ............................................................................................. 18
11. User Guide ............................................................................................................................................ 18
Presales User Guide

1. Introduction
“Model Bank Reference System” is released with demo data to enable the Pre-Sales to
demonstrate T24 Model bank functionality.
It is pre-configured with Role Based Home Pages, Dashboards, Business Processes,
Products, Enquiries, Reports and a host of other features.
This document is intended to aid Pre-Sales to understand the “demo data” available in
PAYMENTS Model Bank and choose the appropriate data set for demos. Also, general
guidelines to be kept in mind for login and navigation are also detailed.

2. General Guidelines
While demonstrating the PAYMENTS functionalities, please login with the User
Name/password provided for each Role.

SIGN ON NAME PASSWORD PROFILE

PAYUSER1 123456 Payment User

PAYUSER2 123456 Payment User

PAYUSER3 123456 Payment User

PAYUSER4 123456 Payment User

PAYUSER5 123456 Payment Admin

PAYUSER6 123456 Payment Admin

PAYUSER7 123456 IIB Connection

INPUTT 123456 Super User

AUTHOR 123456 Super User

Please avoid using the Command line while demonstrating enquiries, versions etc.
Instead use the Menu.

3. Non-ESB Setup
Model Bank is now defaulted with the Non-ESB Solution i.e. T24 is able to process
the files without the support of third party system (ESB)
Below are the few Setup to be followed for the Non-ESB in TPH.

3.1. Changes in Module.xml

 Add the line <module name="com.Slot01.temenos.payments"/> in the
module.xml which is available in the paths below
.\Temenos\Rxx\Infra\AppServer\JBoss\Default\modules\com\slot01\temenos\t24\main
Presales User Guide

.\Temenos\Rxx\Infra\AppServer\JBoss\Default\modules\com\slot01\temenos\tafj\main

Start the jboss and the application server of the model bank environment which will be
available in the below path.
Start \ All Programs \ Model Bank RXX \ Application Server Start

3.2. Set path in PP.IN.CHANNELS

Admin Menu>Payments Hub>Static Data>In Channel
Hard code the exact folder name as below for BATCH & INSTANT records in the
PP.IN.CHANNELS to pick the Incoming file placed in the folder defined.

3.3. Set path in PP.CLEARING

Admin Menu>Payments Hub>Local Clearing>Clearing
Hard code the Non-ESB folder path in the appropriate clearing record. This is used to
generate the Outgoing files. The path mentioned for the STEP2 Clearing is attached
below.
Presales User Guide

3.4. Set path in PP.SOURCE.SETTING

Admin Menu>Payments Hub>Static Data>Source Setting
The Output folder will also be defined here for Non-ESB payments. Illustration below
shows the Source Setting record of STEP2.

3.5. Set clearing frequency in PP.CLEARING.FREQUENCY

Admin Menu>PaymentsHub>LocalClearing>ClearingFrequency
PP.CLEARING.FREQUENCY cut-off time should be less that current system time +
offset defined in company properties. PAYMENTS Clearing Settlement Service picks
up the record which have passed the clearing cut-off and send them for clearing.
Ensure to change the cut-off time to a lower time such that service picks up the record.
Presales User Guide

4. TSA.SERVICE to be started
TSA SERVICE USED FOR

BNK/CLEARING.SETTLEMENT.SERVICE Clearing/CHEQUE
BNK/INWARD.MAPPING Clearing /CHEQUE
BNK/PAYMENT.STPFLOW.MEDIUM Clearing /CHEQUE
BNK/PAYMENT.STPFLOW.HEAVY SWIFT
BNK/PAYMENT.STPFLOW.LIGHT Clearing
BNK/CUST.STATUS.RPT.GEN.MSG Clearing
BNK/parentFeesDetermination Batch Processing
BNK/SWIFT.IN SWIFT
BNK/SWIFT.OUT.LISTENER SWIFT
BNK/PP.INTERFACE.UPDATE SWIFT
BNK/INSTANT.INWARD.MAPPING Instant Payments
PP.AUTO.INVSTMSG.GEN.SERVICE Instant Payments Investigation
PP.AUTO.INVSTMSG.GEN.SERVICE.NRINST Near Real Time Instant Payments
Investigation
PP.VIRTUAL.QUEUE View payments in Virtual Queue Monitor
PP.LC.START.BACS.CD.SCHED BACS Cheque Debit
PP.LC.START.BACS.SCHED BACS Processing
PP.LC.START.HKCLG.RELEASE Honk Kong Clearing Processing
PP.LC.START.HKCLG.SCHED Honk Kong Clearing Processing
STANDALONE.REQUEST.TIMEOUT Trigger Timeout for Standalone requests

Use the http://localhost:9089/TAFJEE/Execute to execute the services.

USER NAME: t24user

PASSWORD: t24User123!

5. Folder used for the NON-ESB/ESB Payments

Purpose
Instant Incoming PACS message
SEPA Pain.001 message
Instant Pain.001 message
Cheque Clearing Input
SEPA Pain002
Instant Pain.002 message
Instant Outgoing PACS message
SEPA Incoming PACS & camt msg
SEPA Outgoing PACS & camt msg
SEPA Pain008
NON ESB FOLDER ESB FOLDER
/PP/NONESB/B2BInstInput /PP/EBAInstInput
/PP/NONESB/BulkCTIInput /PP/BulkCTIInput
/PP/NONESB/C2BInstInput /PP/C2BInstInput
/PP/NONESB/CHQCLGInput /PP/CHQCLGInput
/PP/NONESB/CustStsRptOutput /PP/CustStsRptOutput
/PP/NONESB/CustStsRptInstOutput /PP/InstCSROutput
/PP/NONESB/EBAINSTOutput /PP/InstOutput
/PP/NONESB/STEP2Input /PP/STEP2Input
/PP/NONESB/STEP2Output /PP/CTOutput
/PP/NONESB/BulkDDInput /PP/BulkDDInput
Presales User Guide

6. Pre-Requisites Specific to Products

6.1. SWIFT Payments
 The list of PAYMENTS messages are available in the below path
.\Temenos\RXX\Env\Slot01\Data\T24\UD\MSG.IN

 Change the processing date in the message files. The Todays date in DATES table
and the message date should be the same.

Note: If user want to use the same message multiple times, change the value in Tag
20: Ref and Transfer amount to avoid duplication error.
 Refer the section 4. TSA.SERVICE to be started above

 Manually use the TELNET source and paste the message tRun tSS TELNET in
the TAFJ shell

 The services BNK/SWIFT.OUT.LISTENER and BNK/PP.INTERFACE.UPDATE

will simulate the ACK for SWIFT and change the status of the payment from 687 to 999.

6.2. SEPA Payments

 Refer the Section 3. Non-ESB Setup for configuration to make the payment work on
the non-ESB mode.

 Refer the section 4. TSA.SERVICES to be started above.

 The list of SEPA Inward messages will be available in the path

.\Temenos\RXX\Env\Slot01\Data\T24\UD\MSG.IN

 Amend the PP.SOURCE.SETTING application with the record ID DDI as

highlighted in the screenshot below.
Presales User Guide

 Amend the PP.MEDIUMWEIGHTPRODUCTCOND application with the

record ID O.DD.S.SHA.EUR-20180417 as highlighted in the screenshot below.

 Change the processing date in the SEPA xml files. The today’s date in DATES
table and the message date should be the same.

Note: If user want to use the same message multiple times, change value in Tag <Msg Id>
and Transfer amount to avoid duplication error.
Presales User Guide

6.3. INSTANT Payments

 Refer the Section 3. Non-ESB Setup for configuration to make the payment work on
the non-ESB mode.

 Refer the section 4. TSA.SERVICES to be started above.

 The list of Instant Inward messages will be available in the path
.\Temenos\RXX\Env\Slot01\Data\T24\UD\MSG.IN

 Change the processing date in the Instant xml files. The today’s date in DATES
table and the message date should be the same.

6.4. Cheque
 Refer the Section 3. Non-ESB Setup for configuration to make the payment work on
the non-ESB mode.

 Refer the section 4. TSA.SERVICES to be started above

7. ESB Solution
 Download IIB software and follow the installation guide Payments_Installation
Guide with JBoss- IIB in the given path below to integrate IIB in Model Bank .\
Temenos\RXX\Env\Slot01\Docs\Setup

 The records to be amended manually as mentioned in the table below

 Pre-requisites remain the same as NON-ESB solution. Refer the section 3. Non-
ESB Setup

 For Inward Cheque, We need to place the xml in the below folder so that
the IIB will pick and do processing automatically Input Folder
.\Temenos\RXX\Env\Slot01\Data\T24\UD\PP\CHQCLGInput
 Presales User Guide

8. Demo Scenarios in Model Bank

S.NO Scenarios Type S.NO Scenarios Type S.NO Scenarios Type
1 Receive pain.001, send pacs.008 SEPA 17 Receive SEPA DD SEPA 33 STP Redirect of an SWIFT
Instant collection file (pain.008) DD MT103 payment message
and generate SEPA DD file to NOSTRO account
to clearing (pacs.003)
2 Receive via Channel, send SEPA 18 Receive Inward DD SEPA 34 Initiate Payment Order PO
pacs.008 Instant collection file (pacs.003) DD INATIONAL and waiting
and process all payments for Fraud check and
successfully. Screening response
3 Receive pacs.008 and book the SEPA 19 Receive Inward DD SEPA 35 Initiate Payment Order PO
payment Instant collection file (pacs.003) DD Instpay and awaiting
and partially reject, send response
pacs.002
4 Initiate Instant payment (pacs.008) SEPA 20 Initiate payment reversal SEPA 36 Initiate Payment Order PO
from PO. Instant (pacs.007) for an already DD SEPA
settled SEPA DD payment
5 Send Investigation message SEPA 21 Receive a payment SEPA 37 Release parked Generic
(pacs.028) for an instant outward Instant cancellation request DD Payments from View
pacs.008. (camt.056) for an inward Parked Payments Enquiry
DD (pacs.003) received
and yet to be settled.
6 Initiate & Send Payment recall SEPA 22 SEPA 38 Release payment from Generic
(camt.056) for a processed SEPA Instant Send payment cancellation DD Pending Pre
instant payment (pacs.008) request (camt.056) for an Authorisation
Outward SEPA DD Request(Manual funds
payment sent via pacs.003 authorisation request)
and not yet settled.
7 Receive payment return (pacs.004) SEPA 23 Return SEPA DD after SEPA 39 Release Payment from SWIFT
in response to an outward Instant settlement and generate DD SWIFT Out Exception
cancellation request. pacs.004. Queue
8 SEPA 24 SEPA 40 Release Payment from Generic
Receive Payment recall (camt.056) Instant Receive and process a
and send negative answer DD Manual filter Payment
payment reversal Queue
(camt.029) (pacs.007) for an inward
DD settled previously
9 SEPA 25 Incoming STP with FX SWIFT 41 Send Cancellation SWIFT
Receive payment initiation request
(pain.001) and send payment to (MT103 SWIFT) Request for SWIFT
clearing (pacs.008).
10 Receive payment initiation request SEPA 26 Incoming STP with no FX SWIFT 42 Send a Query(SWIFT SWIFT
(pain.001) and send pacs.008 , (MT103 SWIFT) Investigation)
positive pain.002
11 SEPA 27 Incoming Repair with Credit SWIFT 43 Answer a Query(SWIFT SWIFT
Receive inward Credit Transfer
payment file (pacs.008) and book account Incorrect (MT103 Investigation)
SWIFT incoming in USD
with creditor account
invalid)
12 Receive inward Credit Transfer SEPA 28 Incoming MT202 received SWIFT 44 Reversal of SWIFT SWIFT
payment file (pacs.008) and unable via TARGET2 (EUR) Payments
to process STP. Partial rejection
happens Auto generate pacs.004
13 Receive payment recall (camt.056) SEPA 29 Book payment processed SWIFT 45 Send Pacs.028 Manualy SEPA
for a processed SEPA payment STP (from an MT101) for Ougoing instant Instant
and park the recall message for payment awaits for
manual action. Accept recall and
pacs.002
process return manually.
14 Receive payment recall (camt.056) SEPA 30 Order Entry - Incoming STP SWIFT 46 Resubmit payment from SWIFT
for a processed SEPA payment with FX NA Repair queue
and Park the recall message for
manual action. Send ROI manually
 Presales User Guide

15 SEPA 31 Order Entry - Incoming SWIFT 47 Release pending SWIFT

Send Payment recall for SEPA
payment and a return payment MT202 received via payment for cover
(positive answer to recall) and TARGET2 (EUR)
book.
16 SEPA 32 Order Entry initiated SWIFT
Send payment recall (camt.056) for
SEPA payment and receive/ record outgoing SWIFT payment
negative answer (camt.029). through TARGET2

9. Known Issue in the R19 ModelBank

9.1 Non-ESB: Pain.002 not generated for SEPA
Defect: Pain.002 not getting generated for sucess case -Test Scenario - Receive pain.001,
send pacs.008 and send pain.002. (3097615)

Workaround:
 Copy the Non-ESB Jar PP_NONESBOutward-0.0.4-SNAPSHOT from
.\Temenos\RXX\Infra\AppServer\JBoss\Default\modules\com\slot01\temenos\payments
\main\lib to .\Temenos\RXX\Env\Slot01\Products\TAFJ\Default\ext

 Restart the JBoss. Start the TSM in the Debug mode from the TAFJ shell and start the agent
assigned for BNK/CUST.STATUS.RPT.GEN.MSG in the TAFJ shell (Screenshots attached)
Presales User Guide

9.2 IIB Scenario (ESB): Outward SCT messages are not

generated due to IIB Inbound Adapter connectivity issue

Defect: TPH - T24Inbound Adapter connectivity issue (3104209)

10. Standalone - TPH

10.1 INTRODUCTION
TPH is enhanced to act as a Standalone Payment Hub with ability to process payments
by connecting to an external DDA and General Ledger, and also cater to requirements
where bank’s some customer accounts are held in T24 and some in external DDA.

10.2 Functionality
With Standalone processing feature in TPH, Payment system can interact with external
DDA and General Ledger for the following functionality:

• Account Validation
• Funds Reservation
• Booking
• Cancel Reservation
• Reverse Posting
• Direct Debit Mandate Validation and Amendments
To check the functionality of this Standalone, company NL0010001 has been created in
the Model Bank.

10.3 Products in Standalone

Presales User Guide

10.4 T24 Users with Standalone Menu:

SIGN ON NAME USER NAME PASSWORD

CRCUSER System Admin User 123456
CSUSER Payment Customer service 123456
OPSUSER Payment Operations Service 123456
PRDMGRUSER Payment Product MGR 123456
SYSADMUSER System Admin User 123456
SYSUSER Payment System Support 123456

Standalone SWIFT Payments Demo

10.5 Pre-requisites to process the Standalone SWIFT

Payments
 Copy the PUSHMSG Jar file from the below path
Temenos\RXX\Env\Slot01\Products\TPS\PushMsg and paste it in the lib folder
Temenos\RXX\Env\Slot01\Products\T24\T24lib.

 After PUSHMSG copied, Open the module.xml file from the path
Temenos\RXX\Env\Slot01\Products\T24\T24lib and include the path <resource-root
path="./PUSHMSG.jar" /> as per screenshot below.

 Add the below command in tafj.properties which is available under folder

.\Temenos\R18\Env\Slot01\Products\TAFJ\Default\conf(Applicable only for Standalone)
temn.tafj.appserver.execute.servlet.allowed.commands=PROCESS.STANDALON
E.RESPONSE,START.TSM

 Start the jboss and the application server of the model bank environment which
will be available in the below path. Start \ All Programs \ Model Bank Rxx \
Application Server Start
 Make sure the company Model Bank - Standalone selected from Tools\My
company

 Change the processing date and demo BIC in the message files: The
Todays date in DATES table and the message date should be the same. Change the
date in YYMMDD format. The demo BIC for Standalone Company is DEMONLPX and
the same need to update in the messages before processing in Standalone Company.

 The list of PAYMENTS messages are available in the below path under
respective folders \Temenos\RXX\Env\Slot01\Products\TPS\Messages\
Presales User Guide

Note: If user want to use the same message multiple times, change the value in Tag 20:
Ref and Transfer amount to avoid duplication error.

10.6 Services required

The following TSA.SERVICE items used to process Standalone SWIFT messages in
PAYMENTS
The TSM should be “START” and the below services should be made as “AUTO”

Sl.No. Service Name

1 TSM

2 BNK/SWIFT.IN

3 NL1/PAYMENT.STPFLOW.HEAVY

4 NL1/PAYMENT.STPFLOW.LIGHT

10.7 Processing of Standalone SWIFT Message MT103

a) TAFJ Shell - tRun tSS TELNET

b) Paste the converted MT 103 message.

c) The record in DE.I HEADER will be created in the “UNFORMATTED” disposition

once the message is pushed.
Presales User Guide

d) The BNK/SWIFT.IN service must be run, disposition in DE.I.HEADER changes

to “OFS Formatted”.

The transaction gets generated in POR.TRANSACTION and the same will be available
in the Pending and processed Enquiry (PP.PAY.PEN.PROCESS).
Usermenu > Payments > Payments Hub > Payment Inquiries > Pending and
Processed Payments > Pending and Processed Payments - Transaction wise

e) The NL1/PAYMENT.STPFLOW.HEAVY service must be run and the status

changes to 45.in the ENQ PAY.PEN.PROCESS. The transaction currently awaits
response for Account Validation in this stage.
Presales User Guide

f) To push the responses for payment awaiting responses from external system

i Copy the FT number from the ENQ PAY.PEN.PROCESS screen.

ii Open the AccountingInquiryCreditresponse message from the below path.

Temenos\R18\Env\Slot01\Products\TPS\Messages\Standalone

iii Replace the TRANS.REF in the end of in the response message and place the
file in the path below.
Temenos\R18\Env\Slot01\Data\T24\UD\PP\Standalone\ResponseFolder

iv Execute the Utility PROCESS.STANDALONE.RESPONSE through TAFJEE

v The status will changes to 46 (Post Accounting Entries request sent) after
executing the above utility.

vi The status will move to 662 (Post Accounting Entries request sent) if
NL1/PAYMENT.STPFLOW.HEAVY running in Background else the service
should be invoked manually.
Presales User Guide

vii Open the Postingresponse message from the below path

Temenos\R18\Env\Slot01\Products\TPS\Messages\ResponseMessage.

viii Copy the FT reference from ENQ PAY.PEN.PROCESS replace this reference in
the the end of template with the copied transaction reference in the response
message as step III. Place this file in the below path
Temenos\R18\Env\Slot01\Data\T24\UD\PP\Standalone\ResponseFolder

ix Execute the Utility PROCESS.STANDALONE.RESPONSE through TAFJEE.

x The status of the Transaction will now change to 999 i.e. Payment completed.

10.8 List of Scenarios in STANDALONE

Sno Scenarios Message

1 MT103 AC validation SWIFT-MT103-TPS16173000001-009

2 MT103 Booking SWIFT-MT103-TPS16173000001-009

3 MT101 Fund Reservation SWIFT-MT101-TPS16173000001-003

4 MT103 Cancel Reservation SWIFT-MT101-TPS16173000001-003

5 Outgoing SW Reverse Posting SWIFT-MT101-TPS16173000001-003

6 pacs003 Mandate Validation SEPA-PACS003-TPS18194880004-001

7 Payment Order Scenario NA

11. User Guide

Please refer the User Guide for more details on the Payments system and Scenarios.