The following diagram shows the core elements of the Merchant Portal architecture, specifically:
- How the Message Mapping feature fits into existing functionality
- How the PPCUST, MRCHTS and MRCHTXN records are populated
The Message Mapping enhances the input messages as they arrive at the IRTXNCOL and IRTSVCOL collectors. There are no required modifications to the standard transaction log readers.
As messages arrive at the collector, the code identifies the transaction source. If rules exist for using Message Mapping to populate a field of the messages from the particular transaction source, then those rules are executed in the order in which they are defined.
The rules define:
- the transaction source;
- the 'method' that will be used to populate the Merchant Name;
- the 'source' field that will be used as the key into the dictionary (MAP method) or ranges (RANGE method);
- the 'destination' field that is populated;
- the name of a file that contains the translation information for the MAP and RANGE methods (the Mappings File).
Once the rules have been applied, the log reader message (now potentially altered) is processed in the same way that previous versions of the collectors processed the message.
The Merchant Portal displays are populated using the data collected from the three following records:
|PaymentsPortalCustomer (PPCUST)||The values in the last column of the Mappings File used by TXNCOL populate the PPCUST record and by extension the available Customer Names for Role Based Security (RBS).|
TXNCOL can be configured to populate the MRCHTS record. See Merchant Portal Configuration
|MerchantTransactionDetail (MRCHTXN)||TSVCOL can be configured to populate the MRCHTXN record. See Merchant Portal Configuration|
Unauthorized access is prevented by utilizing Role Based Security (RBS).