1

1
Objectives for the course
2
 Introducing the participants to the concept of payments hub
 Configuring and processing incoming, outgoing, redirect and book
SWIFT payments
 Overview of batch processing (Single debit and multiple credits)
 Understand the need and use of warehousing capability, debit
authority, code words balance reservation, TRIP (Track and Trace
Mechanism)
 Overview of linkage to STeP (Automated Repair Tool) and AML
(Filtering)
 Understand how processed payments can be reversed
 Understand how incoming and outgoing claims are processed
 Understand configuration of local clearing and how system can be
scaled to support additional clearings
 Understand how direct debits (both incoming and outgoing) are
processed
 Using reports and enquiries to perform payments monitoring and
analytics
Prerequisites for this Course 3

 T24 Induction course (T2ITC)

 Understanding of International and Domestic Payments Business
 Hands on experience with T24 product (or) Any other Banking /
Payment Product
Suggested pre-requisite courses 4

 Delivery and SWIFT

 Funds Transfer
 Direct Debit
 Expected Receipts
 Local Clearing
 Nostro Reconciliations
 5

TPS Day 1
 Learning Objectives 6

6
Objectives

 Learn about the:

 Universal Payment Process Flow in Temenos Payment Suite
 Understand the Data Model of TPS

 Learn How to setup the basic Static Data Configuration of TPS

Understand how Incoming messages are received, accepted and
mapped in TPS
Understand the concept of
 Weight Assignment
 Debit Authority
 Debit Party Determination
 Warehousing of Payments
 Balance Check
 Direction Determination
 Product Determination
 TPS – Channel Agnostic
7

MT101 SWIFT
Corporate MT1nn/MT2nn/MT9n
client
pain/
n
bulk files RTGS

SWIFT pacs (ISO 20022)

MT1Nn/2nn/9nn

Bank
Correspondent
MT101 TPS pain (ISO 20022)
Branch own system, pain/bulks Universal
System indirect Payment Hub camt (ISO 20022)
pacs
participant
Local clearing

RTGS Return
PEACH, Local clearing
ACH, Internal transfer
Central pacs
Bank
Return

7
Understanding different message formats 8

Transformation Layer
Payment
Generic Neutral
XML Object
schema

SEPA (Europe)
ACH (US)
SWIFT
TPS – Components Overview
9

Acceptance
Acceptance Payment
PaymentInitialization
Initialization Duplicate
DuplicateCheck
Check Payment
PaymentFinalization
Finalization

Mapping
Mappingand
and Debit
DebitAuthority
Authority Date
DateDetermination
Determination
Assign Weight
Assign Weight

Debit
DebitParty
Party Credit
Auto CreditBank
Bank//Client
Client Credit
CreditBank
Bank
AutoRepair
Repair Determination
Determination Conditions
Conditions Conditions
Conditions

Debit
DebitBank
Bank Credit
CreditParty
Party
STP Validate
ValidateCredit
CreditParty
STPFlow Conditions Determination Party
Flow Conditions Determination

YES Future
FutureRED
RED YES
Payment
Payment
Filtering
Filtering Warehouse
Warehouse
or
orRCVD?
RCVD? Incoming
Incoming NO Routing
RoutingAnd
And
NO or
orBook?
Book? Settlement
Settlement

Payment Future Due Balance

BalanceCheck
Check
Payment Future Due
Warehouse YES Date Debit
Warehouse Date DebitClient
Client
NO Conditions
Conditions
Direction
Direction
Determination
Determination
Fee
Fee

Product
Product
Posting Determination
Determination
Posting

Output Future Send

Output Future Send
Warehouse YES Date Links to External Application Links to DDA Adaptor
Warehouse Date
NO

Payment
PaymentGeneration
Generation
Configuration Driven to enable high STP rates
10
Dashboards
11
Mid Office Payment Entry Screen
12
Exception Handling - Repair and Resubmit Payments
13
In detail audit logs – Trace everything that happens to a payment
14
 15

Static Data Configuration

Concept of capture and store – Will be made obsolete 16

16
 Concepts

Capture data in Store in database

a form table(s)

PP.<Form Name> PPT.<Table Name>

Introduction to concept of POR tables 17

17
 POR.TABLES

POR.TABLE Payment transaction data update by TPS

Some of Key POR.TABLES:

