TEMENOS T24

ARC Internet Banking

Administration

User Guide

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

Copyright 2005 TEMENOS Holdings NV. All rights reserved.

ARC Internet Banking Administration Guide

Table of Contents
Overview.................................................................................................................................................. 4
Concept of AA module ......................................................................................................................... 4
Setup ....................................................................................................................................................... 4
T24 Arrangement Architecture module (AA)........................................................................................ 4
HELPTEXT.MENU ............................................................................................................................. 12
EB.COMPOSITE.SCREEN................................................................................................................ 13
PROPERTY CLASSES...................................................................................................................... 15
Create AA.PROPERTY RECORDS ............................................................................................... 16
ARRANGEMENT.PREFERENCES (Property Class) .................................................................. 18
Overview of each Class ..................................................................................................................... 20
Create CONDITIONS for each PROPERTIES DEFINED.............................................................. 21
Item 1 Create condition for ARRANGEMENT.PREFERENCES (Property Class) ........................ 21
Item 2 create a condition for CUSTOMER (Property Class) .......................................................... 22
Item 3 create a condition for USER.RIGHTS (Property Class) ..................................................... 24
Item 4 create a condition for PRODUCT.ACCESS (Property Class) ............................................. 24
Item 5 create a condition for PROTECTION.LIMIT (Property Class) ............................................ 25
Item 6 create a condition for UI.APPEARANCE (Property Class) ................................................. 25
Item 7 create a condition for UI.BEHAVIOUR (Property Class)..................................................... 26
Setup GROUP Using COS AA.PRODUCT.DESIGNER-PRODUCTS .............................................. 27
Setup the PRODUCTS in the DB.TEST defined. .............................................................................. 30
Proof and publishing .......................................................................................................................... 32
Generate Arrangement ID.................................................................................................................. 35
Create user with EB.EXTERNAL.USER ............................................................................................ 39
Login To ARC-IB URL........................................................................................................................ 41
Additional Set up ................................................................................................................................ 42
Logging in methods for users ......................................................................................................... 42
Transaction signing using challenge response .............................................................................. 51
Set up secure messages ................................................................................................................ 55
Creation of Account Mandates ....................................................................................................... 59
Intermediary Services/Proxy Permissions...................................................................................... 75
Enquiries................................................................................................................................................ 95
!EXT.Variables ................................................................................................................................... 95
EB.External.User ............................................................................................................................ 95
!VARIABLEs in SMS ...................................................................................................................... 95
!EXT.SMS.EXTERNAL.CUSTOMER ............................................................................................. 96

TEMENOS T24 User Guide

Page 2 of 129
ARC Internet Banking Administration Guide

Deal/Transaction processing ............................................................................................................... 100

Payments ......................................................................................................................................... 100
Secure messaging ........................................................................................................................... 105
Account Mandates ........................................................................................................................... 111
Creation of Account Mandates ..................................................................................................... 113
Implementation of ARC-IB Browser on Web sphere ....................................................................... 129

TEMENOS T24 User Guide

Page 3 of 129
ARC Internet Banking Administration Guide

Overview
The ARC Internet Banking (ARC-IB) product is aimed at providing the bank’s customers and approved
intermediaries with access to their account through the internet using secure authentication methods
and security..

Concept of AA module
The Concept of the AA modules setup building block is provided in a document called T24
Arrangement Architecture Product Summary. Please refer to guide for more information.
• ARC-IB.war file can be obtained from [email protected]
• ARC-IB war file needs to be deployed as per standard T24 BrowserWeb.war file into the
Webserver.
• To deploy, copy the ARC-IB.war file into Webserver directory.
• If the Webserver does not auto extract the “war” file into a directory called ARC-IB, then you need
to stop and start the Webserver e.g. shutdown.sh and startup.sh in the bin directory.
• The standard settings like browser name, TCP port number and host IP Address needs to match
the T24 Area configured in TCServer Listener and TCP port number. Please refer to the following
document for details setup option.
• T24 Arrangement Architecture module AA and AI is used to setup internet user access

Useful documents.
• Browser Installation & Configuration user guide
• Browser Security guide

You can have one ARC-IB URL for internet users and one BrowserWeb URL for intranet internal users
connecting to the same T24 system as shown below

Setup
ALL THE FOLLOWING SET UP IS DONE IN INTERNAL BROWSER.

T24 Arrangement Architecture module (AA)

Check in SPF record SYSTEM to see if you have AA and AI, if not the products will need to be
installed.

Also check the COMPANY record has the application AA and AI defined.

TEMENOS T24 User Guide

Page 4 of 129
ARC Internet Banking Administration Guide

Showing the defined applications

The COMPANY record should also have AA.ARRANGEMENT.ACTIVITY added as PGM.AUTOM

ID field. This is to tell the T24 system to auto generate an id number for a new deal.

Showing PGM.AUTO.ID with AA.ARRANGEMENT.ACTIVITY set

You will need to create the following records.

1. EB.CHANNEL a record name INTERNET
2. USER.SMS.GROUP record AI.PERS
3. USER ARCIBUSER.1
4. OFS.SOURCE record ARC

TEMENOS T24 User Guide

Page 5 of 129
ARC Internet Banking Administration Guide

1. EB.CHANNEL record INTERNET

The EB.CHANNEL record for INTERNET

TEMENOS T24 User Guide

Page 6 of 129
ARC Internet Banking Administration Guide

2. USER.SMS.GROUP record AI.PERS (this can be called anything you want, here we call it
AI.PERS for demonstration purposes). The created record allows or restricts user action depending on
what functions are selected. This record will be used in our setup example.

The USER.SMS.GROUP record for AI.PERS

Note the functions set here are dependent on the client usage of your ARC-IB system.

TEMENOS T24 User Guide

Page 7 of 129
ARC Internet Banking Administration Guide

3. The USER record which you will create next, is used for the external users, so can be heavily
restricted.

The user profile for ARCIBUSER.1

Check that the created user ARCUSER is valid and log into T24. If log in fails then check the start and
end date or the attempts are valid.

TEMENOS T24 User Guide

Page 8 of 129
ARC Internet Banking Administration Guide

4. OFS.SOURCE record ARC

Next the creation of an OFS.SOURCE record is required. This is for the TCSERVER to read and pick
up data from.

The OFS.SOURCE record for ARC

The SOURCE type is SESSION because it’s a browser connection session

The LOGIN.ID is set to ANY, so any created External.User may log in
The GENERIC USER is the created ARCIBUSER1
The CHANNEL is INTERNET as this is the platform of use.

TEMENOS T24 User Guide

Page 9 of 129
ARC Internet Banking Administration Guide

The ARC-IB. parameter files need to be edited to match server details. They are located within the
ARC-IB directory.

BrowserParameters.xml - Edit the instance parameter as per below

The required change in Browser Parameters.xml is to the instance field

channels.xml - Edit the server, port and name details to match local information

The required change in channels.xml

BrowserConnection.xml - The browserConnection.xml should be changed as per below

The instance parameter

TEMENOS T24 User Guide

Page 10 of 129
ARC Internet Banking Administration Guide

An ARC adapter and listener must be created as below. The ARC adapter must be the same name
created in the OFS.SOURCE earlier (ARC is the easiest)

JED tcserver.xml and enter the following

OFS.SOURCE ID

The adapter should look like above

Then create a listener for the created adapter with an unused port number in TCServer.xml which can
be located further down the page.

The created listener should look like above.

TEMENOS T24 User Guide

Page 11 of 129
ARC Internet Banking Administration Guide

