v1.7.2 ¶

Creation Date: 16.12.2021

Management Portal ¶

50353 – Making adjustments for those who enter Custom Domain on the Environment Page

Product management, ensuring that these addresses are opened with custom domains when clicking on the links for customers who have entered Custom Domain.

50653 – Necessary improvements for IBAN control in card passes

Depending on the creation of AIS consent, which is in Berlin group standards, the product management requests that the IBAN control, which is also included in the middle, be added to the control currently performed with Masked PAN.

48742 – Preparation of the Custom Domain support page in the Environment field in the Management portal

The product management requests that the Custom Domains field be developed under the Management Portal Environments, Advanced Settings page. Thus, the first part of the infrastructure required for institutions to enter product components with their domains is counted.

56071 – Preparation of Certificate Authority start and promotion selection screens

Product management requests the development of a welcome screen where we can choose which certificate authority we want to define. Thus, customers will have the flexibility to define Konsentus or Mastercard certificate verification, and the product will have the structure to expand in this area.

56079 – Necessary studies for making the definition screens suitable for the new structure

The product management requests that the new structure make the Preta certificate validation screen operational. Thus, tenants who have made this definition before will not have any problems, and the appropriate screen will be prepared for users who will make this definition.

56081 – Development of Mastercard Open Banking Protection Platform definition screens

When MasterCard is selected under the Certificate Authority page, the product management requests the screen given in the mock design below. Thus, different definitions will be made for Konsentus and Mastercard.

UX Studies¶

50387 – UX design of Super Admin-Package definition screen

The product management requests the UX design where the Super Admin user can define the package. Thus, the UX design for the relevant PBI is ready.

50390 – UX design of Super Admin-Package Listing screen

The product management requests the UX design of a screen where the package definitions of the Super Admin user will be listed. Thus, the UX design for the relevant PBI is ready.

50169 – Necessary work for the UX design of the Swagger Editor screen

The product management wants the UX design of the Swagger Editor screen to be remade, taking into account the component capabilities of the UX design. Thus, the product UX quality is increased.

52209 – Refreshing the UX design of the Customer Validation Screen

Product management requests a refresh of the UX design of the Customer validation pages. It is not clear what to do on the current page. This page should be considered in the logic of Social Login, and the Active configuration should be displayed.

52206 – UX design of Environment Advanced Settings Page

The product management requests the necessary UX work to be done to manage the Environment Settings - Show Advanced settings page with a tabular structure.

Renewal UI¶

50170 – Refreshing the Agreement page according to the new UX design

According to the UX design, the product management requests the Agreement page to be refreshed. Thus, progress is achieved in product UX transformation.

50253 – Adapting the Developer Portal Sign-in screen to the new UX design

Product management requests that the Developer Portal sign-in screen be aligned with the new UX design. Thus, the product UX transformation continues in the developer Portal.

50255 – Adapting the Developer Portal Reset Password screen to the new UX design

Product management requests that the Developer Portal Reset Password screen be adapted to the new UX design. Thus, the product UX transformation continues in the developer Portal.

50243 – Developer Portal Landing Page renovations

The product management requests that the product’s developer portal lending page UX conversion be done. In this context, React conversion of HTML codes added to the PBI attachment section is requested for the developer portal lending page. Thus, a critical threshold in the visual transformation of the product is exceeded.

56478 – Adapting the Developer Portal Reset Password screen to the new UX design

The product management requests that the Developer Portal forgot password screen be adapted to the new UX design. Thus, the product UX transformation continues in the developer Portal.

50254 – Adapting the Developer Portal Sign-Up screen to the new UX design

Product management requests that the Developer Portal sign-up screen be aligned with the new UX design. Thus, the product UX transformation continues in the developer Portal.

CBRT Improvements¶

48883 – They carry out the necessary work to write the service layer where the CBRT Payment Consent details are brought

The product management requests that a REST service be written, which brings the payment order consent query with a GET server to be developed. Thus, the necessary work for the standard is completed.

48871 – CBRT Payment Order request Making necessary service improvements to catch error situations

The product management requests the establishment of a mechanism that can validate the Body values sent in the Payment order initiation service in the CBRT standards on the Bank.

48548 – CBRT Updating payment order consent records with a crane job to be developed

Product management should find status “B” records among the registered payment order consent mules and update the status to “S” for those with more than 5 minutes of creation time. Thus, the requirement of TCM standard Page 68 is fulfilled.

49010 – Development of the CBRT Payment Order Consent Display and Approval page

The product management requests the payment order consent display and approval/rejection screen with a page to be created on the Gateway. Thus, the payment order consent request can be approved or rejected.

47563 – Development of CBRT Payment Order validation policy

With a policy to be developed, the product management requests a policy to be written to prevent the payment order from being sent to the bank in case of inconsistency and to change the status of the Consent (consumed) if there is compliance by checking the submission of the payment order and the Consent in the endPoint, which sends the payment orders to the bank with a policy to be developed. Thus, an important step has been taken in the CBRT standards.

48963 – Developing the service layer to meet the CBRT Access Token Request

The product management requests that the necessary work be done to develop the Service and REST layer where the access token request is met. Thus, an issue in TCM standards is resolved.

52442 – Adding the feature of showing the recorded history to the CBRT Payment Order Consent listing screen

The product management requests that a field be added on the Payment order consent screen, where the history of the relevant record can be displayed. Thus, the Bank will be able to see the status of a payment order consent from the beginning.

52441 – Necessary studies for adding history to payment order consent records

The product management requests that the status changes of the Payment order consent initiation records be kept on a separate entity. Thus, the difference in this payment order consent over time can be followed.

49131 – Develop the screen where payment consent sites are listed for the environment opened in CBRT standards.

Product management requests the development of a screen listing payment order consents, as in UK and Berlin group standards. Thus, the institution can see the payment consents on the system and follow the details.