v1.8.6
Creation Date: 24.02.2023
Integration
79044 - Loading the TCMB "Integration configuration" data from the import file
According to the TCMB's request, improvements have been made to load the "Integration configuration" data from the import file.
96855 - Changes to be made on x-rate-limit policy after the update in BKM document
After the update in the BKM document, the code has been developed for the changes to be made on the x-rate-limit policy.
92664 - Updating the integration points documents used in the TCMB standard
Integration points documents used in the TCMB standard were updated.
Account Order Transactions
97165 - Calculation of odmStm field in payment flows not initiated with credentials
Improvements have been made to calculate the odmStm field in payment flows that are not initiated with credentials.
Test Automation
93723, 93726 and 97457 - Preparation of test cases for Payment Order Scenarios in TCMB standards
Test automation cases were prepared for Payment Order Scenarios in accordance with TCMB standards.
Improve Users Experiences Design
91021 - Making user experience and design studies for the Gateway Logs page
User experience and design studies were provided for the Gateway Logs page.
FIXED ISSUES
| PORTAL | TASK | ISSUE | ACTION | STATUS |
|---|---|---|---|---|
Management Portal | 98521 | UI error on the Import-Export screen within the scope of loading the TCMB Integration configuration data from the import file | UI fixed | Done |
Gateway | 98482 | Timestamp format error in x-rate-limit errors received in Payment Order Consent and Payment Order requests | Backend fixed | Done |
Gateway | 98485 | Extra ' value in errorCode in error message received when odmAyr value is not 0 in Payment Order Consent request | Backend fixed | Done |
Gateway | 98431 | Idempotency not working in Payment Order Consent request | Backend fixed | Done |
Gateway | 97159 | The problem of obtaining a new consent with MNOs connected to the relevant TCKN ID, although there is an Account Access Consent with a TCKN and in K status | Backend fixed | Done |
Gateway | 98340 | Incorrect assignment of cancellation detail code value | Backend fixed | Done |
Gateway | 98268 | The problem that the data sent empty in the consent requests are shown in the response | Backend fixed | Done |
Gateway | 97871 | JWS-Signature checksum error | Backend fixed | Done |
Gateway | 98176 | Incorrectly printing the Path information in the error message given when the X Rate Limit limit is stuck in the Get Payment Order Consent request. | Backend fixed | Done |
Management Portal | 97790 | Failure to count X Rate Limit at the Transactions endpoint | Backend fixed | Donev |
Management Portal | 97800 | Failure to count X Rate Limit in Payment Order Consent get request | Backend fixed | Done |
Gateway | 97808 | The error message that comes when the tpp code is sent as "aaa" in the Get Balance request changes when the x rate limit is defined. | Backend fixed | Done |
Gateway | 97831 | Wrong error message when optional headers in some endpoints are sent as duplicate | Backend fixed | Done |
Gateway | 97839 | In some endpoints, when tpp code and psu initiated values are sent blank, an error is given as if a mandatory field was not sent. | Backend fixed | Done |
Gateway | 97848 | In some endpoints, when x tpp code enters 5 characters, it gives an error as if it sent the same parameter twice. | Backend fixed | Done |
Gateway | 97854 | In some endpoints, the fields in the error message are incorrect when the psu intiated value is entered as EH. | Backend fixed | Done |
Gateway | 97822 | Invalid Token is received when there is X Rate Limit definition in get Account List endpoint, but successful response is received when there is no definition | Backend fixed | Done |
Gateway | 97786 | No distinction between Institutional and Individual in X Rate Limit remaining count | Backend fixed | Done |
Gateway | 97798 | In X Rate Limit count, pre-definition requests are not counted | Backend fixed | Done |
Gateway | 97560 | Although odmStm value is created as H in Payment Order Consent request, odmStm value is not included in response when get is made | Backend fixed | Done |
Gateway | 97562 | Error on trip screen despite applying idempotency in Payment Order post request | Backend fixed | Done |
Gateway | 97557 | After the request is sent successfully in the Payment Order post request, only the last character of the x-requset-id in the request header is deleted and the wrong error message is received when the request is sent. | Backend fixed | Done |
Gateway | 97468 | Incorrect errorCode value of the error message received when the request is made with the alc.hspNo field empty ("") in the Payment Order post request | Backend fixed | Done |
Gateway | 97321 | Internal server error | Backend fixed | Done |
Gateway | 97378 | Error when request headers, which are mandatory in TCMB endpoints, are sent during the request. | Backend fixed | Done |
Gateway | 97397 | "There is an authorized account information consent already." getting error | Backend fixed | Done |
Gateway | 97383 | Incorrect errorCode in Payment Order Consent API | Backend fixed | Done |
Gateway | 97166 | The expected error does not occur when X-Access-Token value is sent as invalid while making Payment Order | Backend fixed | Done |
Gateway | 97176 | Invalid Format error in KOLAS flow in Payment Order api | Backend fixed | Done |
Gateway | 97055 | Error when neither hspNo or hspRef is sent in Payment Order confirmation request, as if neither was sent | Backend fixed | Done |
Gateway | 97024 | Incorrect path information when JWS Signature error is received in Payment Order Consent and Account ACCESS consent requests | Backend fixed | Done |
Gateway | 97022 | X-JWS-Signature error on Payment Order Consent and Account Access Consent requests | Backend fixed | Done |
Gateway | 97018 | Getting UNCLASSIFIED_ERROR when the request is discarded by leaving the ttr value blank in the Payment Order Consent request | Backend fixed | Done |
Gateway | 97030 | Wrong error message is given when the Payment Order No value used in the Payment Order get request is an invalid value | Backend fixed | Done |
Gateway | 96902 | Getting 500 Internal Server Error while getting Payment Order | Backend fixed | Done |
Gateway | 95997 | The size of the Account Selection component remains constant when a small number of accounts are listed on the Account Access Consent and Payment Order Consent screens. | Backend fixed | Done |
Management Portal | 96831 | x-rate-limit number not decreasing | Backend fixed | Done |
Gateway | 96836 | Payment Order consent response and Get Payment Order consent model difference | Backend fixed | Done |
Gateway | 96828 | Returning Id information as UUID in Payment Order consent Response | Backend fixed | Done |
Management Portal | 95447 | Authorization problem in adding new user | Backend fixed | Done |
Last updated