HELPTEXT.MENU
The next stage is to create what the external user will see when they log in. The first part of set up is
to create a record in HELPTEXT.MENU with the version or enquiry you wish to attach eg FT like
below with a relevant record name eg AI.PAYMENTS. Any application attached must have the “I F3” so
a new deal can be entered and the version must be a self authorising one so there is no need for a
secondary authoriser.

Creating a version record for HELPTEXT.MENU

Then create a new record called AI.MAIN in HELPTEXT.MENU and link to the above.

Attaching the created version record

Note the AI.PAYMENTS has been entered into the AI.MAIN record

TEMENOS T24 User Guide

Page 12 of 129
ARC Internet Banking Administration Guide

EB.COMPOSITE.SCREEN
Then you must create EB.COMPOSITE.SCREEN for AI.MAIN.HEADER which also forms part of
the external user log in screen

Displaying the AI.MAIN.HEADER composite screen details

Note all the URL listed in this screen will be found in the ARC-IB directory

TEMENOS T24 User Guide

Page 13 of 129
ARC Internet Banking Administration Guide

Creation of a composite screen for EB.EXTERNAL.USER

Before any classes and properties are set up, a further composite screen like below should be created
in EB.COMPOSITE.SCREEN, this uses the one created earlier.

The created record from

EB.COMPOSITE.SCREEN

The created record from

HELPTEXT.MENU

Displaying contents for composite screen called KAMMENU

TEMENOS T24 User Guide

Page 14 of 129
ARC Internet Banking Administration Guide

PROPERTY CLASSES
The setup we will be showing uses pre-defined screens created for AA. Our set up here is for an
internet banking system only.

Now we will set up the AA Property record and associated AA.PROPERTY.CLASS.

a. Click on AA Menu, Product Builder, Property Classes and Properties

Defined Product Conditions

Defined Property Classes for each Property Class

Define the 7 Properties Classes below

Item Property Class Property “name” Product Conditions “name”

1 ARRANGEMENT.PREFERENCES ARRPREF DB.TEST
2 CUSTOMER CUSTOMER DB.TEST
3 USER.RIGHTS DBCUSTRIGHT DB.TEST
4 PRODUCT.ACCESS PRODACCS DB.TEST
5 PROTECTION.LIMIT DAILY.LIMIT DB.TEST
6 UI.APPEARANCE UI.APPEARANCE DB.TEST
7 UI.BEHAVIOUR UI.BEHAVIOUR DB.TEST

The AA.PROPERTY “name” can be anything but there is a maximum character of 15.
The Product Conditions “name” can be anything as per the AA.PROPERTY.CLASS with maximum
character of 60.
b. After creating Properties and Conditions, next step is to create a Group and a Product using AA
Menu, Product Builder, Products application.

Defined Group Defined Product for the

Group

c. Generate an Arrangement ID.

d. Create a user using EB.EXTERNAL.USER.
e. Login using user created.

TEMENOS T24 User Guide

Page 15 of 129
ARC Internet Banking Administration Guide

Create AA.PROPERTY RECORDS

The AA setup uses dynamic application names such as AA.PRD.DES.XXXX where the XXXX is
created by the user.
To make input easier the menus and screens pre-configured for AA will be used as they cater for
these dynamic names automatically.
In order to setup, please login using a normal browser URL link not the ARC-IB URL link because
ARC-IB URL link has security lock down with limited function.
Select the AA MENU or type in MENU AA from the command line.

The menu structure for AA.

Now click on “Product Builder” and then the “Property Classes” and Properties” menu items.
You should get a new pop-up window as shown below.

TEMENOS T24 User Guide

Page 16 of 129
ARC Internet Banking Administration Guide

The group of Classes displayed above.

This is a graphical listing of classes where:

• The binocular icon is used to view a record

• The pen and paper icon are used to amend a record
• The folded paper icon is used to create a new deal
• The blue triangle icon displays created conditions for the particular class,

TEMENOS T24 User Guide

Page 17 of 129
ARC Internet Banking Administration Guide

ARRANGEMENT.PREFERENCES (Property Class)

Click on New page icon next to the ARRANGEMENT.PREFERENCES

Showing the creation of a new property

Then enter ARRPREFS for Property Definition and Enter

Creating AA.PROPERTY record ARRPREF

TEMENOS T24 User Guide

Page 18 of 129
ARC Internet Banking Administration Guide

To get the screen below

Creating AA.PROPERTY record ARRPREF

Once open input the GB Description and Full Description and check the Property Class is
ARRANGEMENT.PREFERENCES, you can then COMMIT
After commit you will see the screen shown below and the property definition name created

Showing the created property record

Repeat this process for all of the seven classes.
Item Property Class Property Class Product Conditions “name”
“name”
1 ARRANGEMENT.PREFERENCES ARRPREF DB.TEST
2 CUSTOMER CUSTOMER DB.TEST
3 USER.RIGHTS DBCUSTRIGHT DB.TEST
4 PRODUCT.ACCESS PRODACCS DB.TEST
5 PROTECTION.LIMIT DAILY.LIMIT DB.TEST
6 UI.APPEARANCE UI.APPEARANCE DB.TEST
7 UI.BEHAVIOUR- UI.BEHAVIOUR DB.TEST

TEMENOS T24 User Guide

Page 19 of 129
ARC Internet Banking Administration Guide

Overview of each Class

UI.BEHAVIOUR
The UI.BEHAVIOUR Property Class defines the manner in which external users can interact with the
internet bank application.
USER.RIGHTS
The USER.RIGHTS Property Class is used by products to set the conditions on which an external user
can do, view and when they are allowed to access the system.
PRODUCT.ACCESS
The PRODUCT.ACCESS Property Class defines the manner in which external users can interact with
the internet bank application.
ARRANGEMENT.PREFERENCES
The ARRANGEMENT.PREFERENCES Property Class defines the manner in which external users can
interact with the internet bank application.
UI.APPEARANCE
The UI.APPEARANCE Property Class defines the User appearance properties. It can be used to
configure tool style, language, skin, date format and amount format at the design level.
PROTECTION.LIMIT
The PROTECTION LIMIT Property Class is used by products which have daily limits on the cumulative
amount of transactions that can be done via an external channel (e.g. Internet, Mobile, ATM, etc.).
CUSTOMER
The CUSTOMER Property Class is used by all products to specify all of the involved parties of an
arrangement and their respective roles.

TEMENOS T24 User Guide

Page 20 of 129
ARC Internet Banking Administration Guide

Create CONDITIONS for each PROPERTIES DEFINED

Item 1 Create condition for ARRANGEMENT.PREFERENCES (Property Class)

Click on the AA Menu, Product Builder and the Product Condition option.

Click on New page icon next to the ARRANGEMENT.PREFERENCES Class ID row.

Creating a new condition for the class

Then enter DB.TEST for Conditions Definition

Creating AA.PRD.DES.ARRANGEMENT.PREFERENCES record DB.TEST

Press enter to get the window page shown below

TEMENOS T24 User Guide

Page 21 of 129
ARC Internet Banking Administration Guide

Creating AA.PRD.DES.ARRANGEMENT.PREFERENCES record DB.TEST

Validate to check any error before COMMIT.

Item 2 create a condition for CUSTOMER (Property Class)

Repeat the same steps as above for CUSTOMER. Sample screen shown below.

Creating AA.PRD.DES.CUSTOMER record DB.TEST

TEMENOS T24 User Guide

Page 22 of 129
ARC Internet Banking Administration Guide

Click on Negotiation Rules tab and select Default Negotiation as Yes.

