Batch UML

Entity that represents information about collection of transactions that are processed together. Batch processing is used in two situations:

• Realtime batches - are used for settlements of pre-authorized transactions.
• File batches - are used to process together card not present transactions (authorization and settlement) of recurring nature such as bill payments, subscription payments, etc.

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

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

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

Reference to the entity that represents chargeback case document information.

Reference to the entity that represents credit agency transaction information.

Any additional information for the merchant.

Date on which a transaction is recorded.

Transactions with effective date (trasaction date) in the past as well as in the future can be processed. Any transactions with dates in the past are processed with the effective date of today, while any future dated transactions are processed on the specified effective date in the future. The only limitation is that a single file should not mix transactions with past, current and future effective dates. In other words, all transactions in the file must be either in the past, effective today or effective in the future.

Reference to the entity that represents emails information.

Indicates whether the file notification is enables in the system.

The date when the batch transaction was processed.

Reference to the entity that represents skip tracing transaction information.

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

Reference to the entity that represents subscription transaction information.

Total amount paid for the item (including tax and discount).

Total count of the batch transaction.