Test Data
Change log
2022/03/17: Updated post-NiFi test files to include changes made in https://frmscoe.atlassian.net/browse/AM-842 and https://frmscoe.atlassian.net/browse/AM-860
Transformations
Each ISO 20022 transaction message that is ingested into Actio flows through the following processes/processors which each may introduce some transformation to the messages:
Process/Processor | Transformation |
|---|---|
TMS API | None |
NiFi (Data Preparation) | Pseudonymisation of Account Information |
CRSP | None |
Rule Processors | None |
Typology Processor | None |
CADProc | None |
TADProc | None |
Message flow
Each message relates to a specific Mojaloop process, as follows:
POST /QUOTES (a Mojaloop request for a quote) translates to pain.001 (payment initiation)
PUT / QUOTES (a Mojaloop quote response) translates to pain.013
POST /TRANSFERS (a Mojaloop request for transfer) translates to pacs.008 (payment settlement)
PUT /TRANSFERS (a Mojaloop transfer response) translates to pacs.002
There is a natural relationship between all of the messages and Actio expects that the relationship between the final versions of messages is maintained through a common transferID (Mojaloop) and EndtoEndIf (ISO 20022). Equivalent ISO 20022 messages can be linked through the following fields in each message:
pain.001: CstmrCdtTrfInitn.PmtInf.CdtTrfTxInf.PmtId.EndToEndId
pain.013: CdtrPmtActvtnReq.PmtInf.CdtTrfTxInf.PmtId.EndToEndId
pacs.008: FIToFICstmrCdt.CdtTrfTxInf.PmtId.EndToEndId
pacs.002: FIToFIPmtSts.TxInfAndSts.OrgnlEndToEndId
Evaluation Focus
The Actio platform will ingest each of the ISO 20022 messages translated from the 4 messages originating from the Mojaloop platform, but not every message will be evaluated for financial crime. Unless the intention is to interdict (block) a transaction, it is only neccesary to evaluate the final step in the transaction process, denoted by the pacs.002 message. The other messages are retained as transaction history, since they all contain slightly different information, but only pacs.002 triggers an evaluation beyond the CRSP.
Notable Deviations from the ISO specification
The Mojaloop and ISO specifications conflict in the following specific and significant ways:
Message identifiers
Mojaloop messages are presented with UUIDv4 identifiers which, along with their dashes, encompass 36 characters. The ISO 20022 message standard restricts identifiers to a field length of only 25 characters, creating a shortfall of one character in the translation from Mojaloop to ISO 20022. We have elected to retain the Mojaloop format for the ingestion of the messages to maintain continuity with the Mojaloop platform without additional transformation and the validation of this information in the TMS API has been updated accordingly.
Pseudonymisation
The pseudonymisation of account information results in a pseudonym with a length of 64 characters which far exceeds the available space for an identifier in the ISO 20022 standard of 35 characters. For the purpose of pseudonymisation, we are allowing a value of 64 characters in the identifier fields.
The field where the pseudonymised is stored is not validated inside the Actio platform and is not expected to raise an error, but this message will no longer be ISO 20022 compliant after pseudonymisation and a system that strictly enforces the standard will not accept the pseudonymised message.
Test data samples
The following files can be used as JSON test samples for specific processes:
Processes/Processors | Message | Sample file |
|---|
Processes/Processors | Message | Sample file |
|---|---|---|
TMS API (In/Out) NiFi (In) | pain.001 |
|
pain.013 |
| |
pacs.008 |
| |
pacs.002 |
| |
NiFi (Out) CRSP (In/Out) Rule Processors (In/Out) Typology Processor (In/Out) CADProc (In/Out) TADProc (In/Out) | pain.001 | Prior to entity resolution implementation: 
After entity resolution implementation (Debtor): 
After entity resolution (Debtor and Creditor):
|
pain.013 |
| |
pacs.008 |
| |
pacs.002 |
|
Source:
Bulk test data