Then commit .

Commit will give you a screen like below.

Committed screen view above

TEMENOS T24 User Guide

Page 23 of 129
ARC Internet Banking Administration Guide

Item 3 create a condition for USER.RIGHTS (Property Class)

Repeat the same steps as Item 1 above for USER.RIGHTS. Sample screen shown below.

Creating AA.PRD.DES.USER.RIGHTS record DB.TEST

SMS GROUP Æ AI.PERS ( created earlier in the USER.SMS.GROUP )
START TIME Æ 0001
END TIME Æ 2400

Next click on negotiation rules tab and select default negotiation as yes then commit .

Item 4 create a condition for PRODUCT.ACCESS (Property Class)

Repeat the same steps as Item 1 above for PRODUCT.ACCESS. Sample screen shown below.

Creating AA.PRD.DES.PRODUCT.ACCESS record DB.TEST

Next click on negotiation rules tab and select default negotiation as yes then commit .

TEMENOS T24 User Guide

Page 24 of 129
ARC Internet Banking Administration Guide

Item 5 create a condition for PROTECTION.LIMIT (Property Class)

Repeat the same steps as Item 1 above for PROTECTION.LIMIT. Sample screen shown below.

Creating AA.PRD.DES.PROTECTION.LIMIT record DB.TEST

Next click on negotiation rules tab and select default negotiation as yes then commit .

Item 6 create a condition for UI.APPEARANCE (Property Class)

Repeat the same steps as Item 1 above for UI.APPEARANCE. Sample screen shown below.

Creating AA.PRD.DES.UI.APPEARANCE record DB.TEST

Next click on negotiation rules tab and select default negotiation as yes then commit .

TEMENOS T24 User Guide

Page 25 of 129
ARC Internet Banking Administration Guide

Item 7 create a condition for UI.BEHAVIOUR (Property Class)

Repeat the same steps as Item 1 above for UI.BEHAVIOUR. Sample screen shown below.

Creating AA.PRD.DES.UI.BEHAVIOUR record DB.TEST

Next click on negotiation rules tab and select default negotiation as yes then commit .

The flow type is a generic field specifying the type of action flow to be performed.
FIRST.LOGIN is used on initial login for customers to accept the terms and conditions. EVERY.LOGIN
is used for normal day to day use. Once the terms and conditions are accepted by the customer then
the ACCEPT TC field in EB.EXTERNAL.USER is updated to YES.
Note- the terms and condition page must be set up separately, please see your account manager for
local requirements of initial login procedures.

The flow type is linked to the flow value and shows what to display at this point in the workflow. This
should be either an EB.COMPOSITE.SCREEN record Id or a URL to a static page.

TEMENOS T24 User Guide

Page 26 of 129
ARC Internet Banking Administration Guide

Setup GROUP Using COS AA.PRODUCT.DESIGNER-PRODUCTS

Click on AA Menu, Product Builder and then the Products option.

Going into the products menu

The below screen will appear.

Creating a new internet services product line

CLICK on new page icon for INTERNET SERVICES to create a new group

TEMENOS T24 User Guide

Page 27 of 129
ARC Internet Banking Administration Guide

Creating AA.PRODUCT.GROUP record INTERNET.CLASS.OF.SERVICE

Give a GB.DESCRIPTION and GB.FULL.DESCRIPTION.

TYPE = Internal

Property Class ARRANGEMENT PREFERENCES with the property defined earlier e.g. DB.TEST.
Do the same for all 7 properties defined by using the add multi-value field
Button.

TEMENOS T24 User Guide

Page 28 of 129
ARC Internet Banking Administration Guide

After inputting all 7 properties click on Mandatory check box for CUSTOMER and USER.RIGHTS
properties.

Above is the completed record

Click on validate a deal icon to check no error message. Then commit the deal.
You will get a read only view of the defined properties after commit.

TEMENOS T24 User Guide

Page 29 of 129
ARC Internet Banking Administration Guide

Setup the PRODUCTS in the DB.TEST defined.

Click on the blue triangle button to expand the Product Groups column and click on the new page icon
for New Product definition in PRODUCTS.
Input a name for the Product Designer e.g. DB.TEST

Creating a new product deal for internet.class.of.service

Give a GB DESCRIPTION and GB FULL DESCRIPTION and select the Property and condition
defined earlier.

TEMENOS T24 User Guide

Page 30 of 129
ARC Internet Banking Administration Guide

Defining all the Property and Conditions as shown below.

Again by using the add multi-value field button.

Select the corresponding Property class defined with 7 Conditions defined earlier.

The complete AA.PRODUCT.GROUP record DB.TEST

Validate to check for any errors and then commit.

TEMENOS T24 User Guide

Page 31 of 129
ARC Internet Banking Administration Guide

Proof and publishing

As per the AA framework architecture products must be first proofed and then published. Any errors
shown at the proof stage must be corrected before being proofed again then published.

Click on the blue play button at INTERNET.SERVICES within Product lines and again at
INTERNET.CLASS.OF.SERVICE within Product groups

The proof and publish stage

Click on the manage icon (gear & spanner). You will get a screen like below.

TEMENOS T24 User Guide

Page 32 of 129
ARC Internet Banking Administration Guide

The proof stage of the deal using AA.PRODUCT.MANAGER record DB.TEST

Input a GB DESCRIPTION and select PROOF for ACTION Field plus T24 date for AVAILABLE DATE
field. Then validate and commit.

TEMENOS T24 User Guide

Page 33 of 129
ARC Internet Banking Administration Guide

Click on the manage icon (gear & spanner) again.

Do the same again but this time select PUBLISH and validate the deal to check.

The publish stage of the deal using AA.PRODUCT.MANAGER record DB.TEST

Then commit. You will get a screen like below.

A completed deal in view mode

TEMENOS T24 User Guide

Page 34 of 129
ARC Internet Banking Administration Guide

Generate Arrangement ID
From the Menu Tab AA, click on the front office sub tab and then the product catalogue composite.

The AA menu from where to create your Arrangement ID

You will get a screen like below:-

When you click on the blue play button at INTERNET.SERVICES and again at ARC IB

Stepping Across to create new Arrangement

Next to generate a new Arrangement ID click on the new page icon for DB.TEST
This will pop-up another window as shown on the next page.

Entering customer number for which the arrangement is required

Select a CUSTOMER account from the drop down.
The @ID is automatically generated and is a no input field.
In the Arrangement field the term NEW is already populated in it. This tells the system to generate a
new arrangement.
The field CUSTOMER refers to the customer this arrangement is being created for.
PRODUCT is automatically generated with the name of the Internet Class of Service that you chose.
EFFECTIVE DATE is the system date.

TEMENOS T24 User Guide

Page 35 of 129
ARC Internet Banking Administration Guide

Click on Validate to check the class of service

This will then generate all the Product Conditions for this Product to appear as this stage is where
personalisation of the Product can take place

A final review of all details entered in AA.ARRANGEMENT.ACTIVITY

Change any fields that need changing then commit.

Arrangement number is linked to transaction ID above

Copy or note down the transaction ID from above.

Now you need to Logout and login as a different user to authorize the new record, by clicking on AA
Menu, Front Office and the Manage Arrangement option.

The mange arrangement record in the menu must be selected

TEMENOS T24 User Guide

Page 36 of 129
ARC Internet Banking Administration Guide

This will launch an enquiry selection window, where you can enter several different forms of data to
bring up your arrangement.

Enter any information that relates to your customer here

The created arrangement list

If there is an unauthorized arrangement it will be highlighted in this column.

