The informational structure of a payment is expandable and may include any additional parameters and classifications necessary for the bank.

The following payment history breakdowns are collected and accumulated in the system:

• Payment events history (status changes, completed acceptances, times of message despatch and receipt, times of transactions and payment status change in registration system)
• Payment documents turnover. Messages exchanged with external systems relating to a specified payment, internal messages by payment (messages about errors, informational and diagnostic messages, operator comments).
• History of transactions in accounting system related to specified payment.

Work by regulations
The business logic for a payment attribute definition as well as its processing algorithms is realized in the form of a flexible decision tree.

The decision tree is simultaneously a business process specification and a performed code of the payment processing program.

Descriptions in the form of decision tree may easy be changed (including by user, if authorised) during system processing.

In order to control the relationship between compliance and business demands, a representative set of tests is prepared and performed.