POR.TRANSACTION
POR.ACCOUNTINFO
POR.ADDITIONALINF
POR.PARTYCREDIT
POR.PARTYDEBIT
POR.POSTINGLINE
Business Case 1 18

 Incoming MT103 18
Process incoming MT103 19

19
 Business Case 1

Alfa Beta in US, wishes to pay USD 340 to his supplier Nike located in UK.

Nike holds an USD account with T24 Bank while Alfa Beta has an USD account with CITI
Bank in US, NY

CITI Bank, on behalf of Alfa Beta sends a MT103 to T24 Bank

CITI Bank shares a direct account relationship with T24 Bank.

T24BANK uses TPS (Temenos Payment System) for handling all types of payment
transactions and T24 acts as the DDA system (Demand Deposit Account)

Transaction charges on the receiver’s side is NIL

Charge type used is SHA

Process incoming MT103 20

20
 MT103 Message flow

Ordering Alpha Beta

Customer
 
 
 
  
CITI Bank
Sender
(CITIUS33)
 
 
  
  

T24 BANK
Receiver
(DEMOGB)
 
 

Beneficiary
Customer Nike, UK
 
 
Process incoming MT103 21

21
 MT103 Message

{1:F01DEMOGBPXAXXX9024629991}{2:O1031425131119CITIUS33AXXX89245950131311191435S}{3:{108:BNKMT103FXSHA}}{4:

:20:BUC1MT013INC

:23B:CRED

:32A:160719USD340,00

:50K:/GB10MIDL40051574128754

Alfa Beta

New York

US

:52A:MIDLGB22XXX

:59:/11193

Nike

London

UK

:70:INCOMING STP NO FX

:71A:SHA

-}

SWIFTMT103-BUC1-001.txt
Introduction to payment neutral object 22

 Message Received and Mapped22

Introduction to concept of POR tables 23

23
 POR.TABLES
 POR.TRANSACTION main payment object table
Introduction to concept of POR tables 24

 Other POR Tables 24

Party Roles 25

25
Static Data Configuration 26

 Introduction to Static Data 26

Configuration in TPS

 TPS Static tables

 PPT.COMPANY
 PPT.COMPANYPROPERTIES
 PPT.CURRENCY
 PPT.SOURCE
 PPT.CHANNEL
 PPT.REGION
 PPT.STATUSCODE
Static Data Configuration 27

27
 PPT.COMPANY
Static Data Configuration 28

28

 PPT.COMPANYPROPERTIES

Company’s key attributes are

captured in this table
Static Data Configuration 29

29
 PPT.CURRENCY
 CURRENCY Record
Static Data Configuration 30

30
 PPT.SOURCE
 “SOURCE” using Swift Channel

CHAPS SWIFT

SWIFT
TARGET2

Source ChannelName SourceDescription

CHAPS SWIFT CHAPS payments recevied via SWIFT

SWIFT SWIFT SWIFT messages received via SWIFT

TARGET SWIFT TARGET2 payments received via SWIFT

Static Data Configuration 31

31
 PPT.CHANNEL

 Payment Channels
Static Data Configuration 32

32
 PPT.REGION
 Entity’s Region in the country

 Country Code

 Region
Static Data Configuration 33

 STATUSCODE 33
 PPT.STATUSCODE
 Payment transaction flow monitor
 Signifies payment current state and completion (i.e. ‘999’)
How does TPS process a payment message?
34

Acceptance
Acceptance Payment
PaymentInitialization
Initialization Duplicate
DuplicateCheck
Check Payment
PaymentFinalization
Finalization

Mapping
Mappingand
and Debit
DebitAuthority
Authority Date
DateDetermination
Determination
Assign Weight
Assign Weight

Debit
DebitParty
Party Credit
Auto CreditBank
Bank//Client
Client Credit
CreditBank
Bank
AutoRepair
Repair Determination
Determination Conditions
Conditions Conditions
Conditions

Debit
DebitBank
Bank Credit
CreditParty
Party
STP Validate
ValidateCredit
CreditParty
STPFlow Conditions Determination Party
Flow Conditions Determination

YES Future
FutureRED
RED YES
Payment
Payment
Filtering
Filtering Warehouse
Warehouse
or
orRCVD?
RCVD? Incoming
Incoming NO Routing
RoutingAnd
And
NO or
orBook?
Book? Settlement
Settlement