Click in the Do Activity option and authorize the record.

Take note of the Arrangement number as this will be needed in the EB.EXTERNAL.USER
application.

TEMENOS T24 User Guide

Page 37 of 129
ARC Internet Banking Administration Guide

Click on the authorize button.

The completed arrangement with arrangement details

TEMENOS T24 User Guide

Page 38 of 129
ARC Internet Banking Administration Guide

Create user with EB.EXTERNAL.USER

From the command line enter EB.EXTERNAL.USER. This is where you create the external user and
link it with the recently created arrangement ID.

About to create an external user

Type in an internet user name e.g. 111222333, it must be nine numeric characters for record ID. The
user must specify 9 numbers of any order.

TEMENOS T24 User Guide

Page 39 of 129
ARC Internet Banking Administration Guide

The EB.EXTERNAL.USER application

There are several mandatory fields to be filled.

NAME: This should be the name of the customer.
CUSTOMER: This is the number of the customer to whom the EXTERNAL.USER is being created for.
PASSWORD Review: This is the date when the password should be change. Works under the format
chosen by the company in the Date Format. M (to be changed monthly) 01 (every month) DD (specify
the day it need changing)
Reference:
01 Every month
02 Every two months
03 Every quarter
06 Every 6 months
START DATE: The date it should start
END DATE: The date it will end
ATTEMPTS: the number of times the external user can attempt to login incorrectly before the user gets
locked out. This is between 1 – 9.
The Arrangement number which was just created goes in the field Arrangement.1
Note you must Logout and Login as a different user to authorize the new ARC user 111222333
before proceeding to the next section.

TEMENOS T24 User Guide

Page 40 of 129
ARC Internet Banking Administration Guide

Login To ARC-IB URL

Now after creating the EXTERNAL.USER, you can launch the ARC-IB URL e.g.
http://localhost:8080/ARC-IB/servlet/BrowserServlet

The Default External user log in screen

Enter the User ID 111222333 and a password e.g. 123456 and click Login or Enter.

When you successfully login the screen layout and menu designs created earlier will appear.

The created screen for this set up

TEMENOS T24 User Guide

Page 41 of 129
ARC Internet Banking Administration Guide

Additional Set up
Logging in methods for users
Below is the set up for using different login methods.
EB.CHANNEL
New channel records are created in EB.CHANNEL.

TEMENOS T24 User Guide

Page 42 of 129
ARC Internet Banking Administration Guide

EB.EXTERNAL.USER

CHANNEL will match entries in EB.CHANNEL

LOGIN.METHOD is made a mandatory field having a drop-down list of login methods.
MEMORABLE.DATA is no longer a part of the Channel Multi Value.

TEMENOS T24 User Guide

Page 43 of 129
ARC Internet Banking Administration Guide

ARC-IB Login Page

ARC-IB Login Page has been modified to allow multiple logins for the external user.
A single external user will be able to log in using different credentials which have different
levels of access (via arrangements).

The available entries in ARC Login Page are

o INTERNET.OTP-PIN (for one time password/PIN authentication)
o INTERNET.OTP (for one time password authentication)
o INTERNET.PW (for password only authentication)
o INTERNET.PW-MW (for password(pw)/memorable word (mw)
authentication)

TEMENOS T24 User Guide

Page 44 of 129
ARC Internet Banking Administration Guide

INTERNET.OTP-PIN

When logging in using the OTP-PIN credential, the corresponding arrangement is displayed to the
user. The Auth Type is selected accordingly.

TEMENOS T24 User Guide

Page 45 of 129
ARC Internet Banking Administration Guide

INTERNET.OTP

When logging in using the OTP credential, the corresponding arrangement is displayed to the user.
The Auth Type is selected accordingly.

TEMENOS T24 User Guide

Page 46 of 129
ARC Internet Banking Administration Guide

INTERNET.PW

TEMENOS T24 User Guide

Page 47 of 129
ARC Internet Banking Administration Guide

When logging in using the PW credential, the corresponding arrangement is displayed to the user. The
Auth Type is selected accordingly.

INTERNET.PW-MW

TEMENOS T24 User Guide

Page 48 of 129
ARC Internet Banking Administration Guide

When logging in using the PW-MW credential, the corresponding arrangement is displayed to the user.
The Auth Type is selected accordingly.

Binding to 4TRESS
On clicking the “Please Register here” link, the user will be redirected to the Registration page for
binding OTP and PIN to 4TRESS.

OTP and PIN need to be bound to 4TRESS first and only after successful binding can the user use
these credentials for logging into ARC.

TEMENOS T24 User Guide

Page 49 of 129
ARC Internet Banking Administration Guide

Successful binding message is seen.

TEMENOS T24 User Guide

Page 50 of 129
ARC Internet Banking Administration Guide

Transaction signing using challenge response

Below is configuration of transaction signing using challenge response.
EB.CHALLENGE.RESPONSE: Defines the Challenge Response methods during transaction
commit. Application, version, field details and the challenge is mentioned.

TEMENOS T24 User Guide

Page 51 of 129
ARC Internet Banking Administration Guide

VERSION: New field has been added to version to link Challenge Response Table and. ID of the
EB.CHALLENGE.RESPONSE table should be mentioned in the “Chall Resp” field of the CONFIRM
version.

TEMENOS T24 User Guide

Page 52 of 129
ARC Internet Banking Administration Guide

AA.PRD.DES.UI.BEHAVIOUR: New ATTRIBUTE called “CHALLENGE / RESPONSE” has

been added to EB.LOOKUP table named “COMMIT.ACTIONS*CHALLENGE.RESPONSE”. The new
attribute “CHALLENGE.RESPONSE” is present in the field Commit Action of
AA.PRD.DES.UI.BEHAVIOUR

TEMENOS T24 User Guide

Page 53 of 129
ARC Internet Banking Administration Guide

OVERRIDE: The following records have been added to OVERRIDE table and the attribute
“CHALLENGE RESPONSE” has been added to the “Approve method” field.

TEMENOS T24 User Guide

Page 54 of 129
ARC Internet Banking Administration Guide

Set up secure messages

In order for EB.SECURE.MESSAGE to work with ARC-IB, EB.EXTERNAL.USER has to work.

Also for the messages to be read and sent, some versions and enquiries must be created too. The
user can configure the enquiries and version to do exactly what they wish the system to do regarding
EB.SECURE.MESSAGE. Messages can be tracked by using context workflow to display the
PARENT.MESSAGE.ID to track a string of messages.
Below is one kind of set-up for reading and sending messages
• Enquiry to run at login to show customer and DAO inbox
• Enquiry for DAO to view replies and new messages from clients
• Enquiry for Customer to view replies and new messages from DAO/Bank departments
• Version for DAO to send messages and replies
Version for Customer to send and reply to messages

Enquiry for external customer to read their messages from the bank.

Above is a basic created enquiry which can be linked to the external user screen.

TEMENOS T24 User Guide

Page 55 of 129
ARC Internet Banking Administration Guide

Enquiry created to read messages from external customer to DAO

The PREDEFINED.SELECTION in the record above is populated with “TO STATUS EQ UNREAD“.
This will filter out all the read messages, and only display the unread messages.

TEMENOS T24 User Guide

Page 56 of 129
ARC Internet Banking Administration Guide

The DAO record

On DAO record there is a new field called ACCEPT.MESSAGE. When this is checked, an external user
can select who they want to send the message to.

TEMENOS T24 User Guide

Page 57 of 129
ARC Internet Banking Administration Guide

