The AML resource server is running as a separate service and has its own release cycle different from the rest of the OIDC platform.
Changes in V75
Release date: 2022-09-12
No | Changes |
---|---|
1 | High risk industry sectors are now highlighted in the reports |
2 | Improved error messages for the Norwegian Population Registry |
Changes in V74
Release date: 2022-08-10
No | Changes |
---|---|
1 | Preparations to switch the supplier-based integration against The Norwegian National Registry from Vipps AS to BankID BankAxept AS. More information and updated delegate routines will be provided for merchants and customers soon. |
2 | The report language parameter now supports additional values nb and nn . Valid options are now: no|nb|nn|en|NO|EN|NB|NN (two letters ISO 639-1) |
3 | Added mapping of previously unknown organization types |
4 | Added test persons from Sweden, Denmark and Finland |
Changes in V73
Release date: 2022-07-05
No | Changes |
---|---|
1 | Added support for BankID authentication input to the asynchronous person search API |
2 | The organization search against Sweden, Denmark, and Finland is available by default to any customer, and manual access request for this purpose is no longer necessary. |
3 | Added a danish test company to the Current environment |
4 | Bug fixes in the handling of webhooks in the asynchronous APIs |
Changes in V72
Release date: 2022-06-22
No | Changes |
---|---|
1 | The Beneficial Owners report service will now deliver a positive response with a PDF report even when the customer has no access to the Norwegian National Registry. The information elements citizenship and birthplace will be missing in this case. |
2 | Removed information about fuzzy mode from the Person PDF report. |
3 | Changed to the improved name searching algorithm against Norwegian National Registry also to requests with the usage of the date of birth instead of ssn. This name matching can return successful results even for inputs consisting of initials or name parts not present in the registration. |
4 | Fixed a bug causing duplicate error messages about roles in the Person PDF report. |
Changes in V71
Release date: 2022-06-08
...
No | Changes | ||||
---|---|---|---|---|---|
1 | The reason to be a beneficial owner is now also returned as part of the JSON API response. Three new fields are introduced:
In addition, the existing field | ||||
2 | Improved support for AML search after persons with nationality other than Norwegian.
| ||||
3 | Beneficial owners are described with an address when the information is available. (both PDF and JSON) | ||||
4 | Unidentified beneficial owners are described with a country when that information is available. (both PDF and JSON) |
...
No | Changes |
---|---|
1 | Switched to T-rank as the source of all ownership information delivered from the organization service:
This change comes with multiple benefits for the customer:
Note that with this release we are also making some changes to the presentation of ownership in the PDF reports:
|
...
No | Changes | |||||
---|---|---|---|---|---|---|
1 | Information about BankID identification has been enhanced with more information about the related BankID certificate. In the PDF report the following elements are presented:
The following elements are added to the JSON response:
| |||||
2 | Fixed a bug in continuous screening which caused an error when adding persons. | |||||
3 | The lifespan of PDF reports has been increased to 30 minutes (from the previous 10 min). This is the deadline for when all reports must be downloaded before they are deleted from the server. | |||||
4 | Changes to the terms used in PDF reports regarding the organization types General Partnership and General Partnership with shared liability. "Aksjonærer" is renamed to "Deltakere" (English: Partners). Also, the percentage of ownership is removed from General Partnership. | |||||
5 | Adjustments to which scenarios the signature rights remark exceptions possible is added to the response. |
...
No | Changes |
---|---|
1 | Introducing a timeout of 9 seconds on the person and organization resource endpoints, so all requests can be excepted to give a response within this time limit. |
2 | Person report: Sanction results will contain an explicit note when the birth date is different than the search criteria. In the JSON response, a new data element "queryMismatch" is introduced to inform about the same thing. |
3 | Invalid organization number is handled as HTTP 400 bad request |
4 | Monitor: Introducing a new data element "hitType" on alerts. The enum comes in two variants:
|
5 | Person test data: search on date of birth is now possible |
6 | Organization test data: purpose is returned |
...