v1.1.1
Creation Date: 27.07.2020
4033 Creating A New Tenant Authority
Tenant admin can define a new tenant authority. Thus, more than one user can be authorized for a tenant.
The invitation e-mail is sent to the new user.
User activation is completed by e-mail and password is defined.
Authority can be selected when defining a new user.
More than one role can be assigned to a user.
It is managed based on tenant.
4035 Defining new roles for User Management
Document Admin, Endpoint Admin and Configuration Admin roles are defined.
It is managed based on tenant.
4036 User Listing and Update
Tenant admin can check and update the list of users he created.
Tenant admin can list the users he defined.
The role of a selected user can be changed.
Tenant admin can deactivate the user.
It is managed based on tenant.
7811 Publishing ApiGoβs Contracts under the Legal Page
Airapi users can see the contracts from one point. Airapiβs contracts are publishing under the Legal Page according to their categories.
Contracts are shown in the Free Trial section.
Admin Role Management
4653 Configuration Admin
A user with the Configuration Admin role can access the Configurations and Test Automation menus when logged in to the Management Portal. So, the admin will be able to manage the configuration settings.
The admin can log in with Configuration Admin Role as a user.
Configuration Admin transactions are logged.
4649 Document Admin
A user with the Document Admin role can access the Documents and Agreements menus when logged in to the Management Portal. So, the admin will be able to manage Documents and Contracts.
The admin can log in with Document Admin Role as a user.
Document Admin transactions are logged.
4654 Restriction Admin
A user with the role of Restriction Admin can access the Restrictions menu when logged in to the Management Portal. So, the admin will be able to manage restrictions.
The admin can log in with Restriction Admin Role as a user.
Restriction Admin transactions are logged.
4652 Endpoint Admin
A user with the role of Endpoint Admin can access the Endpoints, Applications and Developers menus when logged in to the Management Portal. So, the admin will be able to manage Endpoint definitions, applications, and developers.
The admin can log in with Endpoint Admin Role as a user.
Endpoint Admin transactions are logged.
6369 Developer Portalβs Documents Order
The order of the documents prepared in the Management Portal is displayed on the Developer Portal. In the Management Portal, the location/order of the documents under a category can be changed.
Categories can be changed among themselves.
Documents and categories can be deleted.
7538 Managing dynamically Developer Portal Menus
Airapi user can give a link to add the desired document.
In the Management Portal, a dynamic menu can be added.
Configuration -> Developer Portal Settings -> Home Menus
Domain Management
4145 β.comβ and β.com.trβ Transitions
Local users who want to use Airapi Cloud can access via βairapi.com.trβ and global users via βairapi.comβ.
4146 Certificate Definitions for βapigo.comβ and βapigo.com.trβ
ApiGo Cloud users can access apigo.com and apigo.com.tr addresses with the https protocol.
All components can be accessed with the https protocol.
4049 Exclude Policy
Specific endpoints can be defined that are not affected by global constraints. Thus, the policy provides flexibility in Endpoint configuration.
Exclude Policy can be defined while creating an endpoint.
TPP is not affected by Global Restriction when it sends a request to the gateway.
In the policy definition, which restrictions will not be affected can be choosen.
Data Mask Policy
7544 Data Mask Policy
When defining an endpoint, a desired data field can be masked with this policy. Besides, private customer data can be masked dynamically.
Data Mask policy can be used in all types of environment and for Endpoint created with POST and PUT methods.
7545 Masked Data for Logging
If the gateway has an endpoint with mask policy, it performs the log operation with masked private data.
Payment Initiation and Consent logs are masked in an environment based on Berlin Group Standards.
Payment Initiation logs are masked in an environment based on UK Open Banking Standards.
Multiple Functions Policy
5361 Multiple Functions Policy
An endpoint can execute multiple transactions from more than one destination path. So, validation and other managerial processes can be done.
Multiple Functions Policy can be reached in the General category.
The following options are available under each destination address. Transfer Header, Transfer Body (This feature can be selected for methods other than GET.)
Another destination can be added with the Add new button.
Up to five destination addresses can be added.
Destination Path in the Endpoint definition screen do not need to fill if this Policy has been defined.
Only one Multiple Functions Policy can be added for an Endpoint.
5373 Displaying Static Endpoints
Endpoints created automatically according to the selected environment type can be displayed on the Endpoints menu.
Static endpointsβ scripts can be updated which is created in an environment based on Berlin Group Standard.
βv1β expression at the beginning of endpoints are added as a default.
Retiring API Policy
4121 Versioning of API Updates
When defining Endpoint, version can be defined. Thus, the version for APIs can be reached.
When updating Endpoints in Management Portal, version definition such as v1 / v2 / v3 can be specified.
The version information is added to the path of Endpoint.
4122 Retiring API Policy
With Retiring API Policy, TPP is informed that the desired Endpoint is no longer available.
The policy can be added while defining Endpoint.
The response message is editable.
When accessed through the gateway, the defined message along with HTTP 400 code can be responded.
8683 Global Variables Setting
Global variables used in the environment can be defined. These definitions can be used for creating APIs, documents, and contracts.
Values are stored in based on environment.
This setting can be exported/imported with configurations.
4039 Displaying Activity Logs
The activities of all authorized users are logged on the Management Portal. So, the audit trace infrastructure has been created.
Username, status, description, and action date are logged in Activity Logs.
4040 Monitoring Activity Logs
Tenant admin can list activity logs. Thus, he can follow the logs made by himself and the other authorized users.
Activity logs located on the Management Portal can be brought for the relevant tenant.
Tenant admin logs can filter by date, status code, HTTP method, status, path, and transaction by criteria.
Tenant admin can export to MS Excel.
4044 Global Rate Limit Management
Tenant admin can define, update, or delete a central Rate Limit for all endpoints. Thus, the limit can use as a single definition to be valid for all endpoints.
Global Rate Limit based on an environment.
How many requests, how long they will wait, what is the response message can be defined.
Identification, update, and deletion can be executed on one screen.
4045 Rate Limit Policy - Additional Development
Tenant admin can define how many requests and how long they will wait in the current rate limit policy.
Policy can work in all methods. (GET, PUT, POST, DELETE)
Request number and duration information can be recorded based on environment.
4047 Working Hours Configuration Management
Endpoints can be accessed at certain times of the day. Thus, TPPs cannot access these endpoints outside certain hours.
Working Hours configuration can be defined and updated from one screen.
Time Zone can be defined in Working Hours configuration.
The days of the week can also be specified in the configuration.
Berlin Group Standards Documentation and Endpoints
4052 Berlin Group Standards Documentation
Berlin Group Standards documents are defined automatically after an environment in the Berlin Group Standard is created.
Prepared in accordance with the XS2A Interface (Berlin Group Standards) document.
9174 Fund Confirmation Endpoint
Fund Confirmation Endpoint is automatically generated for an environment created in the Berlin Group Standards.
Prepared in accordance with the XS2A Interface (Berlin Group Standards) document.
Organizing Error and Warning Messages
6488 Returning error messages from gateway with an error format according to Berlin Group Standards
Error Messages have been revised according to the XS2A Framework document.
Prepared in accordance with the XS2A Interface (Berlin Group Standards) document.
6491 Displaying errors returned from the Gateway
Errors received from the Gateway can be displayed on Management Portal to error management.
Errors can be filtered on the Management Portal.
It can be clearly seen whether the error is caused by Gateway or destination path.
Filtered log can be exported to MS Excel.
5017 Export/Import Operations on Endpoint Definition Screen
Export can be done by selecting all endpoints or specific endpoints in the endpoint definition screen.
Endpoint definitions come with βselect allβ selected by default.
The user can do unselect all and select specific Endpoints if he wishes.
In the import process, the user can import all endpoints or as many as he wishes.
During the import process, the Endpoint definition is displayed in destination environment.
If Endpoint transfer is made after import, Push button will be active in Endpoint definition screen.
5578 Showing only User Defined Endpoints in Swagger
When the developer clicks on the swagger link, only User Defined Endpoints will be appeared.
Payment and Consent List β Additional Development
6315 Filtering Payment Initiation List
In enviroments created with the Berlin Group Standards, the desired record can be easily found using the payment initiation list filter.
It can work in environments created in the Berlin Group Standard.
The list table can be filtered according to the following fields. Status, Payment Service, Payment Product, UserName
6316 Reject Function for Payment Initiation
Payment initiation records can be rejected. Thus, cancellation request of transactions coming to the bank can be made through Airapi.
The function can be worked in environments created according to Berlin Group Standards.
Records that do not have a rejected status can be rejected. Status = RJCT
The rejection action can be logged by tenant admin and specified accordingly.
6317 Filtering Account Consent List
The list of account consents can be filtered so that the desired record is found easily.
It can work in environments created in the Berlin Group Standards.
The list table can be filtered according to the following fields. Status, UserName, TPPName
Constant expressions in the filters are brought with the combo box.
6318 Reject Function for Account Consent
Account Consent records can be rejected. Thus, cancellation request of transactions coming to the bank can be made through Airapi.
The function can be worked in environments created according to Berlin Group Standards.
Records that do not have a rejected status can be rejected. Status = RJCT
The rejection action can be logged by tenant admin and specified accordingly.
7556 Combo boxes for filters in Payment Initiation and Account Consent Lists
Constant expressions in the filters are brought with the combo box.
All fields except the UserName field can be displayed with the combo box.
6375 Runman Test User and Test Report
Users that will be used while performing test automation can be defined on a screen. Thus, the authentication process is automatically executed in test automation.
Test users can be added, deleted, updated, and listed.
FIXED ISSUES
Last updated