The user record with department code as DAO officer

The DAO is defaulted from the DEPARTMENT.CODE field in USER record. This can be a DAO or a
bank department.

TEMENOS T24 User Guide

Page 58 of 129
ARC Internet Banking Administration Guide

New message from customer to accepting DAOS

A new message from external customer displaying DAO with ACCEPT.MESSAGES checked.

Creation of Account Mandates

To enable the creation of Account Mandates the following tables need to be established:
EB.SIGNATORY.GROUP
EB.MANDATE
EB.MANDATE.PARAMETER
EB.SIGNATORY.GROUP:
This table contains the internal organisation structure of a corporate customer. Various groups of
employees (to be stored as T24 customers) of the corporate organization will be grouped together as
an identifiable group. The same group can be linked to the mandate such that appropriate rights can
be provided. For a mandate, the signatories have to be within the group.
Below are examples of an EB.SIGNATORY.GROUP set up for a corporate customer Dell with the
various levels from Director to Section Head.

TEMENOS T24 User Guide

Page 59 of 129
ARC Internet Banking Administration Guide

TEMENOS T24 User Guide

Page 60 of 129
ARC Internet Banking Administration Guide

TEMENOS T24 User Guide

Page 61 of 129
ARC Internet Banking Administration Guide

EB.MANDATE.
The above EB.SIGNATORY.GROUPS is then linked into the EB.MANDATE record. This is keyed on
the customer record with a given sequence number. This contains information on the signatory groups
required for authorisation of transactions within a given range. This also specifies the minimum
signatories required for a particular transaction involving the same customer.

TEMENOS T24 User Guide

Page 62 of 129
ARC Internet Banking Administration Guide

EB.MANDATE.PARAMETER
This table is keyed based on a valid T24 application. This contains information on the location of
amount field, customer field to be looked up for every application. This controls the application allowed
to be accessed by the external user.

TEMENOS T24 User Guide

Page 63 of 129
ARC Internet Banking Administration Guide

TEMENOS T24 User Guide

Page 64 of 129
ARC Internet Banking Administration Guide

The fields MANDATE.APPLICAITON / MANDATE.REG/ MANDATE RECORD on the applications

CUSTOMER and ACCOUNT are used to link the above tables.

Field Field Name Type Description Example

No
XX < MANDATE.APPLICATION Must be a record on FUNDS.TRANSFER. If
MANDATE.PARAMETER. left blank, applies to all
Indicates for which application applications
these mandate settings apply.
XX - MANDATE.REG (or ERG) Must be a record on ONLY.AC.TRANSFERS
EB.RULE.GATEWAY.
Indicates the rule that must be
passed to ensure the mandate
checking is triggered. Not a
mandatory field, if null then the
mandate checking is always
triggered.
XX > MANDATE.RECORD Must be a record from 100123.ABCDE
EB.MANDATE – when the
APPLICATION is used, and the
rule posed in MANDATE.REG
is used, so that mandate
checking is required, this is the
MANDATE that is checked
against to ensure that the
correct number of signatories
etc are available.

TEMENOS T24 User Guide

Page 65 of 129
ARC Internet Banking Administration Guide

The mandate record field is populated with the EB.MANDATE records set up for this customer and
associated account.

TEMENOS T24 User Guide

Page 66 of 129
ARC Internet Banking Administration Guide

Drop down selection based on the setting in EB.MANDATE

The field SIGNATORY on application FUNDS.TRANSFER /BULK.STANDING.ORDER

/STANDING.ORDER and DIRECT.DEBITS indicates the customers who are signing this particular
transaction.

Field Field Name Type Description Example

No
XX - SIGNATORY Indicates the customers who 123123123
are signing this particular
456456456
transaction
(FT,STO,BULK.STO etc) and 789789789
therefore approving it for
processing. These customers
will be compared with the
mandate requirements, to see if
they fit and the trade can
therefore go through.

TEMENOS T24 User Guide

Page 67 of 129
ARC Internet Banking Administration Guide

TEMENOS T24 User Guide

Page 68 of 129
ARC Internet Banking Administration Guide

EB.EXTERNAL.SIGNATURE
Based on the previous tables two ARC user Julie and Richard are established. This means that for
transactions less than 50,000 either two department heads or one manager have to sign.

TEMENOS T24 User Guide

Page 69 of 129
ARC Internet Banking Administration Guide

FUNDS.TRANSFER entered by Richard

TEMENOS T24 User Guide

Page 70 of 129
ARC Internet Banking Administration Guide

View of the above FUNDS.TRANSFER displays Richard as the signatory

TEMENOS T24 User Guide

Page 71 of 129
ARC Internet Banking Administration Guide

Example of the approval enquiry displayed for Julie

TEMENOS T24 User Guide

Page 72 of 129
ARC Internet Banking Administration Guide

TEMENOS T24 User Guide

Page 73 of 129
ARC Internet Banking Administration Guide

Julie has authorised the FUNDS.TRANSFER

TEMENOS T24 User Guide

Page 74 of 129
ARC Internet Banking Administration Guide

FUNDS.TRANSFER displayed in Browser shows Julie and Richard signature

Intermediary Services/Proxy Permissions

For an Intermediary to work they have to have the products they are allowed and the Customers they
are allowed to act on behalf of completed via INTERNET.SERVICES and further access restriction to
be provided by having a new AA property class associated with each of the Customers he acts for.
This property class is called PROXY.PERMISSIONS and contains the following:

The PROXY.PERMISSION table

This gives explicit permission for a Proxy (Intermediary) (defined by his Customer number) to access a
Customer’s specific accounts, arrangements, contracts and portfolios. Several Proxies may act on
behalf of a single Customer.
All Customers who have Proxies acting for them must have an AA arrangement which consists of the
AA property classes: CUSTOMER and PROXY.PERMISSIONS. This should be an AA Product in a
new AA Product Line called PROXY.SERVICES.

TEMENOS T24 User Guide

Page 75 of 129
ARC Internet Banking Administration Guide

A PROXY.SERVICES arrangement is linked to INTERNET.SERVICES arrangement via the class

USER.RIGHTS. In USER.RIGHTS we have a new multi-valued
ALLOWED.CUSTOMER/PROXY.ARRANGEMENT field. There can be an unlimited number of
customers, but each customer can only have a single proxy services arrangement here.

Displaying the proxy arrangement set up

The setup for a proxy user is to be done as below:

TEMENOS T24 User Guide

Page 76 of 129
ARC Internet Banking Administration Guide

AA.PROXY.PERMISSIONS
There is a PROXY.SERVICES
Arrangement for each Internet
user who has access to the
Corporate CUSTOMER Corporate’s accounts
CUSTOMER PROXY.SERVICES
ARRANGEMENT
~~~~~~~~~
~~~~~~~~~ CUSTOMER Corporate employee user 1
~~~~~~~~~ PROXY.PERMISSIONS
~~~~~~~~~ PROXY 1
~~~~~~~~~ ACCOUNT 1
~~~~~~~~~ ACCOUNT 7 Every user has their own
ACCOUNT 9 arrangement. There are
PROXY.SERVICES different classes of service for
ARRANGEMENT corporate users e.g. inputter,
CUSTOMER
view only, inputter and
PROXY.PERMISSIONS authoriser, administrator.
PROXY 2
ACCOUNT 1 Generally these do not need to
ACCOUNT 7
ACCOUNT 9
be specific to a single corporate.
PROXY.SERVICES INTERNET.SERVICES CUSTOMER
ARRANGEMENT ARRANGEMENT
~~~~~~~~~
CUSTOMER CUSTOMER ~~~~~~~~~
PROXY.PERMISSIONS ~~~~~~~~~ ~~~~~~~~~
PROXY 3 ~~~~~~~~~ ~~~~~~~~~
ACCOUNT 1 ~~~~~~~~~ ~~~~~~~~~
ACCOUNT 3 ~~~~~~~~~ ~~~~~~~~~
ACCOUNT 5 ~~~~~~~~~
ACCOUNT 7 USER.RIGHTS
ALLOWED CUSTOMER 1
PROXY ARRANGEMENT 1