Payment Future Due Balance

BalanceCheck
Check
Payment Future Due
Warehouse YES Date Debit
Warehouse Date DebitClient
Client
NO Conditions
Conditions
Direction
Direction
Determination
Determination
Fee
Fee

Product
Product
Posting Determination
Determination
Posting

Output Future Send

Output Future Send
Warehouse YES Date Processed Component Processing Component
Warehouse Date
NO

Payment
PaymentGeneration
Generation
Concept of Message Acceptance and Mapping 35

35
 TPS Message Process

Other Channels

Messaging Channels

TPS

Messaging process consists of below stages:

 RECEIVED: Original Message is received
 ACCEPTED: Post successful validation of received message
 MAPPED: Transformed into TPS and status assigned for payment transaction process
Concept of Message Acceptance and Mapping 36

 Message Received, Accepted and Mapped

36
Configuration of Message Acceptance and Mapping 37

 Message Acceptance37

PPT.MSGFORMAT

PPT.MSGFORMATPERCHANNEL

PPT.MESSAGEACCEPTANCEPARAM
Configuration of Message Acceptance and Mapping 38

 Message Mapping
38

PPT.MSGPAYMENTTYPE

PP.MSGPAYMENTTYPECHANNEL

PPT.MESSAGEMAPPINGPARAMETER
Assign Weight for the Payment 39

39

Swift Channel 1 . Heavy

Weight

SEPA Target

Weight
assignment

Clearing Channel 2. Medium Weight

Local Clearing

Other Channel ( Corporate )

3. Light Weight
 Assign Weight for the Payment 40

40
PPL.SPECIFICWEIGHT

High Level
Company ID Originating Source Message Type Rank Specific Weight Weight

MF1 * * 3 P2 H

MF1 SWIFT 103 1 P1 H

MF1 SWIFT * 2 P3 H
Skip Programs based on weight 41

41
 Weight to skip redundant process

PPT.PROGRAMSPERWEIGHT
Code Words 42

42
Code Words – Processing Sequence 43

43
Processing Sequence – Additional Information 44

44
Processing Information Code and Code
Result of Processing Sequence API Fags/Code Words that will be set
Sequence Words
Assign Requested Credit Value Date
1 OTHR/BBDD  
equal to Requested Execution Date
• Set Credit value Date Imposed
Flag 
Assign Requested Credit Value date =
Credit Value date in the message for • Set the Skip Balance Check flag 
INSBNK (In tag 23E) Cddmmyy and impose the same for
processing • Set the SkipBoundaryCheck flag 
2
OTHR/NBALANCE/Dddmmyy
and /or /Cddmmyy Assign Debit Value date = Debit value • Set the value of the Skip Fee flag
date in the message for Dddmmyy and to ‘A’ (Skip All charges)  
impose the same for processing
• Set the value of the Debit Authority
Indicator field to ‘S’ 
• Set Credit value Date Imposed
Flag 
• Set the Skip Balance Check flag 
INSSDR (In tag 72) • Set the SkipBoundaryCheck flag 
3
Debit Value Date = Requested Credit
value Date in the message • Set the value of the Skip Fee flag
REC/NBALANCE
to ‘A’ (Skip All charges)  

• Set the value of the Debit Authority

Indicator field to ‘S’
Set RED to RCVD if RED is in future and
6 INSBNK (In tag 23E)
make RED as blank.
SLA Determination 45

 SLA Determination 45
Debit Authority
46

Acceptance
Acceptance Payment
PaymentInitialization
Initialization Duplicate
DuplicateCheck
Check Payment
PaymentFinalization
Finalization

Mapping
Mappingand
and Debit
DebitAuthority
Authority Date
DateDetermination
Determination
Assign Weight
Assign Weight

Debit
DebitParty
Party Credit
Auto CreditBank
Bank//Client
Client Credit
CreditBank
Bank
AutoRepair
Repair Determination
Determination Conditions
Conditions Conditions
Conditions

Debit
DebitBank
Bank Credit
CreditParty
Party
STP Validate
ValidateCredit
CreditParty
STPFlow Conditions Determination Party
Flow Conditions Determination

YES Future
FutureRED
RED YES
Payment
Payment
Filtering
Filtering Warehouse
Warehouse
or
orRCVD?
RCVD? Incoming
Incoming NO Routing
RoutingAnd
And
NO or
orBook?
Book? Settlement
Settlement

