Sub Batch UML

Represents a sub-group of transactions within Batch or Retail Cycle.

Sub-batch is maintained for each group of transacions that have their own processing logic. For example, a batch that contains both credit card and ACH transactions will have two sub-batches in it.

Another example is a batch that contains transactions belonging to more than one Merchant Account. In such cases, when processing settings are different for each account, multiple sub-batches are created.

Error transactions are placed in a separate sub-batch. Decline transactions for rebill are placed in a separate sub-batch as well.

Reference to the entity that represents account update batch information.

Reference to the entity that represents account update subscription transaction information.

Reference to the entity that represents account update transaction information.

Reference to the entity that represents aggregate sub-batch file.

Date of approval.

Code of the user that approved the operation.

The date of the first attempted sub-batch operation.

Reference to the entity that represents a group of batch transactions which must be settled together.

Reference to the entity that represents real-time financial transaction.

Reference to the entity that represents chargeback case activity information.

Reference to the entity that represents chargeback case document information.

Reference to the entity that represents collections transactions information.

Reference to the entity that represents credit agency transactions information.

Reference to the entity that represents information about duplicated sub-batch.

Reference to the entity that represents emails information.

Reference to the entity that represents information about batch file.

Indicates whether the sub-batch operation has a decline from the processor.

Reference to the entity that represents information about sub-batch on hold.

Indicates that the database table is blocked.

Indicates whether the response is suppressed.

Represents the type of performed sub-batch operation.

The date when the sub-batch was processed.

Name of the provider associated with this sub-batch file.

The number of the sub-batch operation reccurence times left.

Reference to the entity that represents a group of real-time transactions which must be settled together.

The number of the sub-batch operation reccurence times.

Represents the type of sub-batch operation to be performed after the review.

Reference to the entity that represents skip tracing transaction information.

Indicates current status of the sub-batch operation.

Represents the type of sub-batch operation to be performed.

Represents current type of sub-batch file content.

Type of the sub-batch operation.

Reference to the entity that represents subsciption transaction information.

Total amount of the sub-batch transactions.

Total number of the transactions included in the sub-batch file.