Customer record so
bank knows details of
Normally for corporate users user
there will only be one allowed
customer. However, employees
of a parent company may have EB.EXTERNAL.USER
access to accounts of CUSTOMER
subsiduaries, so there would ~~~~~~~~~~
ARRANGEMENT
then be an entry for the parent ~~~~~~~~~
~~~~~~~~~
and each subsidiary ~~~~~~~~~
~~~~~~~~~

A detailed diagram of Proxy Permission set up

TEMENOS T24 User Guide

Page 77 of 129
ARC Internet Banking Administration Guide

To create a proxy permission the following files need to be created in AA, for a more detailed
explanation of the relevance of these files please refer to the AA user guide.

Example of an AA.PROPRTY

TEMENOS T24 User Guide

Page 78 of 129
ARC Internet Banking Administration Guide

Example of an AA.PRODUCT.GROUP

TEMENOS T24 User Guide

Page 79 of 129
ARC Internet Banking Administration Guide

Example of AA.PRODUCT.DESIGNER

TEMENOS T24 User Guide

Page 80 of 129
ARC Internet Banking Administration Guide

An example AA.PRD.DES.CUSTOMER

The above property class tester is linked to the previous screen.

TEMENOS T24 User Guide

Page 81 of 129
ARC Internet Banking Administration Guide

Example of AA.PRODUCT.MANAGER
Once all the above records have been created you need to proof and publish the records to check all
conditions are correct. If you have done something wrong you will receive an error on the above
application AA.PRODUCT.MANAGER.
Once this has been accepted and published then the product will be created.

TEMENOS T24 User Guide

Page 82 of 129
ARC Internet Banking Administration Guide

The above shows the product has been created.

The above shows a record of what has been done to the new product.
Next create the actual AA.ARRANGEMENT.

TEMENOS T24 User Guide

Page 83 of 129
ARC Internet Banking Administration Guide

TEMENOS T24 User Guide

Page 84 of 129
ARC Internet Banking Administration Guide

Dell is the customer and the proxy is Julie.

Julie has now got access to dell USD accounts.

TEMENOS T24 User Guide

Page 85 of 129
ARC Internet Banking Administration Guide

AA.ARR.PROXY.PERMISSIONS has also been created from the arrangement number

AA00335HVYNH.

TEMENOS T24 User Guide

Page 86 of 129
ARC Internet Banking Administration Guide

To create the access for the ARC user you need to set up the following:

First create a SMS group that will restrict/allow access to the applications in T24, this can be a group
rather than creating one for each customer:

TEMENOS T24 User Guide

Page 87 of 129
ARC Internet Banking Administration Guide

Next the AA.PRODUCT used was INTERMEDIARY

TEMENOS T24 User Guide

Page 88 of 129
ARC Internet Banking Administration Guide

Product line called INTERNET.SERVICES within the product are property classes, we need to update
the AA.PRODUCT.CONDITION for user rights.

TEMENOS T24 User Guide

Page 89 of 129
ARC Internet Banking Administration Guide

This is then linked to the AA.PRODUCT.CONDITIONS:

So in the classes USER.RIGHTS we have several Product Conditions, we would then create a
condition called INTERMIDIARY and add the SMS user group AI.INTERMIDIARY to this condition in
the field SMS group.

So now the PRODUCT called INTERMIDIARY has been updated with these SMS conditions which
are linked to the USER RIGHTS.
When creating the AA.ARRNAGEMENT for the external user we will use the Product name
INTERMIDIARY in the field Product for this example.

TEMENOS T24 User Guide

Page 90 of 129
ARC Internet Banking Administration Guide

TEMENOS T24 User Guide

Page 91 of 129
ARC Internet Banking Administration Guide

The user rights is updated with the link to the AA.ARRANGEMENT for DELL under AA00335HVYNH.

TEMENOS T24 User Guide

Page 92 of 129
ARC Internet Banking Administration Guide

The UI behaviour shows the link to the composite screen used for the user.

TEMENOS T24 User Guide

Page 93 of 129
ARC Internet Banking Administration Guide

Then you must create an EB.EXTERNAL.USER record for the proxy user like below

We can see the arrangement ID used AA00335SGRN is taken from the AA intermediary arrangement
set up in the previous screen.
You will know be able to log in as en external proxy user in ARC
Proxy arrangements can be made once the set up as detailed above is complete. The person allowing
their account, portfolio etc to be viewed by an external person (intermediary) must set up the proxy
arrangement.

TEMENOS T24 User Guide

Page 94 of 129
ARC Internet Banking Administration Guide

Enquiries
!EXT.Variables
An enquiry can be run to display information for the !EXT customer, account or any selection criteria
you define. To define a !EXT selection you must first run an ENQUIRY called !EXT.XXX where XXX is
the name you will give to the !EXT selection item. The data you enter in the first selection will then
become the !EXT selection criteria. You can then reference this value in another enquiry selection by
entering !!EXT.XXX in the selection criteria column.
Browser will support setting these !EXT.XXX variables either with values from another field or with a
literal value (such as “123”).
So not only can the variables be set in one Enquiry and used in others but the content can be set from
a field value or a literal as well as from selection data.
The variables can also then be used in context based workflows such as pre-filling fields on a Version
from the Enquiry output and populated variables..
These variables can be used in a version in the AUTOM.NEW.CONTENT field.
Literal values can also be set too. It can be a single literal eg “ACCOUNT” or a string literal with
spaces eg “NEW !EXT ACCOUNT” or , “100069”, “My Customer”, as long as the literal is in speech
marks.
A list of values can also be displayed as long as the values are surrounded by [ ] e.g. [A] [B] [C]
The ENQUIRY called USER.VARIABLES allows the user to list the !EXT content of any !!EXT
variables

EB.External.User
With EB.EXTERNAL.USER, when an external user logs in the following variables are set
automatically.
!EXT.CUSTOMER (Customer number)
!EXT.EXTERNAL.USER (Mnemonic)
!EXT.ARRANGEMENT (Arrangement number)

!VARIABLEs in SMS
The following variables get initialised when the user logs in based on the data and access rights
provided:

• !EXT.SMS.CUSTOMERS
• !EXT.SMS.ACCOUNTS
• !EXT.SMS.ARRANGEMENTS
• !EXT.SMS.CONTRACTS

TEMENOS T24 User Guide

Page 95 of 129
ARC Internet Banking Administration Guide

• !EXT.SMS.PORTFOLIOS
• !EXT.SMS.EXTERNAL.CUSTOMER

!EXT.SMS.EXTERNAL.CUSTOMER
There is a !EXT variable called !EXT.CUSTOMER which is set to the CUSTOMER in the
EB.EXTERNAL.USER. The value in !EXT.CUSTOMER is also assigned
to !EXT.SMS.EXTERNAL.CUSTOMER.

Displaying !EXT.SMS.EXTERNAL.CUSTOMER with variable value