Payment Future Due Balance

BalanceCheck
Check
Payment Future Due
Warehouse YES Date Debit
Warehouse Date DebitClient
Client
NO Conditions
Conditions
Direction
Direction
Determination
Determination
Fee
Fee

Product
Product
Posting Determination
Determination
Posting

Output Future Send

Output Future Send
Warehouse YES Date Processed Component Processing Component
Warehouse Date
NO

Payment
PaymentGeneration
Generation
Debit Authority 47

 Debit Authority Configurations47

Debit Party Determination
48

Acceptance
Acceptance Payment
PaymentInitialization
Initialization Duplicate
DuplicateCheck
Check Payment
PaymentFinalization
Finalization

Mapping
Mappingand
and Debit
DebitAuthority
Authority Date
DateDetermination
Determination
Assign Weight
Assign Weight

Debit
DebitParty
Party Credit
Auto CreditBank
Bank//Client
Client Credit
CreditBank
Bank
AutoRepair
Repair Determination
Determination Conditions
Conditions Conditions
Conditions

Debit
DebitBank
Bank Credit
CreditParty
Party
STP Validate
ValidateCredit
CreditParty
STPFlow Conditions Determination Party
Flow Conditions Determination

YES Future
FutureRED
RED YES
Payment
Payment
Filtering
Filtering Warehouse
Warehouse
or
orRCVD?
RCVD? Incoming
Incoming NO Routing
RoutingAnd
And
NO or
orBook?
Book? Settlement
Settlement

Payment Future Due Balance

BalanceCheck
Check
Payment Future Due
Warehouse YES Date Debit
Warehouse Date DebitClient
Client
NO Conditions
Conditions
Direction
Direction
Determination
Determination
Fee
Fee

Product
Product
Posting Determination
Determination
Posting

Output Future Send

Output Future Send
Warehouse YES Date Processed Component Processing Component
Warehouse Date
NO

Payment
PaymentGeneration
Generation
Determining Debit Party 49

49

 Determine the debit party, determine and validate account

 Implied Debit – Validate account

Defining the LORO/NOSTRO Accounts 50

50
Bank Conditions
51

Acceptance
Acceptance Payment
PaymentInitialization
Initialization Duplicate
DuplicateCheck
Check Payment
PaymentFinalization
Finalization

Mapping
Mappingand
and Debit
DebitAuthority
Authority Date
DateDetermination
Determination
Assign Weight
Assign Weight

Debit
DebitParty
Party Credit
Auto CreditBank
Bank//Client
Client Credit
CreditBank
Bank
AutoRepair
Repair Determination
Determination Conditions
Conditions Conditions
Conditions

Debit
DebitBank
Bank Credit
CreditParty
Party
STP Validate
ValidateCredit
CreditParty
STPFlow Conditions Determination Party
Flow Conditions Determination

YES Future
FutureRED
RED YES
Payment
Payment
Filtering
Filtering Warehouse
Warehouse or
orRCVD?
RCVD? Incoming
Incoming NO Routing
RoutingAnd
And
NO or
orBook?
Book? Settlement
Settlement

Payment Future
FutureDue
Due Balance
BalanceCheck
Check
Payment
Warehouse YES Date
Date Debit
Warehouse DebitClient
Client
NO Conditions
Conditions
Direction
Direction
Determination
Determination
Fee
Fee

Product
Product
Posting Determination
Determination
Posting

Output Future
FutureSend
Send
Output
Warehouse
Warehouse YES Date
Date Processed Component Processing Component
NO

Payment
PaymentGeneration
Generation
Bank Conditions
52
Warehouse
53

Acceptance
Acceptance Payment
PaymentInitialization
Initialization Duplicate
DuplicateCheck
Check Payment
PaymentFinalization
Finalization

Mapping
Mappingand
and Debit
DebitAuthority
Authority Date
DateDetermination
Determination
Assign Weight
Assign Weight

Debit
DebitParty
Party Credit
Auto CreditBank
Bank//Client
Client Credit
CreditBank
Bank
AutoRepair
Repair Determination
Determination Conditions
Conditions Conditions
Conditions

Debit
DebitBank
Bank Credit
CreditParty
Party
STP Validate
ValidateCredit
CreditParty
STPFlow Conditions Determination Party
Flow Conditions Determination

