Distribution copy

Distribution copy is when outbound transactions are copied to one or more endpoints. During ingestion, business rules are used to determine which transactions are copied. Endpoints that have copied transactions associated with them are called sidepoints, and the transactions are called sidepoint transactions.

Sidepoint transactions are processed similarly to original transactions. The sidepoint transactions are mapped with other transactions that are associated with the same sidepoint, resulting in a hierarchy of sidepoint transactions, sidepoint batches (ICLs), and sidepoint transmissions.

Sidepoint transmissions are processed similarly to original transmissions. The transmissions are mapped, built, and released according to the configuration for the partner associated with the corresponding sidepoint. Sidepoint transmissions differ from original transmissions as follows:
Remapping
Endpoint remapping is restricted to endpoints that have existing sidepoint mappings or have no mappings. A sidepoint transmission cannot be remapped to an existing endpoint transmission. An endpoint transmission cannot be remapped to an existing sidepoint transmission.
Replica endpoints
Replica endpoints are not created for sidepoint transmissions.
Transmission definition override
Transmission definition overrides assigned to transactions at ingestion override endpoint transmission definitions only. Sidepoint transmissions always use the transmission definition that is assigned to the related endpoint.
Processing windows
Processing windows are not assigned to sidepoint transmissions.

A new distribution type field is used to distinguish between the original and sidepoint transactions, batches (ICLs), and transmissions. Depending on the user preferences for individual pages, the distribution type field is displayed on the user interface for transactions, batches (ICLs), and transmissions. It can also be used as a parameter for an event handler to limit which distribution type causes the handler to run. The distribution type is sidepoint when the transaction, batch (ICL), or transmission is a sidepoint and is endpoint for original transactions, batches (ICLs), and transmissions.

Configuring distribution copy

Distribution copy requires the following configuration and updates:
  • Configure the following, which relate to the sidepoint and to the assignment rules:
    • Endpoints to use as sidepoints
    • Inbound and outbound services
    • Transmission definitions
    • Inbound product subscriptions
    • Endpoint subscription service
  • Define the business rules needed to determine which transactions are copied into sidepoints
  • Review any outbound presentment group state events that are defined in the Scheduler.xml file and add the distribution type parameter if necessary. For example, transactions probably should not be processed twice by components such as Settlement.
The reference implementation supporting the following features provides an example of distribution copy:
  • FTM for Corporate Payment Services
  • FTM Check