Merchant Portal Data Processing

The following illustration depicts a typical deployment of Merchant Portal. Other server topologies are available to meet any specific needs.

When Merchant Portal is active, the data flow throughout the system follows this pattern.

1. TXNCOL receives data from the Transaction Source (eg. BASE24, CONNEX, etc.) and maps it to the MerchantTransactionSummary (MRCHTS) record.
   1. Message Mapping is applied and a Merchant Name is written into the record if possible.
   2. Values for Merchant Name are also collected and mapped to the PaymentsPortalCustomer (PPCUST) record.
2. TSVCOL receives data from the Transaction Source (eg. BASE24, CONNEX, etc.) and maps it to the MerchantTransactionDetail (MRCHTXN) record.
   
   1. Message Mapping is applied and a Merchant Name is written into the record if possible.
3. The Administrator Creates Roles & Users for Role Based Security.
   1. Roles are assigned Customers based on Customer Names from the PPCUST record.
   2. Roles designed to use the Merchant Portal have the Merchant Portal set as their home dashboard.
   3. Users are created and given the correct Role(s).
4. Users log into the Web Application and are directed to the Merchant Portal.
   1. The Merchant Portal display requests MRCHTS & MRCHTXN Records.
   2. Role Based Security filters MRCHTS Records based on the Merchant Name, protecting data from those unauthorized to see it.