YES Future
FutureRED
RED YES
Payment
Payment
Filtering
Filtering Warehouse
Warehouse or
orRCVD?
RCVD? Incoming
Incoming NO Routing
RoutingAnd
And
NO or
orBook?
Book? Settlement
Settlement

Payment Future
FutureDue
Due Balance
BalanceCheck
Check
Payment
Warehouse YES Date
Date Debit
Warehouse DebitClient
Client
NO Conditions
Conditions
Direction
Direction
Determination
Determination
Fee
Fee

Product
Product
Posting Determination
Determination
Posting

Output Future
FutureSend
Send
Output
Warehouse
Warehouse YES Date
Date Processed Component Processing Component
NO

Payment
PaymentGeneration
Generation
 Types of Warehouse 54

54
 Warehouse

 Payment warehouse – When Requested Execution Date or Requested Credit Value Date is
in future, payments are warehoused at the start of STP flow based on Bank Conditions

 Future due date warehouse – When calculated Credit Value date is in future and processing
date is also pushed to future to meet the credit value date

 Send date warehouse – When Send date is in future

Release from Warehouse 55

55

 Moves Payments from Warehouse to STP, Filter and Payment

Generation based on different Payment status

 Triggered during Start of Day (SOD)

 Release from warehouse – Normal and force release

Do we have sufficient balance on the debit account?
56

Acceptance
Acceptance Payment
PaymentInitialization
Initialization Duplicate
DuplicateCheck
Check Payment
PaymentFinalization
Finalization

Mapping
Mappingand
and Debit
DebitAuthority
Authority Date
DateDetermination
Determination
Assign Weight
Assign Weight

Debit
DebitParty
Party Credit
Auto CreditBank
Bank//Client
Client Credit
CreditBank
Bank
AutoRepair
Repair Determination
Determination Conditions
Conditions Conditions
Conditions

Debit
DebitBank
Bank Credit
CreditParty
Party
STP Validate
ValidateCredit
CreditParty
STPFlow Conditions Determination Party
Flow Conditions Determination

YES Future
FutureRED
RED YES
Payment
Payment
Filtering
Filtering Warehouse
Warehouse or
orRCVD?
RCVD? Incoming
Incoming NO Routing
RoutingAnd
And
NO or
orBook?
Book? Settlement
Settlement

Payment Future
FutureDue
Due Balance
BalanceCheck
Check
Payment
Warehouse YES Date
Date Debit
Warehouse DebitClient
Client
NO Conditions
Conditions
Direction
Direction
Determination
Determination
Fee
Fee

Product
Product
Posting Determination
Determination
Posting

Output Future
FutureSend
Send
Output
Warehouse
Warehouse YES Date
Date Processed Component Processing Component
NO

Payment
PaymentGeneration
Generation
Balance Check 57

57
Balance Check process

TPS T24

Balance Check Balance Interface DDA

Tables referred: Tables used:

1. PPT.BALANCECHECKREQUIRED 1. AC.LOCKED.EVENTS

2. AC.FUNDS.AUTHORISATION
2. PPT.MANUALAUTHREQUIRED

3. PPT.REJECTRESPONSEACTION
Balance Check - Configuration 58

58

PPT.BALANCECHECKREQUIRED

PPT.MANUALAUTHREQUIRED
Balance Check - Configuration 59

59
PPT.REJECTRESPONSEACTION
Balance Check Process Flow 60

Check Account 60
status and
restriction

Check if Balance Check is Continue with

PPT.BALANCECHECKREQUIRED
required? Payment processing

Required

PPT.MANUALAUTHREQUIRED Manual Auth required?

Y/N

Send Request to DDA

along with Manual Auth
required flag

Reserve Balance
Flow Within DDA
(ACLK) and send Balance
Yes (Working Balance – Locked Amount + Limits)
Success response to Available?
TPS

No

Park Payment
Manual Funds Manual Auth
Yes
Authorisation queue Required
(ACFA)

No

Authorise
Send Rejected
Overdraft No
resp onse to TPS
request?

Yes
Reserve Balance
(ACLK) and Send
‘Approved’ response
to TPS

RejectResponse
Can cel PPT.REJECTRESPONSEACTION
Action is R or C?

Repair

Park payment in
Cancel Payment and
Repair queue i.e.
set status to 997
status 235
Determine direction of payment
61

