On March 12, 2026, CS company organized an online event dedicated to the practical aspects of implementing the TrekSEP module – the NBU’s new service for tracking the status of payment operations – and issues regarding methods for complying with the requirements of NBU Resolutions No. 130 and No. 97. The event gathered representatives from Ukrainian banks preparing for integration with the new system within the deadlines set by the regulator.
It is worth recalling that the main goal of implementing TrekSEP is to provide clients and market participants with a transparent tool for tracking the execution stages of payment operations in the SEP (Electronic Payment System). This involves accomplishing two key tasks:
-
Automatically populating the NBU Tracking database with information on the processing stages of financial transactions.
-
Receiving client inquiries about transaction statuses and providing comprehensive responses with all available statuses.
Technical Implementation from CS: Simplicity, Reliability, and Automation
During the webinar, a ready-made solution for TrekSEP integration based on the B2 ABS (Automated Banking System) – SEP Tracking Service – was reviewed in detail. The main focus was on three key requirements for the process: maximum automation with minimal staff involvement, process transparency, and architectural simplicity that is simultaneously reliable and scalable.
The complete workflow was presented:
-
Populating TrekSEP: It was demonstrated how entities for trck.001 messages are formed based on the functionality for processing business events, and how they are sent to the Central SEP (COSEP).
-
Roles in the System: The roles were clarified, distinguishing between participants (banks, treasury, financial companies) and users (payers, beneficiaries, and other legal entities and individuals possessing payment information) who have the right to send inquiries.
-
Transaction Statuses: A detailed status transition scheme was presented – from acceptance of the payment instruction (ACFC), its sending to COSEP (ACSP), and debiting (ACSC) to crediting the beneficiary’s account (ACCC) or crediting the account for unallocated sums (ACWP). Scenarios for transaction rejection (RJCT) were also discussed separately.
Handling Inquiries and Visualization
A separate part of the presentation was devoted to the format of inquiries to TrekSEP (trck.999), which contains only three mandatory parameters: the transaction’s UETR, the transfer amount, and the desired response format (abbreviated or full). A demonstration was given of how the responses (trck.002) would be visualized for users in the B2ng interface – both in the abbreviated form and in the extended form with the history of all statuses.
Regulatory Requirements: Resolutions No. 130 and No. 97
The event addressed the current requirements of the National Bank of Ukraine. Specifically, the implementation of the requirements of Resolution No. 130 was discussed in detail. According to this resolution, the payer’s bank is obliged to inform the client about the payment’s UETR, the fact of its successful completion, or the reason for its rejection. Explanations were also provided on how this information would be provided for instant payments via Response, and how informing would be organized for regular credit transfers initiated through iFOBS or at a bank branch.
An equally important topic was the implementation of the requirements of Resolution No. 97 concerning the QR code structure. Participants were presented with the detailed composition of the QR code (from the BCD service tag and format version to beneficiary data, amount, payment purpose, and digital signature) and, most importantly, the rules for transferring this data into the pacs.008 message. Special attention was paid to the possibilities of using the “Display” field to transmit additional XML tags, allowing for flexible configuration of the payment instruction.
Practical Outcomes and Next Steps
The online meeting featured lively discussions on practical issues: nuances of processing incoming instant payments, reasons for their rejection, automation of control over the instant payment register status, as well as future challenges such as working with pain.013FD (mass payment requests from the tax authorities) and automation of processing requests regarding seized accounts.
Roman Mayevsky, Head of Technical Support Department:
Having a successful track record of implementing SEP 4.0 and Instant Payments projects, we approached the launch of TrekSEP with a ready-made and clear solution. Our goal is to make the integration process as comfortable as possible for banks by automating the most complex areas and ensuring full compliance with NBU requirements.
Following the event, all participants received presentation materials.
Currently, CS continues to provide individual consultations with banks, helping them formulate a connection strategy for TrekSEP and assess the necessary resources.
Our previous material on CS’s solution for TrekSEP integration is available at the link.
For detailed information about the SEP Tracking Service solution, please contact the CS client department: [email protected]
