Versions Compared

Version Old Version 48 New Version 49
Changes made by

Kristoffer Skaret (Unlicensed)

Janny Kinende

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space PDOIDC and version master

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 V72

Release date: 2022-06-21

NoChanges
1The 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.
2Removed information about fuzzy mode from the Person PDF report.
3Changed 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.
4Fixed a bug causing duplicate error messages about roles in the Person PDF report.

Changes in V71

Release date: 2022-06-08

NoChanges
1

Added support for organization search against Denmark.

See further documentation about:

2Added information about missing response elements in the PDF reports when an error occurs. This optional error message can be present in any chapter.
3

Changed the validation pattern for Swedish SSN in the person search. The standard ÅÅMMDD-XXXX format is now supported. Note that the special variant ÅÅMMDD+XXXX is currently not supported.

Also added validation of SSN (NO, SE, DK, FI) in the monitor API.

Changes in V70

Release date: 2022-05-20

NoChanges
1

Improved the name matching algorithm in searches against the Norwegian population registry. The name matching can now return successful results even for inputs consisting of initials or name parts not present in the registration.

Changes in V69

Release date: 2022-05-12

...

NoChanges
1

The reason to be a beneficial owner is now also returned as part of the JSON API response.

Three new fields are introduced:

  1. reason : Enum describing the reason
  2. reasonPhrase : Text description of the reason. Same as is presented in the report, in the same language.
  3. integratedOwnership: Share of integrated ownership.

In addition, the existing field percentageControl is adjusted to only return a value in cases where the share of control clearly can be described with a number. (Typically this is null when reason is a role or indirect control).

2

Improved support for AML search after persons with nationality other than Norwegian.

  • the input parameter ssn now supports national ID number for the countries Norway, Sweeden, Denmark, and Finland.
  • if a Swedish nationality is given, a Sanction/PEP result with match quality of 500 (full ssn match) is possible.
  • The input parameter countryOfSsn is deprecated and replaced with the more syntactically correct parameter country. Both parameters are supported and have the same effect.
Info
Note that if an ssn is not present, an input consisting of only the name and dateOfBirth parameters are sufficient. This can lead to PEP/Sanction match results for any international person.
Info
Information from national registers, such as an address, is still only available for Norwegian citizens. Similar support will be added for other Nordic countries in a future release.
3Beneficial owners are described with an address when the information is available. (both PDF and JSON)
4Unidentified beneficial owners are described with a country when that information is available. (both PDF and JSON)

...

NoChanges
1

Switched to T-rank as the source of all ownership information delivered from the organization service:

  • Beneficial owners
  • Direct owners
  • Subsidiaries

This change comes with multiple benefits for the customer:

  • Improved data quality
  • Calculation of beneficial owners is in accordance with the updated rule set in The Anti-Money Laundering Act.
  • All ownership information is now completely in sync with the present ownership indicators calculation

Note that with this release we are also making some changes to the presentation of ownership in the PDF reports:

  • The list of owners is limited to the 20 with the biggest ownership.
  • All ownership chapters are included even if the listed content is empty.
  • Visual improvements

...

NoChanges
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:

  • Timestamp (time of authentication)
  • Certificate serial number (serial number of the BankID certificate)
  • Organization (Issuer of the BankID certificate)
  • Organizational Unit (Organization number of the issuer)

The following elements are added to the JSON response:

  • originator (complete originator String, similar to the one delivered as part of the ID Token)
  • serialNumber (BankID serial number, similar to bankid_altsub in the ID Token)
Info
titleExample originator string
CN=BankID Bankenes ID-tjeneste Bank CA 2,
OU=988477052,
O=Bankenes ID-tjeneste AS,*
C=NO;OrginatorId=9775;OriginatorName=Gjensidige Bank RA 1
2Fixed a bug in continuous screening which caused an error when adding persons.
3The 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.
4Changes 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.

...

NoChanges
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.

3Invalid 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:

  • MATCH: the person has been added to a sanction or PEP list
  • REMOVED: the person has been removed from a sanction or PEP list
5

Person test data: search on date of birth is now possible

6Organization test data: purpose is returned

...