Scribd
Upload
62 views

T24 Interview

The document outlines the integration and processing flow for various financial transactions, including the use of XSLT for message delivery and transformation, as well as the configuration of parameters for payment processing and API interactions. It details the handling of different payment types, such as pacs and pain messages, and describes the setup for API development using Maven and Postman. Additionally, it covers the necessary configurations for logging, duplicate checks, and transaction conditions to ensure smooth operation within the financial system.

Uploaded by

ameybfinance
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
62 views

T24 Interview

The document outlines the integration and processing flow for various financial transactions, including the use of XSLT for message delivery and transformation, as well as the configuration of parameters for payment processing and API interactions. It details the handling of different payment types, such as pacs and pain messages, and describes the setup for API development using Maven and Postman. Additionally, it covers the necessary configurations for logging, duplicate checks, and transaction conditions to ensure smooth operation within the financial system.

Uploaded by

ameybfinance
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

DEInwardInteg -> delivery XSLT -> Camel layer ( It will split the message and apply

the delivery XSLT and DE.I,HEADER request to transact and if not issues it will
pass to the TPH)-> PPSWIFTInwardXml transform the file and push it to TPH ->
PP.MSG.ACCEPTANCE.PARAM -> PP.MESGMAPPINGPARAMETER ( Enrigh API ->
updatePaymentObject) -> POR.TRANSACTION (Details of transaction)/
POR.SUPPLEMENTARYINFO (account and customer Details) -> It will pass to Delivery
*PPT.RECEIVED.FILE.DETAILS -> To check all incoming messages - status hould be
mapped
* PP.COMPANY.PROPERTIES - > to enable the MX Date swiftMX EffectiveData
* PP.HEAVEYWeightProductCondition (based on input, output will decide) -> Non-STP
Indicator set to Y ( It will go to repair)
* LORO.NOSTRO.ACCOUNT -> All configuration for swift and settlement account based
on external account maintained
* PP.RMA -> Relationship mutual agrement -> to configure which all payment we can
send to the other bank

* FT.APPL.DEFAULT - This application allows the user to define application-level


default values, which is used when processing FUNDS.TRANSFER or STANDING.ORDER
instructions. These values will be applicable irrespective of the transaction type,
and the user must create one record for each COMPANY (that is, in case of multi-
company setup) on the system.
* FT.TXN.TYPE.CONDITION - aThis application allows the user to define the default
conditions for each transaction type, which can be processed by the FUNDS.TRANSFER
and STANDING.ORDER applications. User can define Transaction Code Credit,
Transaction Code Debit, Comm Types, Charge Types, Forw Value Max and Back Value Max
for each transaction type.
* FT.COMMISSION.TYPE - commission types are applicable for each transaction type.
These commission types should be defined
* FT.CHARGE.TYPE - The default charge types applicable for each transaction type.
These charge types must have been previously created
* EB.DUPLICATE.TYPE - This application allows the user to define selected fields to
check for any duplicate contracts for the given application.
* AC.EXPECTED.RECS - Inward by Telex (IT) types of funds transfer , receipt of
funds record can be generated in the AC.EXPECTED.RECS
Ordering Bank
IN Account With Bank
Beneficiary Bank
Receiver's Correspondent (Tag 54)
Intermediary Institution (Tag 56)
* PD.PAYMENT.DUE -which contains all payments which have fallen due and not yet
been fully repaid.
* PD.PARAMETER -

* To enable TPS logs -> TPS.INTERNAL.CONFIGS - TPS logs


