As domestic markets increasingly adopt ISO20022 standard, Financial Institutions are challenged to ensure integration of these new maps in their validation architecture. In this context, our customers are asking to incude support for SORBNET (Nati...
Include TAIWAN FISC RTGS maps in FinPay PLUS package
As domestic markets increasingly adopt ISO20022 standard, Financial Institutions are challenged to ensure integration of these new maps in their validation architecture. In this context, our customers are asking to incude support for TAIWAN FISC R...
Support Open API 3.0 specifications int he OpenAPI typetree importer
As of now the OpenAPI importer only support swagger 2.0 json format. However, as the OpenApi V3 in json/yaml become more and more common it would be very usefull for ITX to support it.
data anonymization/masking (typetree attribute + test mode)
There are 2 requirements that lead to this idea:
1.) external requirements like GDPR force us to anonymize/pseudonymize data in non-production environments2.) A-B-testing would be much easier if we can mask dynamic attributes (e.g. timestamps)
Thi...
You can build one TypeTree or one strucutre and can use it for example as part of choice-group in another TypeTree. Everybody that use TypeTree as a kind of central unit and have to reuse these structures in other interfaces will benefit.
include support for Hong Kong Interbank Clearing - CHATS - in the FinPay PLUS Package
Financial institutions are challenged to ensure validation of an evolving SWIFT rules. In this context, our customers are asking to incude support for CHATS in FinPay PLUS package
include support for the SWISS Interbank Clearing - EUROSIC in the FinPay PLUS Package
Financial institutions are challenged to ensure validation of an evolving SWIFT rules. In this context, our customers are asking to incude support for euroSIC standard in FinPay PLUS package
ITX - Extend validation exception handling for messages with a known structure BUT an unknown (as more recent) version
Currently ITX FinPay routing map identifies a messages based on the tag <FIToFICstmrCdtTrf> in Document and not based on message name and its version (pacs.008.001.08). This causes a problem when a message based on a more recent version is r...
Currently the SERIESTOTEXT function does not distinguish the type of an object when the same field from the type tree is passed at different level. To make things clear, below is an example of a typical ANSI X12 type tree and the 'X12 Segment' is ...
Expanding the map name field will help us us maintain standard Map naming convention with proper description of the map function and the associated standards. The current limitation of 32 bytes is not sufficient. Other mapping tools like Sterling ...