Payment Validation Rule Nodes

Payment validation rule nodes are a set of nodes that together build a payment validation workflow. Each payment validation rule node uses a combination of one or two tables to support its functionality.
  • Routing transit
  • Account
  • Process control
  • AuxOnUs
  • Amount
  • Field4Node
  • ExtProcCodeNode
  • Endorse
  • Pocket map
  • Record ID validation – this is not a node but is a common operation
All payment validation rule nodes perform a lookup on its primary table. For example, the RTNode does its lookup in the routing transit table, the account node in the account table, and so forth. Several nodes do a subsequent lookup in the record ID validation table. These nodes are:
  • Routing transit
  • Account
  • Process control
  • Auxiliary on us
  • Amount
  • Field 4
  • Extended process control

The record ID validation table lookup is performed when the record ID is changed following the primary lookup.

Not all fields are required in the tables. Payload fields that begin with ibmNpr and ibmInt can be set with a specific value that causes the field to be skipped (not transferred to the decision request record) when a successful lookup has occurred. Character type fields set to all spaces or empty and byte type fields set to ‘-1’ (or more specifically, all X'FF's) are ignored.

A user exit is available (but not required) for dynamic redirection of the workflow and modification of data fields. The routine called is buildClientResponse. The parameters passed to this function are:
  • DecisionRequest
  • NodeResponse
  • Exception

User exits are available for each node. The preProcess routine is called prior to the primary table lookup and the buildClientResponse routine is called after the lookup.

Each node is described in detail in the following sections:
Table Record Layout
Defines the fields that are in the table. Additional fields can be added, but these fields must be present.
Fields That Can Change
Identify fields in addition to the table payload fields that the node may modify in its execution.
Results
Shows how the node responds to the workflow controller. These directly correspond to the results= XML setting of the workflow connection.
Initialize and Process
These sections describe the steps taken by the node when the client application issues the initialize and decision messages, respectively. In most cases, no special steps are performed during the initialize.