* To trigger any L3 API at a specific TPH payment status -> PP.STATUS.ACTION
* DE.CARRIER - > we will define all the MX mssage types and Delivery configuration
eg. CBPRPLUS and add carrier in DE.PRODUCT
* DE.MESSAGE.HEADER -> technical header definition ( XMLV2 and BAH)
* DE.BUSINESS.SERVICE.RULES -> subtype can contain PCS.008. -> STP/COVER
* DE.MESSAGE -> CAMT052 and CAMT053
* Technical Ack/Nack required is configured in DE.INTERFACE -> SWIFTXMLINT
*DE.FORMAT
* DE.MAPPING - Extends Delivey - method List<Field>
MapAdditionalDataToMessageType() -
* DE.FORMAT.SWIFT - For conversion rtn - updateSwiftMessage
* DE.HANDOFF.DETS
* DE.DLN.REQUIREMENTS
* DE.INTERFACE - Technical Ack/Nack required is configured in DE.INTERFACE
T24 event wizard in ds and define the event (type of like TS r
* IF.INTEGRATION.SERVICE.PARAM - EVENT TYPE(project name and flow name) , event
destination (queues)
* IF.FLOW.OVERRIDE
* IF.EVENTS.INTERFACE.TABLE
* IF.EXIT.EVENT.FILTER - You can set up the condition on which the event will be
triggered by setting up the required conditions for the flow
If no definition is available for the flow in the IF.EXIT.EVENT.FILTER table,
the event will be stored in the events table as usual.
Java -
ServiceLifeCycle ->
getIds() -> This interface enables the implementer to return a list of Ids to the
process, the RECORD routine (process/inputRecord) will then be invoked on all the
ids in the list.
updateRecord() This interface enables the developer to update the records of any
table.
process() -> Define a method to process a single record from the table specified by
getTableName
processSingleThreaded() -. This interface enables the implementer to define tasks
to be executed during the running of services eg during end of day processing.
Enquiry
setValues() -> This interface enables the implementer to set the value of an
element displayed in the enquiry results programatically to a list of values.
setValue() -> This interface enables the implementer to set the value of an element
displayed in the enquiry results programatically.
Nofile -
setIds() -> This interface enables the implementer to define the list of record Ids
that the enquiry will process.
setRecord() -> This interface enables the implementer to set the entire contents of
a record prior to it being processed by the enquiry engine.

Payments (pacs.XXX)
pacs.008 (FI to FI Customer Credit Transfer): Facilitates credit transfers between
financial institutions on behalf of customers.
pacs.009 (FI to FI Institution Credit Transfer): Handles high-value or time-
critical credit transfers between financial institutions.
pacs.004 (Payment Return): Used to return a payment that could not be processed
successfully.

Payment Initiation (pain.XXX)


pain.001 (Customer Credit Transfer Initiation): Initiates a payment instruction
from a customer to its financial institution.
pain.002 (Payment Status Report): Provides status updates on previously sent
payment instructions.
pain.007 (Customer Payment Reversal): Requests the reversal of a previously
processed payment.

Cash Management (camt.XXX)


camt.052 (Bank to Customer Account Report): Provides account activity details for a
specific period.
camt.053 (Bank to Customer Statement): Sends a detailed statement of account
balances and transactions.
camt.054 (Bank to Customer Debit/Credit Notification): Informs customers of account
debit or credit transactions.

API - using post man -> param,authorization,Header ( you can uncheck unnecessary
tags), Body, Pre - request Script , Tests and seettings
getAccountBalances
TABLE, XX.API.VERB.RESOURCEID.Major.Minor.Patch Eg. ST.API.CUSTOMERS.1.0.0
AC.API.ACCOUNTS.TRANSACTIONS.1.0.0
In version also you can add as hyperlink
If want to add data in body - DISPLAY.BREAK to ONCE
1. Browse for archetype-catalog.xml file in the location where irf-m2repo.zip
folder is extracted.
1. Need to create 2 maven project 1 service container (irf-service-container-
archetype - Enter Group Id and Artifact Id)
after creating project start the server Run As > Maven Build. in goal mention
jetty:run
Maven > Install to build the project
2. Create a service project (irf-service-archetype Enter Enter Group
Id(com.temenos.test) and Artifact Id (eg. test-api) and veersion )
3. Workbench to define a Provider API
Jboss - http://localhost:9089/irf-test-web/api/v1.0.0/meta/apis
4.In Interaction Framework Workbench, click APIs > Create Provider API ,
Use POST to create new resources.
Use PUT to amend an existing resource.
Use GET to view a resource.
Use DELETE to remove a resource.
5. Map URL parameters to the query selection (transact versionn or enquiry)
6. Click Finish to create a zip file containing the Swagger specification, Camel
routes, mappings and mock responses.
api-docs - This folder contains swagger which will show the specification of our
API ,
7. after adding logic download the artifact
inventory - This folder contains details of the generated artefacts/APIs. Which is
useful to load existing APIs to the workbench
rather than selecting artefacts from scratch.
Services- This folder contains the xml routes for routing the API to appropriate
transact artefact.
This file alone is fine to deploy in a container to get our API work.,
7. Import the generated artefacts: Extract the contents of the downloaded zip file
into the service-provider-project/resources folder.
8. Maven install serive project
9. To add API to the service container project,
In your service container project, edit pom.xml.
In the MAIN dependency (Group Id(com.temenos.test) and Artifact Id (eg. test-api)
and veersion) add your API as a dependency below the comment <!-- Add any project
dependencies here-->.
10. Use Postman or any REST client application to make a GET request to the
management service.
localhost:8080/api/v1.0.0/meta/apis it should return a response

You might also like