KDPW provides access to the test environments, both in the U2A model and the A2A model. Access to the test environments for participants, entities seeking participation and IT vendors is free of charge.
The test environment is an environment which mirrors the current version of the KDPW system, made available for the purpose of software compatibility testing, or an additional environment for the testing of new functionalities developed by KDPW or new versions of functionalities available in the system. The application test environment does not have to be fully compatible with the production environment currently provided by KDPW.
KDPW does not ensure that changes are made to adapt the test environment to the specific requirements of participants or non-participants.
Access to the test environments provides support for KDPW services by allowing users to understand and adapt to the technical and organisational requirements associated with participation in these services.
KDPW does not provide 24/7 access to the test environments and may impose technical interruptions in access to the test environments.
An entity which is a participant in a KDPW service gets access to the test environment of that service based on the institution code issued to it as part of its participation. An entity which is not a participant in a KDPW service should get an institution code in accordance with the procedure described below in order to access the test environment.
Two types of test environment are offered:
- The EDU environment is an educational test environment where participants can test KDPW services in a version compatible with the status of the production environment. By definition, this environment is educational in nature and is made available to participants and software developers of participants of KDPW services in order to test the compatibility of their own software with the software provided operationally by KDPW.
- The TST environment is a test environment designed to conduct tests of new services and new or modified features of services released in production. This environment is used by KDPW for in-house testing and testing with participants as part of development work. The TST environment is also available to entities developing software for participants in KDPW services.
Access to test environments for KDPW participants
KDPW participants are provided with access to the test environments of KDPW systems under their participation agreements.
The rules for accessing and handling communications in the test environments are the same as those in place in the production environment.
Access includes both the U2A and A2A interfaces.
In the case of the U2A interface, after obtaining the KDPW participant status, it is possible to submit access requests to the test environments of the applications provided in the Service Portal using the same attributes (institution code, LEI) that are required in the production environment.
Each environment has its own dedicated access point:
each of which is accessed using a single access account.
The test environments are independent, which means that separate authorisation is required for each environment.
In A2A communication, the participant can access both the production and the test environments (TST, EDU).
Communication with the test environments of KDPW services in the A2A model takes place via test communication channels, independent for the TST and EDU test environments.
Authentication to communication channels is based on test electronic certificates, where a test certificate issued to an institution code allows the participant to establish access to both test environments.
Test certificates are issued using the production application A2A Certificates (TST and EDU test environments are not available for this application). The application allows to download certificates for the production and test environments.
The rules for accessing and handling communications in the test environments are the same as those in place in the production environment.
Access includes both the U2A and A2A interfaces.
In the case of the U2A interface, after obtaining the KDPW participant status, it is possible to submit access requests to the test environments of the applications provided in the Service Portal using the same attributes (institution code, LEI) that are required in the production environment.
Each environment has its own dedicated access point:
each of which is accessed using a single access account.
The test environments are independent, which means that separate authorisation is required for each environment.
In A2A communication, the participant can access both the production and the test environments (TST, EDU).
Communication with the test environments of KDPW services in the A2A model takes place via test communication channels, independent for the TST and EDU test environments.
Authentication to communication channels is based on test electronic certificates, where a test certificate issued to an institution code allows the participant to establish access to both test environments.
Test certificates are issued using the production application A2A Certificates (TST and EDU test environments are not available for this application). The application allows to download certificates for the production and test environments.
Access to test environments for entities that are not KDPW participants
Non-participants (entities seeking participation or participants’ IT vendors) may access the KDPW test environments as described below.
How to get access?
Step 1: Access request for test environments
To get access to the test environments of KDPW systems, the entity seeking access should submit a request in accordance with the KDPW template.
The request is made once, irrespective of how many services the entity intends to access. The request provides the basis for access of the entity to the test environments of the various services, in particular to issuing institution codes under which the entity will be identified in the services.
Step 2: Acceptance of the request by KDPW
Information on the acceptance of the request by KDPW will be sent to the entity's email address provided in the request.
KDPW may refuse access without giving any reason.
Step 3: Getting the institution code
If the request is accepted by KDPW, the entity may request KDPW to issue the institution code(s) under which communication with the KDPW systems will be established.
The code is issued in the context of the particular business service for which the entity intends to conduct testing and the type of activity which the entity will be performing. For this purpose, the entity should contact the KDPW organisational unit responsible for the service.
Step 4: Establishing a connection in a communication interface (U2A and/or A2A)
After getting the institution code, the entity can get access to individual services.
In the case of the U2A interface, it is possible to submit access requests to web applications in the Service Portal using the access account. The person requesting access in the role of user should have the authorisation of the entity on whose behalf he/she is requesting to communicate directly with KDPW. When requesting access in the role of administrator (permission administrator or service administrator), the person should have the authorisation to grant other persons access to the application and to withdraw such access.
When using access via the A2A interface, it is necessary to establish network connections (according to the rules for establishing access for the A2A interface) and to get an electronic certificate used to secure the transmission and authenticate to the dedicated communication channel. In this case, it is necessary to access the A2A Certificates application in the production environment of the Service Portal https://online.kdpw.pl and to download the electronic certificate to the test environments in the application.
How to get access?
Step 1: Access request for test environments
To get access to the test environments of KDPW systems, the entity seeking access should submit a request in accordance with the KDPW template.
The request is made once, irrespective of how many services the entity intends to access. The request provides the basis for access of the entity to the test environments of the various services, in particular to issuing institution codes under which the entity will be identified in the services.
Step 2: Acceptance of the request by KDPW
Information on the acceptance of the request by KDPW will be sent to the entity's email address provided in the request.
KDPW may refuse access without giving any reason.
Step 3: Getting the institution code
If the request is accepted by KDPW, the entity may request KDPW to issue the institution code(s) under which communication with the KDPW systems will be established.
The code is issued in the context of the particular business service for which the entity intends to conduct testing and the type of activity which the entity will be performing. For this purpose, the entity should contact the KDPW organisational unit responsible for the service.
Step 4: Establishing a connection in a communication interface (U2A and/or A2A)
After getting the institution code, the entity can get access to individual services.
In the case of the U2A interface, it is possible to submit access requests to web applications in the Service Portal using the access account. The person requesting access in the role of user should have the authorisation of the entity on whose behalf he/she is requesting to communicate directly with KDPW. When requesting access in the role of administrator (permission administrator or service administrator), the person should have the authorisation to grant other persons access to the application and to withdraw such access.
When using access via the A2A interface, it is necessary to establish network connections (according to the rules for establishing access for the A2A interface) and to get an electronic certificate used to secure the transmission and authenticate to the dedicated communication channel. In this case, it is necessary to access the A2A Certificates application in the production environment of the Service Portal https://online.kdpw.pl and to download the electronic certificate to the test environments in the application.
kdpw_stream test environment
Rules for feeding data to the EDU test environment
In order to conduct tests of monthly reporting on Treasury bonds (processing of semt.tr1 and semt.tr2 messages), the test period (defined as the reporting period) must be agreed with the KDPW Supervision Department well in advance of the tests as the test environment will be prepared to process periods shorter than one month. The solution will make it possible to test this functionality several times within a single month, provided that no days outside the reporting month are included.
Organisation of tests concerning corporate actions and the fulfilment of issuers’ obligations
Tests of corporate actions and the fulfilment of issuers’ obligations towards securities holders are carried out on the basis of the "ONP Test Application Form" , which should be sent to kdpw@kdpw.pl no later than the 5th working day of the month for tests to be carried out in that month. If the form is sent after this date, the test will be carried out in the following month.
ONP Test Application Form
- Databases will be copied from the production environment (PRD) to the test environment (EDU) once a month, as at the last working day of the month.
- Financial instrument databases: production instruments will be copied, instruments that only exist in the test environment will remain unchanged.
- Balances: for production instruments, all production balances will be copied. For test securities, balances (10,000 units each) will be automatically created for all Participants (production and test Participants) in the test database together with the corresponding issue volume in the issue account
- Participant databases: these will be copied in accordance with the rules for copying the financial instrument database. After the copying operation, test Participants will only have balances in test financial instruments, excluding derivatives.
- All settlement instructions not settled by the date of database copying will be cleared in the test environment.
| Settlement session code | Session start time | Types of operations executed in the session |
|---|---|---|
| R | 09:00 | Morning technical session |
| 1 | 12:00 | Payment session – all operations |
| 2 | 14:00 | Payment session – all operations |
| 3 | 16:00 | Payment session – all operations |
| W | 16:15 | Evening technical session |
| RTGS | Types of operations executed |
| 09:00 – 16:00 | All operations |
- Settlement in the real-time gross settlement (RTGS) system is conducted between 09:00 and 16:00.
- The scope of operations executed in the test environment corresponds to the scope specified in Appendix 2 to the Detailed Rules of Operation of KDPW.
- Transactions are settled on the assumption of full cash coverage; standard tests do not envisage the use of a connection with a clearing bank.
In order to conduct tests of monthly reporting on Treasury bonds (processing of semt.tr1 and semt.tr2 messages), the test period (defined as the reporting period) must be agreed with the KDPW Supervision Department well in advance of the tests as the test environment will be prepared to process periods shorter than one month. The solution will make it possible to test this functionality several times within a single month, provided that no days outside the reporting month are included.
Organisation of tests concerning corporate actions and the fulfilment of issuers’ obligations
Tests of corporate actions and the fulfilment of issuers’ obligations towards securities holders are carried out on the basis of the "ONP Test Application Form" , which should be sent to kdpw@kdpw.pl no later than the 5th working day of the month for tests to be carried out in that month. If the form is sent after this date, the test will be carried out in the following month.
ONP Test Application Form