!EXT.SMS.CUSTOMERS
This is to be set to the multi value list of Customer in field ALLOWED.CUSTOMERS in the property class
USER.RIGHTS.
THE customer number entered in the ALLOWED.CUSTOMER field enables access and input of
contracts on behalf of this CUSTOMER.

Displaying !EXT.SMS.CUSTOMER with variable value

.

TEMENOS T24 User Guide

Page 96 of 129
ARC Internet Banking Administration Guide

TEMENOS T24 User Guide

Page 97 of 129
ARC Internet Banking Administration Guide

!EXT.SMS.ACCOUNTS
This will be set as follows:
A. For Direct User (!EXT.SMS.EXTERNAL.CUSTOMER same as Allowed Customer)
Select all ACCOUNT Id’s whose CONDITION.GROUP is that of value specified in AC.GRP.ALLOW
(Note: AC.GRP.ALLOW is a m/v field.)
If no value is specified in AC.GRP.ALLOW or PRODUCT.ACCESS then ACCOUNT Id’s would be
NULL.
B. For Proxy User:
For all the Customers in !EXT.SMS.CUSTOMERS:

The arrangement record (use the AA API AA.GET.ARRANGEMENT) specified in the associated
PROXY.ARRANGEMENT field is read. Then, the list of Accounts specified in the field Account in the
associated PROXY.PERMISSIONS property class (use AA API AA.GET.PROPERTY.CONDITIONS)
is arrived at. If ALL is specified, then the concat file CUSTOMER.ACCOUNT is read to get the list of
Accounts. Now the list of Accounts is scanned and the Account’s whose CONDITION.GROUP is that
of value specified in AC.GRP.ALLOW is taken as the value for this variable(Note: AC.GRP.ALLOW is
a multi value field.)

Displaying multiple values for !EXT.SMS.ACCOUNTS

!EXT.SMS.ARRANGEMENTS
A. Direct User:
The AA.ARRAGEMENT file with Customer same as !EXT.SMS.EXTERNAL.CUSTOMER is selected
and is added to the value of the variable
B. Proxy User:
For all the Customers in !EXT.SMS.CUSTOMERS:
The arrangement record (use the AA API AA.GET.ARRANGEMENT) specified in the associated
PROXY.ARRANGEMENT field) is read. Then, the list of Arrangement specified in the field
Arrangement in the associated PROXY.PERMISSIONS property class (use AA API
AA.GET.PROPERTY.CONDITIONS) is arrived at. If ALL is specified, then the file
AA.ARRANGEMENT is selected with CUSTOMER EQ !EXT.SMS.CUSTOMERS and is added to the
value of the variable.

TEMENOS T24 User Guide

Page 98 of 129
ARC Internet Banking Administration Guide

Displaying the !EXT.SMS.ARRANGEMENTS

!EXT.SMS.CONTRACTS:
A. Direct User:
For the moment we do not have the logic to populate this variable for a Direct User.
B. For Proxy User:
For all the Customers in !EXT.SMS.CUSTOMERS:
The arrangement record (use the AA API AA.GET.ARRANGEMENT) specified in the associated
PROXY.ARRANGEMENT field) is read. The list of Contracts specified in the field Account in the
associated PROXY.PERMISSIONS property class (use AA API AA.GET.PROPERTY.CONDITIONS)
is arrived at and produced as the value for this variable.

Displaying the !EXT.SMS.CONTRACTS

TEMENOS T24 User Guide

Page 99 of 129
ARC Internet Banking Administration Guide

!EXT.SMS.PORTFOLIOS
A. For Direct User
The file SEC.ACC.CUST with ID as !EXT.SMS.EXTERNAL.CUSTOMER is read and the list of
portfolio’s of that Customer is arrived at. Now, the portfolio’s which have the MANAGED.ACCOUNT
same as the values specified in PORT.ALLOW is filtered and is added as the value to this variable.

B. For Proxy User:

The arrangement record (use the AA API AA.GET.ARRANGEMENT) specified in the associated
PROXY.ARRANGEMENT field) is read. Now, the list of Accounts specified in the field Account in the
associated PROXY.PERMISSIONS property class (use AA API AA.GET.PROPERTY.CONDITIONS)
is arrived at. If ALL is specified, then the file SEC.ACC.CUST with ID as Customer is read and the list
of portfolio’s of that Customer is filtered. Now, the portfolio’s which have the MANAGED.ACCOUNT
same as the values specified in PORT.ALLOW is taken as the value for the variable

Displaying the !EXT.SMS.PORTFOLIOS

Deal/Transaction processing
Payments
Payments can be made to the customers other accounts with bank, to a loan, credit card or mortgage,
as long as all products are from the same bank the customer is logging into. The displayed data is
editable by the bank using version and enquiries and context workflow within the version.

TEMENOS T24 User Guide

Page 100 of 129
ARC Internet Banking Administration Guide

Displaying customers’ accounts

TEMENOS T24 User Guide

Page 101 of 129
ARC Internet Banking Administration Guide

Transferring money from one account to the other.

Note- we did not set up the same menu as above in our set up, they were created earlier.

TEMENOS T24 User Guide

Page 102 of 129
ARC Internet Banking Administration Guide

Showing the preview and confirm before deal slip is displayed.

TEMENOS T24 User Guide

Page 103 of 129
ARC Internet Banking Administration Guide

Confirmation of transaction

TEMENOS T24 User Guide

Page 104 of 129
ARC Internet Banking Administration Guide

Secure messaging
The functionality for EB.SECURE.MESSAGE is for banks to communicate with their customers and
vice versa with classified secure information, such as overdraft results, loans application outcomes,
promotions and offers.

Working process

Creating a new message from the bank to external customer

A simple revision for the bank staff to use.

TEMENOS T24 User Guide

Page 105 of 129
ARC Internet Banking Administration Guide

Message received in customer inbox, and unread status.

Our illustration above shows the client new messages when they log in.
Note- We can filter the messages base on the client and message status.

TEMENOS T24 User Guide

Page 106 of 129
ARC Internet Banking Administration Guide

Customer received message

Reading message as external customer, once commit button (green arrow) is pressed, status will
change to read.

TEMENOS T24 User Guide

Page 107 of 129
ARC Internet Banking Administration Guide

Above shows customer inbox with message status changed to read.

Above shows the message status has changed to read as the customer has read the message.

TEMENOS T24 User Guide

Page 108 of 129
ARC Internet Banking Administration Guide

About to reply to DEPARTMENT.ACCOUNT.OFFICER from inbox

Customer having read message is about to reply to the DEPARTMENT.ACCOUNT.OFFICER

(DAO) to acknowledge the receipt of the message.

TEMENOS T24 User Guide

Page 109 of 129
ARC Internet Banking Administration Guide

DEPARTMENT.ACCOUNT.OFFICER is defaulted in due to version, and reply is typed and sent.

The DAO is defaulted in due to VERSION content, and reply is typed and sent, note the PARENT
MESSAGE ID, as this enables the external customer to follow the message string back to the start.

TEMENOS T24 User Guide

Page 110 of 129
ARC Internet Banking Administration Guide

Reading reply in DEPARTMENT.ACCOUNT.OFFICERS inbox

The message from the bank or customer can be sent from the application EB.SECURE.MESSAGE
and by setting up different enquiries and versions, the sender or recipients can view, reply and delete
messages. The DAO has to have the ACCEPT.MESSAGES field set to yes in the DAO record.
The functionality is dependent on how the user configures the VERSIONS and ENQUIRIES

