v1.8.2
Creation Date: 18.01.2023
Payment Order Transactions
90269 - Obtaining consent without customer data
Improvements have been made to obtain consent without some customer data.
85219 - Adding changes to the Payment Order model to the product
Necessary work has been done to add the changes made in the Payment Order model to the product.
88875 - Redesign of Payment Order Consent confirmation screen
Payment Order Consent confirmation screen has been redesigned.
90249 - Header control in the service of listing the consents offered by the banks to their customers through their own systems
An improvement was made on the header control in the service of listing the consents offered by the banks to their customers through their own systems.
90192 - Approval with the OTP mechanism while approving the Payment Order consent
While the Payment Order consent is being approved, it is ensured that the approval process is performed with the OTP mechanism.
90095 - Policy preparation for payment status inquiry
Policy has been prepared in order to query the payment status.
85559 - Necessary studies for adding the changes made in the Payment Order Consent model to the product
Necessary work has been done to add the changes made in the Payment Order Consent model to the product.
89388 - Target url access problem
The problem of returning the expected result of the Target Url in the PIS - Payment Filter with a Consent endpont has been fixed.
89585 - Providing customer account authorization check for payment order consent
Improvements have been made to provide customer account authorization check for payment order consent.
89570 - Checking Fraud status before confirming payment order consent
Fraud status is checked before the payment order consent is approved.
89588 - What to do on the consent confirmation screen when the sender account information is not specified while creating the payment order consent
An improvement has been made on what to do on the consent confirmation screen when the sender account information is not specified while creating the payment order consent.
89589 - Adding QR code improvements to the product in payment order consent
Data matrix improvements have been added to the product in the payment order consent.
89548 - Managing colas information from customer verification service while creating payment order consent
Improvements have been made to manage the colas information from the customer verification service while generating the payment order consent.
Integration
90153 - The ability of the consent rework service developed for the integration layer to work according to the payment and account consents.
It has been ensured that the consent rework service developed for the integration layer can work according to the payment and account consents.
89188 - Signature Control Function
Signature Control Function feature has been enhanced.
89972 - Adding a status check to the header of the consent rework service developed for the integration layer
Status control is added to the header of the consent rework service developed for the integration layer.
87700 - Policy development to offer HealthCheck services
Policy has been developed to provide HealthCheck services.
88633 - Linking structure of endPoints defined for the environment opened in the Central Bank standard can work according to default values
The Linking structure of the endPoints defined for the environment opened in the Central Bank standard has been enabled to work according to the default values.
89026 - Revocation of consent when a re-display link is called while Account Access Consent or Payment Order Consent status is "Authorized" or "Authority Used"
Improvements have been made to revoke consent when a re-display link is called while the Account Access Consent or Payment Order Consent status is "Authorized" or "Authority Used".
82698 - Development for Data Format Validations
Improvements have been made for Data Format Validations.
89408 - Improvements to be made after GKD if the user does not have express banking permission
Improvements to be made after GKD if the user does not have open banking permission have been determined.
89838 - Adding the services that require GKD routing as a query parameter to the request
It is provided to add the services that require GKD routing as a query parameter to the request.
89973 - Adding the consent field to the GKD transaction
It has been ensured that the consent field is added to the GKD process.
89325 - Making the necessary improvements to sign the transaction responses and add them to the request header.
Necessary improvements were made so that transaction responses were signed and added to the request header.
88878 - Adding the YΓS cost field on the CBRT Integrations screen and applying this value to the Payment Order Consent response
In the TCMB Integrations screen, YΓS expense field is added and this value is applied to the Payment Order Consent response.
Account Information Service
87235 - Actions to be taken in case the user cancels by pressing the reject button on the account access consent confirmation screen
Improvements have been made for the actions to be taken in case the user cancels by pressing the reject button on the account access consent confirmation screen.
89027 - Actions to be taken if the bank user has no account on the Account Access Consent Approval screen
On the Account Access Consent Approval screen, improvements have been made regarding the actions to be taken if the bank user does not have an account.
82705 - Management of limits for automated queries not initiated by the user by YΓS
Limits are managed by YΓS for automated queries that are not initiated by the user.
88928 - Adapting the change made in the customer verification service to the product while creating the Account Consent
While creating the Account Consent, the change made in the customer verification service was adapted to the product.
89584 - Providing client account authorization control for account access consent
Improvements have been made to ensure customer account authorization control for account access consent.
89543 - Checking Fraud status before confirming account access consent
Fraud status is checked before the account access consent is approved.
FIXED ISSUES
| PORTAL | TASK | ISSUE | ACTION | STATUS |
|---|---|---|---|---|
Developer Portal | 91049 | Clocks in ISO format return as +03:00 in request and +00:00 in response | Backend fixed | Done |
Gateway | 91039 | Removing customer controls from the delete end in the integration layer | Backend fixed | Done |
Gateway | 91040 | Payment Order Consent Inquiry request is a blank value with 404 status as a response. | Backend fixed | Done |
Gateway | 91037 | Setting odmStm=H as default in case kmlVrs is not sent in payment order consent request | Backend fixed | Done |
Gateway | 91025 | In the response of the Health Check API, status should be returned instead of value. | Backend fixed | Done |
Gateway | 91022 | In GKD Cancellation Cases, removing the Consent screen and going directly to the cancellation link | Backend fixed | Done |
Gateway | 91023 | In GKD Cancellation Cases, clicking the consent link for the second time leads to direct cancellation | Backend fixed | Done |
Gateway | 91018 | The problem of getting a successful response when a request is made by putting an invalid Consent Number in the url to the Rework endpoint. | Backend fixed | Done |
Gateway | 91011 | No error is received when we want to revoke a revoked consent at the delete end for Account Order consent. | Backend fixed | Done |
Gateway | 91015 | "TR.OHVPS.Resource.InvalidFormat" error is not received when the request is sent by entering alpha numeric value in the hhsKod value field in the request body of the account information consent | Backend fixed | Done |
Gateway | 91008 | After the account information consent is created for the corporate customer, the values of kmlkTur and kmlkVrs are null while getting it. | Backend fixed | Done |
Gateway | 90978 | In the Transactions endpoint, an invalid error is received for the accountOperationBslTrh and accountIslemBtsTrh params. | Backend fixed | Done |
Gateway | 90954 | After obtaining consent for A ttp with X acocunt in Account Information Consent, an error is received when trying to obtain consent for B tpp with the same X acconut. | Backend fixed | Done |
Gateway | 90745 | Special character problem in Query String | Backend fixed | Done |
Gateway | 90277 | "UNCLASSIFIED_ERROR" is received when the x-consent-type value is sent as A on the delete end opened to the bank for the customer whose payment order consent has been obtained. The same situation is valid for the consent of the consent order and the sending of the P. | Backend fixed | Done |
Gateway | 90802 | Without X-TPP-Name header, when Get Account Consent request is sent after payment order consent is received, the response is null. | Backend fixed | Done |
Gateway | 90741 | While there is "kolas" under "alc" in the request body of the Payment Order request, the "unv" value should not be mandatory. | Backend fixed | Done |
Gateway | 90777 | Adding 0 to the beginning of rizaCancelDetailCodes, which are single digits in the account access consent | Backend fixed | Done |
Gateway | 90206 | Bank Login > Redirection URL error | Backend fixed | Done |
Gateway | 89897 | Editing date field validations as field=pageNo remaining, related field itself | Backend fixed | Done |
Identity server | 90208 | unable to access consent screen | Backend fixed | Done |
Gateway | 90374 | Checking access token and refresh token validations | Backend fixed | Done |
Gateway | 90103 | Problems detected in validation controls of TCMB Payment Order Consent Header and Body parameters. | Backend fixed | Done |
Gateway | 90440 | Changing the errorCode when an undefined customer number is entered in the Payment Order consent request | Backend fixed | Done |
Gateway | 90280 | Payment order consent status remains E when Refresh Token Expire Date expires | Backend fixed | Done |
Gateway | 90172 | wrong payment order no sending | Backend fixed | Done |
Gateway | 89901 | Changing the error when the receiver is sent empty or the alc.hspNo is not sent at all in the payment order consent request | Backend fixed | Done |
Gateway | 89892 | For paging endpoints, when a non-page number is entered, the response is completely blank. | Backend fixed | Done |
Gateway | 90158 | Changing the error in sending the wrong consent no in the renewal token | Backend fixed | Done |
Management Portal | 89722 | Gateway Logs problem | Backend fixed | Done |
Gateway | 90283 | Access token - yetType length check in refresh token | Backend fixed | Done |
Management Portal | 89032 | An error is returned in the logs of the healtcheck service, which received a successful response, in the gateway logs. | Backend fixed | Done |
Gateway | 90209 | UNCLASSIFIED_ERROR | Backend fixed | Done |
Gateway | 89889 | krdHsp may not be displayed if kulKrdTtr is empty | Backend fixed | Done |
Gateway | 90017 | date errors | Backend fixed | Done |
Gateway | 90150 | Having Terminated when refresh token deadline arrives | Backend fixed | Done |
Gateway | 89911 | Check if the consent number is greater than 128 in the access token | Backend fixed | Done |
Gateway | 89912 | Access token consent number size is correct, the error given when an incorrect consent number is entered with no format error changes | Backend fixed | Done |
Gateway | 90096 | If the consent creation process is done with kolas, the information that comes full as a result of consent does not come in the Get account consent query. | Backend fixed | Done |
Gateway | 89992 | If the x-rateLimitte page number parameter is greater than 1, it should not increase the transaction counter. | Backend fixed | Done |
Gateway | 90108 | Payment Order Consent > Updating the colas data returned in Response back into the consent | Backend fixed | Done |
Gateway | 90016 | Payment Order Consent > Customer Validation > adding currency | Backend fixed | Done |
Gateway | 89903 | Sending gon.hspRef information to senderAccRef field in CustomerValidation | Backend fixed | Done |
Gateway | 90088 | Url index error | Backend fixed | Done |
Gateway | 90033 | odmStm field not coming in get Consent | Backend fixed | Done |
Gateway | 89999 | kkodUrtKod field not coming in get Consent | Backend fixed | Done |
Gateway | 89907 | Adding rzaIptlDtyKod in response model | Backend fixed | Done |
Gateway | 89981 | accounts > transactions > although data is returned from the bank, no data is returned for pages other than page 1. | Backend fixed | Done |
Gateway | 89980 | The x-request-id requirement check should be removed at the /api/v1/tcmb/consent/delete/{rizaNo} endpoint. | Backend fixed | Done |
Gateway | 88808 | Fields in the response model of the Access Token request must be camelCase | Backend fixed | Done |
Gateway | 89031 | There are extra /s in the response body of the healthcheck endpoint. | Backend fixed | Done |
Gateway | 90115 | The control of the x-customer-id header in the request header of the delete end we opened to the bank should be completely removed. | Backend fixed | Done |
Gateway | 90136 | Failed_'14' : DDH cancellation : Fraud Suspicion | Backend fixed | Done |
Gateway | 88807 | When an empty body is received from the bank's transactions service, airapi's transactions endpoint cannot be parsed. | Backend fixed | Done |
Gateway | 88811 | It is not necessary to send the x-access-token = {{x-access-token}} header among the request headers of the RevorkAnAccountConsent endpoint. | Backend fixed | Done |
Gateway | 88810 | In the case where the Account Consent Request is ohkTur B, when the first consent is in status B, and a new consent is created for the same customer, the consent status of the first consent is not withdrawn to I. | Backend fixed | Done |
Gateway | 88896 | The Get Account List endpoint does not work with the current model. | Backend fixed | Done |
Gateway | 89158 | GET /accounts/{hspRef}/operations validation of queryString fields | Backend fixed | Done |
Gateway | 89161 | Validation of GET /balance and GET /accounts/{hspRef}/balance queryString fields | Backend fixed | Done |
Gateway | 89162 | Validation of GET /accounts and GET /accounts/{hspRef} queryString fields | Backend fixed | Done |
Gateway | 89216 | Endpoints > Waiting for Target URL even though AirApi Functions are attached | Backend fixed | Done |
Gateway | 89593 | AuthorizationCode popup appearing and disappearing immediately | UI fixed | Done |
Gateway | 89095 | Consent ID longer than 128 characters in access and renewal token | Backend fixed | Done |
Gateway | 89098 | sending refresh token empty | Backend fixed | Done |
Gateway | 89238 | Empty or no PSU-Fraud-Check sent | Backend fixed | Done |
Gateway | 89241 | The x-access-token requirement and control in Get Payment Consent will be removed | Backend fixed | Done |
Gateway | 89659 | Creating Account Information Consent gets Internal Server Error | Backend fixed | Done |
Gateway | 89495 | ErrorCode adjustment according to the code information from the bank customer-validation service | Backend fixed | Done |
Gateway | 89100 | After revoking the consent in the access token, First of all, it should control over the consent. | Backend fixed | Done |
Gateway | 89154 | If iznTur = 02 is not selected, there will be no hspDty object in the response. | Backend fixed | Done |
Gateway | 89153 | time validation between dates | Backend fixed | Done |
Gateway | 89156 | If iznTur = 05 is not selected, there should be no islDty object in the response | Backend fixed | Done |
Gateway | 89721 | Account_access_consent deletion - gives error 500 Internal Error. | Backend fixed | Done |
Gateway | 89747 | Meaningless error when unable to connect to Payment Order Consent Account Service | Backend fixed | Done |
Gateway | 89036 | In environments opened in TCMB standard, the Scope selection screen should not be displayed while performing GKD. | Backend fixed | Done |
Gateway | 88805 | Problem on DDH screen during Account Information Consent process | Backend fixed | Done |
Gateway | 89099 | access token controls | Backend fixed | Done |
Gateway | 89883 | UNCLASSIFIED_ERROR | Backend fixed | Done |
Gateway | 89640 | AccountOperationBslTime max 1 year back check | Backend fixed | Done |
Gateway | 89025 | If there is no customer sent in the body of the account access request, the error should be changed. | Backend fixed | Done |
Gateway | 89886 | bldAddress field must be required when authorization type is A | Backend fixed | Done |
Gateway | 89753 | Returning the date fields in the Account Access Consent response object in ISO format | Backend fixed | Done |
Gateway | 89754 | Returning the date fields in the Account Payment Consent response object in ISO format | Backend fixed | Done |
Gateway | 89890 | The min date for the AccessPermitLastTrh must be consent +1 day | Backend fixed | Done |
Gateway | 89891 | No Consent Cancellation Detail Code in payment order response | Backend fixed | Done |
Gateway | 89893 | Only the ending one of the dates is wrong, but both of them are wrong. | Backend fixed | Done |
Gateway | 89910 | The odmAyr.yosKod will be removed from the payment order consent response. | Backend fixed | Done |
Gateway | 89422 | Payment Order Consent validations | Backend fixed | Done |
Gateway | 89738 | When I send the date as 2022-10-071T20:34:15+03:07, "Internal Server Error" is returned. | Backend fixed | Done |
Gateway | 89902 | Issue when gon.hspNo is never sent in Payment Order Consent | Backend fixed | Done |
Gateway | 89984 | yetYntm should not take any value other than Y and A | Backend fixed | Done |
Gateway | 89895 | RevorkConsent method will remove rizaNo from header | Backend fixed | Done |
Gateway | 89896 | It looks like x-rate-limit = 0. There should be 4 in the individual and 12 in the corporate. | Backend fixed | Done |
Gateway | 89983 | Changing the format of dates in the response model to ISO | Backend fixed | Done |
Gateway | 89905 | Authorization Failed | Backend fixed | Done |
Gateway | 89908 | gkd.yetTmmTime = should be set as consent creation date + 5min | Backend fixed | Done |
Gateway | 89898 | "krmKmlkVrs" and "krmKmlkTur" are not sent to Customer Validation service while creating payment order consent | Backend fixed | Done |
Gateway | 89899 | When you remove the "kmlk" object completely and send it, the error will be changed. | Backend fixed | Done |
Gateway | 89989 | Token check fix when going to bank service | Backend fixed | Done |
Gateway | 89904 | If kolas.kolasTur and kolas.kolasDgr are full, they are sent to the addressType and addressValue fields in the CustomerValidation service. | Backend fixed | Done |
Gateway | 89922 | Accounts are listed despite having gon.hspNo. | Backend fixed | Done |
Gateway | 89909 | In the payment order consent response, waitingOdmZmn CustomerValidation is not received, but it is filled with date | Backend fixed | Done |
Gateway | 89906 | Error change when sending ohbsMasrafTtr.ttr = 0.0 | Backend fixed | Done |
Gateway | 88593 | In the Create_An_Account_Consent service, there should be a 12-month check for accountIslemBslZmn and accountIslemBtsZmn instead of 6 months. | Backend fixed | Done |
Gateway | 89900 | Error received when islTtr.ttr = 0.0 will be replaced | Backend fixed | Done |
Gateway | 90003 | Problems detected in validation controls of Header and Body parameters of TCMB requests. | Backend fixed | Done |
Gateway | 90063 | Managing the error from the bank in payment order requests | Backend fixed | Done |
Last updated