v1.8.5

Creation Date: 22.02.2023

Payment Order Transactions

95647 - Listing only relevant account types for cases where account selection is made in payment order consent

Improvements have been made to list only the relevant account types for cases where account selection is made in the payment order consent.

94966 - Variation of messages displayed in x-JWS-Signature error states

x-JWS-Signature provides a variety of messages displayed in error situations.

94967 - Variation of messages displayed in PSU-Fraud-Check error states

Diversification of messages displayed in PSU-Fraud-Check error cases is provided.

94969 - New validations added to the Payment Order request

New validations have been added to the Payment Order request.

Test Automation

93722 - Payment Order Scenarios test automation in TCMB standards

A code has been developed for test automation of Payment Order Scenarios in TCMB standards.

93776 - Header and Signature controls for Account Access Consent in TCMB standard

Header and Signature controls were automated for Account Access Consent in TCMB standard.

Applications

94762 - Dynamic change of define public key feature during application creation

During application creation, it is provided to dynamically change the define public key feature.

Kuveyt Türk

91176 - Editing the payment consent confirmation screen in accordance with the new design

Payment consent confirmation screen has been arranged in accordance with the new design.

KT Bank AG - Obdirectory Certificate Validation Integration

94712 - Preparation of test cases for OB Directory and obtaining customer approval

Test scenarios were prepared for OB Directory and customer approval was obtained.

SOAP Connector

88432 - The names of the properties entered in the Input field in Modify Request Body can be made dynamic.

The names of the properties entered in the Input field in Modify Request Body can be made dynamic.

Integration

94717 - Product-specific development of new features added by BKM on x-rate-limit

New features added by BKM regarding x-rate-limit were developed specifically for the product.

FIXED ISSUES

PORTAL	TASK	ISSUE	ACTION	STATUS
Management Portal	96453	UI Findings related to X-Rate-Limit policy.	UI fixed	Done
Management Portal	91376	Cannot be deleted from applications registered on the application screen	Backend fixed	Done
Developer Portal	86694	Expressions do not fit in Applications > Description Field	UI fixed	Done
Gateway	96415	Change of yetTmmTime information in Payment order response	Backend fixed	Done
Gateway	96512	500 Internal Server Error error is received when the consent number value is sent as an example 123 in the endpoint with the X-Rate-Limit definition	Backend fixed	Done
Gateway	96510	Incorrect printing of the path information of the error message given due to X-Rame-Limit	Backend fixed	Done
Gateway	96447	No X-Rate-Limit check when X-Access-Token is not sent in Get Account Consent and Get Payment Consent endpoints	Backend fixed	Done
Gateway	96459	Error creating consent in X-Rate-Limit check	Backend fixed	Done
Gateway	96402	Failure to return Id as GUID in Payment Order Consent Response	Backend fixed	Done
Gateway	96442	Incorrect error message when Access Token is sent in Payment Order Inquiry request	Backend fixed	Done
Gateway	96406	Editing the time difference between occurTime and yetCommentTime	Backend fixed	Done
Gateway	96417	Payment Order consent (POST) > Response > update status information	Backend fixed	Done
Gateway	96181	InvalidFormat error when xAccessToken is not sent in Payment Order Consent query request	Backend fixed	Done
Gateway	96056	Problems detected in request header validations of Account Information endpoints	Backend fixed	Done
Developer Portal	86705	Application Approve Workflow problem	Backend fixed	Done
Gateway	92555	Internal server error in get_acounts_list method	Backend fixed	Done
Gateway	95615	Problem with Psu-Fraud-Check and X-JWS-Signature headers past exp date	Backend fixed	Done
Gateway	95405	A 500 Internal Server Error is received when trying to create an Account Access Consent with the data received from the trip.	Backend fixed	Done
Gateway	95646	Incorrect yetTmmTime format in payment order consent response	Backend fixed	Done
Management Portal	95111	Gateway logs problem	Backend fixed	Done
Gateway	95745	PSU-Fraud-Check header is not checked when bypass=1 as in X-JWS-Signature	Backend fixed	Done
Gateway	95616	The problem of creating successful consent when the request is sent as "04 and 05 are not sent", "by sending the values of accountIslmBslZmn and accountIslBtsTime" as permissionTur	Backend fixed	Done
Management Portal	95166	Dirty data in ModifyRequestBody output	Backend fixed	Done
Gateway	95306	Incorrect error is received when request for consent with Consent Status B and Y in access token request with Renew Token	Backend fixed	Done
Gateway	95614	Header controls are not done before kmlkTur control in the body.	Backend fixed	Done
Gateway	95170	Changing the IzinTur info in account selection	Backend fixed	Done
Gateway	95275	httpCode, httpMessage, errorCode are incorrect in x-JWS-Signature error cases	Backend fixed	Done
Gateway	95518	Incorrect errors for X-TPP-Code and X-ASPSP-Code headers	Backend fixed	Done
Gateway	94968	Changing odmKynk validation in Payment Order Consent	Backend fixed	Done
Developer Portal	94400	Certificate error	Backend fixed	Done
Gateway	91590	Internal server error	Backend fixed	Done
Gateway	95206	Incorrect error code in Access Token and Payment Order API in x-JWS-Signature error states	Backend fixed	Done

Next Previous