Account Mandates
Account mandates within T24 can be linked to individual accounts so that there can be more
signatories, a range of signatory levels, and a dependency on the transaction value. These mandates
are available for bank staff to view. Transactions subject to mandate carried out by internal bank
users have the signatories manually entered onto a transaction and then checked by T24 against the
mandate. For ARC Internet Banking the signatories are checked automatically.
Introduction
For ARC IB External Users (e.g. corporate employees) -
1. Who is allowed to enquire on an account
2. Who is allowed to input debit transactions on an account (Funds Transfer, Standing Order,
Bulk Standing Order)
3. The number of signatories and level of signatory and debit amount for a debit transaction on
an account – see example below:

TEMENOS T24 User Guide

Page 111 of 129
ARC Internet Banking Administration Guide

Authorised Authorised Authorised Authorised

Signature Signature Signature Signature
Dept Head Manager Area Manager Director

Up to $4,000,000 Y

Up to $200,000 YY

Up to $100,000 YY Y

Up to $50,000 YY Y

Up to $25,000 Y

Example mandate structure

People (e.g. Corporate

Corporate Customers
employees)
CUSTOMER EB.MANDATE CUSTOMER

CUSTOMER EB.MANDATE CUSTOMER

0-n 1
0-n 0-n EB.MANDATE
0-n

0-n

0-n
1-n People (e.g. Corporate
0-n employees)
ACCOUNT / 0-n EB.SIGNATORY.GROUP CUSTOMER
PORTFOLIO
ACCOUNT
ACCOUNT/ EB.SIGNATORY.GROUP CUSTOMER
PORTFOLIO
0-n 1-n
ACCOUNT
ACCOUNT/ EB.SIGNATORY.GROUP CUSTOMER
PORTFOLIO
ACCOUNT / EB.SIGNATORY.GROUP CUSTOMER
PORTFOLIO

CUSTOMER

Example of a relationship diagram

TEMENOS T24 User Guide

Page 112 of 129
ARC Internet Banking Administration Guide

The diagram above shows the relationship between the new tables and the existing CUSTOMER
and ACCOUNT tables. Note that:
• An Account, Customer or Portfolio can have zero or more Mandates, which applies to all
applications, different mandates for each application or even different mandates for different
circumstances within the same application. Mandates can be shared by
accounts/customers/portfolios. Note, the mandates would only be shared on customers
where the concept of a ‘Container Customer’ is used.
• A Mandate must have one or more Signatory Groups OR Customers (Corporate employees)
associated with it.
• A Mandate has a single Customer (normally a corporate) associated with it. A corporate
Customer can have several Mandates (maximum is the number of accounts held).
• A corporate Customer, for these purposes, must have one or more Customers (Corporate
employees) associated with it.

Creation of Account Mandates

To enable the creation of Account Mandates the following tables need to be established:
EB.SIGNATORY.GROUP
EB.MANDATE
EB.MANDATE.PARAMETER

EB.SIGNATORY.GROUP:
This table contains the internal organisation structure of a corporate customer. Various groups of
employees (to be stored as T24 customers) of the corporate organization will be grouped together as
an identifiable group. The same group can be linked to the mandate such that appropriate rights can
be provided. For a mandate, the signatories have to be within the group.
Below are examples of an EB.SIGNATORY.GROUP set up for a corporate customer Dell with the
various levels from Director to Section Head.

TEMENOS T24 User Guide

Page 113 of 129
ARC Internet Banking Administration Guide

TEMENOS T24 User Guide

Page 114 of 129
ARC Internet Banking Administration Guide

EB.MANDATE.
The above EB.SIGNATORY.GROUPS is then linked into the EB.MANDATE record. This is keyed on
the customer record with a given sequence number. This contains information on the signatory groups
required for authorisation of transactions within a given range. This also specifies the minimum
signatories required for a particular transaction involving the same customer.

TEMENOS T24 User Guide

Page 115 of 129
ARC Internet Banking Administration Guide

TEMENOS T24 User Guide

Page 116 of 129
ARC Internet Banking Administration Guide

EB.MANADATE.PARAMETER
This table is keyed based on a valid T24 application. This contains information on the location of
amount field, customer field to be looked up for every application. This controls the application allowed
to be accessed by the external user.

TEMENOS T24 User Guide

Page 117 of 129
ARC Internet Banking Administration Guide

TEMENOS T24 User Guide

Page 118 of 129
ARC Internet Banking Administration Guide

The fields MANDATE.APPLICAITON / MANDATE.REG/ MANDATE RECORD on the applications

CUSTOMER and ACCOUNT are used to link the above tables.

Field Field Name Type Description Example

No
XX < MANDATE.APPLICATION Must be a record on FUNDS.TRANSFER. If
MANDATE.PARAMETER. left blank, applies to all
Indicates for which application applications
these mandate settings apply.
XX - MANDATE.REG (or ERG) Must be a record on ONLY.AC.TRANSFERS
EB.RULE.GATEWAY.
Indicates the rule that must be
passed to ensure the mandate
checking is triggered. Not a
mandatory field, if null then the
mandate checking is always
triggered.
XX > MANDATE.RECORD Must be a record from 100123.ABCDE
EB.MANDATE – when the
APPLICATION is used, and the
rule posed in MANDATE.REG
is used, so that mandate
checking is required, this is the
MANDATE that is checked
against to ensure that the
correct number of signatories
etc are available.

TEMENOS T24 User Guide

Page 119 of 129
ARC Internet Banking Administration Guide

The mandate record field is populated with the EB.MANDATE records set up for this customer and
associated account.

TEMENOS T24 User Guide

Page 120 of 129
ARC Internet Banking Administration Guide

Drop down selection based on the setting in EB.MANDATE

The field SIGNATORY on application FUNDS.TRANSFER /BULK.STANDING.ORDER

/STANDING.ORDER and DIRECT.DEBITS indicates the customers who are signing this particular
transaction.

Field Field Name Type Description Example

No
XX - SIGNATORY Indicates the customers who 123123123
are signing this particular
456456456
transaction
(FT,STO,BULK.STO etc) and 789789789
therefore approving it for
processing. These customers
will be compared with the
mandate requirements, to see if
they fit and the trade can
therefore go through.

TEMENOS T24 User Guide

Page 121 of 129
ARC Internet Banking Administration Guide

TEMENOS T24 User Guide

Page 122 of 129
ARC Internet Banking Administration Guide

EB.EXTERNAL.SIGNATURE

Based on the previous tables two ARC user Julie and Richard are established. This means that for
transactions less than 50,000 either two department heads or one manager have to sign.

TEMENOS T24 User Guide

Page 123 of 129
ARC Internet Banking Administration Guide

FUNDS.TRANSFER entered by Richard

TEMENOS T24 User Guide

Page 124 of 129
ARC Internet Banking Administration Guide

View of the above FUNDS.TRANSFER displays Richard as the signatory

TEMENOS T24 User Guide

Page 125 of 129
ARC Internet Banking Administration Guide

Example of the approval enquiry displayed for Julie

TEMENOS T24 User Guide

Page 126 of 129
ARC Internet Banking Administration Guide

TEMENOS T24 User Guide

Page 127 of 129
ARC Internet Banking Administration Guide

Julie has authorised the FUNDS.TRANSFER

TEMENOS T24 User Guide

Page 128 of 129
ARC Internet Banking Administration Guide

FUNDS.TRANSFER displayed in Browser shows Julie and Richard signature

Implementation of ARC-IB Browser on Web sphere

For details on implementation of ARC-IB browser on web sphere ,please refer to the user guide on
“Browser Security Guide”

TEMENOS T24 User Guide

Page 129 of 129