Acceptance
Acceptance Payment
PaymentInitialization
Initialization Duplicate
DuplicateCheck
Check Payment
PaymentFinalization
Finalization

Mapping
Mappingand
and Debit
DebitAuthority
Authority Date
DateDetermination
Determination
Assign Weight
Assign Weight

Debit
DebitParty
Party Credit
Auto CreditBank
Bank//Client
Client Credit
CreditBank
Bank
AutoRepair
Repair Determination
Determination Conditions
Conditions Conditions
Conditions

Debit
DebitBank
Bank Credit
CreditParty
Party
STP Validate
ValidateCredit
CreditParty
STPFlow Conditions Determination Party
Flow Conditions Determination

YES Future
FutureRED
RED YES
Payment
Payment
Filtering
Filtering Warehouse
Warehouse or
orRCVD?
RCVD? Incoming
Incoming NO Routing
RoutingAnd
And
NO or
orBook?
Book? Settlement
Settlement

Payment Future
FutureDue
Due Balance
BalanceCheck
Check
Payment
Warehouse YES Date
Date Debit
Warehouse DebitClient
Client
NO Conditions
Conditions
Direction
Direction
Determination
Determination
Fee
Fee

Product
Product
Posting Determination
Determination
Posting

Output Future
FutureSend
Send
Output
Warehouse
Warehouse YES Date
Date Processed Component Processing Component
NO

Payment
PaymentGeneration
Generation
Direction Determination 62

62
 Direction

# Debit account Credit Account (Ultimate Direction

(Remitter is in own Beneficiary is in own
ledger) ledger)
1 Yes No Outgoing
2 No No Redirect

3 Yes Yes Book

4  No Yes Incoming

Bank or Client(Customer) Transfer 63

63
Bank Or Client Transfer

Message Type Transfer Type Description

MT101 C Originating party is a customer

MT103 C Originating party is a customer

MT202 B Originating party is a bank and beneficiary party is a

bank

MT202COV B Originating party is a bank and beneficiary party is a

bank

STO C Originating party is a customer

Batch – Parent** C Originating party is a customer

Batch – Child** C Originating party of the parent is a customer

Clearing settlement (Incoming/Outgoing)** C Underlying transactions are customer transfers

Clearing transactions (incoming/outgoing)** C Beneficiary party is a customer

Claim** C Ultimately it is the Customer who bears the charges of

the claim

Order Entry payments/Repair * B or C  

Product Determination
64

Acceptance
Acceptance Payment
PaymentInitialization
Initialization Duplicate
DuplicateCheck
Check Payment
PaymentFinalization
Finalization

Mapping
Mappingand
and Debit
DebitAuthority
Authority Date
DateDetermination
Determination
Assign Weight
Assign Weight

Debit
DebitParty
Party Credit
Auto CreditBank
Bank//Client
Client Credit
CreditBank
Bank
AutoRepair
Repair Determination
Determination Conditions
Conditions Conditions
Conditions

Debit
DebitBank
Bank Credit
CreditParty
Party
STP Validate
ValidateCredit
CreditParty
STPFlow Conditions Determination Party
Flow Conditions Determination

YES Future
FutureRED
RED YES
Payment
Payment
Filtering
Filtering Warehouse
Warehouse or
orRCVD?
RCVD? Incoming
Incoming NO Routing
RoutingAnd
And
NO or
orBook?
Book? Settlement
Settlement

Payment Future
FutureDue
Due Balance
BalanceCheck
Check
Payment
Warehouse YES Date
Date Debit
Warehouse DebitClient
Client
NO Conditions
Conditions
Direction
Direction
Determination
Determination
Fee
Fee

Product
Product
Posting Determination
Determination
Posting

Output Future
FutureSend
Send
Output
Warehouse
Warehouse YES Date
Date Processed Component Processing Component
NO

Payment
PaymentGeneration
Generation
Product Determination 65

65

Product Determination

Heavy Weight Medium Weight Light Weight

Usually used for Usually used for Local

SEPA
International Payments Clearing Payments
Product Determination 66

 Heavy Weight Product 66

 What Did We Learn? 67

67
Conclusion

Overviewof payment processing in

Payment Hub
Static
configurations used in Payment
processing
Process Incoming MT103 till product
determination component
Thank You 68

68

For training Enquiries

[email protected]

www.temenos.com