Skip to content

Latest commit

 

History

History
325 lines (199 loc) · 12.9 KB

File metadata and controls

325 lines (199 loc) · 12.9 KB

Changelog Know Your Customer

Table of Contents

Please be aware that the project will have frequent updates to the main branch. There are no compatibility guarantees associated with code in any branch, including main, until it has been released. For example, changes may be reverted before a release is published. For the best results, use the latest published release.

The below sections record the changes for each API version in each release as follows:

  • for an alpha release, the delta with respect to the previous release
  • for the first release-candidate, all changes since the last public release
  • for subsequent release-candidate(s), only the delta to the previous release-candidate
  • for a public release, the consolidated changes since the previous public release

r2.1

Release Notes

This release contains the definition and documentation of

  • kyc-match v0.3.0-rc.1
  • kyc-fill-in v0.3.0-rc.1
  • kyc-age-verification v0.1.0-rc.1

The API definition(s) are based on

  • Commonalities v0.5.0-rc.1
  • Identity and Consent Management v0.3.0-rc.1

kyc-match v0.3.0-rc.1

kyc-match v0.3.0-rc.1 is a release candidate version for the CAMARA KnowYourCustomer Match API

Added

  • Define a phoneNumber pattern in kyc-match yaml file by @GillesInnov35 in camaraproject#170

Changed

kyc-fill-in v0.3.0-rc.1

kyc-match v0.3.0-rc.1 is a release candidate version for the CAMARA KnowYourCustomer Fill-in API

Added

  • n/a

Changed

Fixed

kyc-age-verification v0.1.0-rc.1

Main Changes

  • First API proposal

Added

New Contributors

Full Changelog: https://github.com/camaraproject/KnowYourCustomer/compare/r1.4...r2.1

r1.4

Release Notes

This release contains the definition and documentation of

  • kyc-match v0.2.1
  • kyc-fill-in v0.2.0

The API definition(s) are based on

  • Commonalities v0.4.0
  • Identity and Consent Management v0.2.0

kyc-match v0.2.1

kyc-match v0.2.1 is the first initial version for the CAMARA KnowYourCustomer Match API

Main changes

  • Update test plan and remove unneeded scenario
  • There are no changes to the API definitions and API version numbers compared to r1.3

Changed

  • Update test plan and remove unneeded scenario by @fernandopradocabrillo in camaraproject#163

kyc-fill-in v0.2.0

kyc-fill-in v0.2.0 is the first initial version for the CAMARA KnowYourCustomer Fill-in API

Main Changes

  • No changes in kyc-fill-in in this release

Full Changelog: https://github.com/camaraproject/KnowYourCustomer/compare/r1.3...r1.4

r1.3

Release Notes

This release contains the definition and documentation of

  • kyc-match v0.2.1
  • kyc-fill-in v0.2.0

The API definition(s) are based on

  • Commonalities v0.4.0
  • Identity and Consent Management v0.2.0

kyc-match v0.2.1

NOTE: kyc-match v0.2.0 has been revoked and should not be considered due to a bug found in matchScore response property that makes this version not suitable. It is fixed in v0.2.1

kyc-match v0.2.1 is the first initial version for the CAMARA KnowYourCustomer Match API

Main changes

  • Includes Score functionality
  • Includes updated endpoint and API documentation
  • Includes test plan

Added

  • Include test plan for kyc-match operation by @fernandopradocabrillo in camaraproject#140

Changed

  • Remove countryMatchScore property by @fernandopradocabrillo in camaraproject#137
  • Update endpoint description to reflect all use cases by @fernandopradocabrillo in camaraproject#138

Fixed

Removed

  • n/a

kyc-fill-in v0.2.0

kyc-fill-in v0.2.0 is the first initial version for the CAMARA KnowYourCustomer Fill-in API

Main Changes

  • API definition updated to conform to the Commonalities v0.4.0 and Identity and Consent Management v0.2.0 guidelines included in the CAMARA Fall24 meta-release. No new features were added.

Added

  • Include test plan for kyc-match operation by @ToshiWakayama-KDDI in camaraproject#142

Changed

  • n/a

Fixed

  • n/a

Removed

  • n/a

New Contributors

  • n/a

r1.2

NOTE: Release r1.2 has been revoked due to a bug found in kyc-match v0.2.0 code. It is fixed in kyc-match v0.2.1 as part of r1.3 release.

r1.1

Release Notes

This release contains the definition and documentation of

  • kyc-match v0.2.0-rc.1
  • kyc-fill-in v0.2.0-rc.1

The API definition(s) are based on

  • Commonalities v0.4.0
  • Identity and Consent Management v0.2.0

kyc-match v0.2.0-rc.1

Added

Changed

  • Alignment of info, servers objects and security scope names by @rartych in camaraproject#114

Fixed

  • n/a

Removed

  • n/a

kyc-fill-in v0.2.0-rc.1

Main Changes

  • API definition updated to conform to the Commonalities v0.4.0 and Identity and Consent Management v0.2.0 guidelines included in the CAMARA Fall24 meta-release. No new features were added.

Added

  • n/a

Changed

  • Scope changed from know-your-customer:fill-in to kyc-fill-in:fill-in

Fixed

  • n/a

Removed

  • n/a

New Contributors

v0.1.1

This is a bugfix release for the first version of the KYC APIs.

Please note

  • This is an alpha version, it should be considered as a draft.

What's changed

Added

  • Update the description of the country field to reflect that the ISO 3166-1 alpha-2 format should be used.

Changed

N/A

Fixed

N/A

Removed

N/A

v0.1.0

This is the first alpha version of the KYC APIs.

  • Note: API documentation is embedded in the YAML files.

Please note:

  • This is an alpha version, it should be considered as a draft.

What's changed

  • New API KYC Match, v0.1.0, with a single operation for Match Identity:

    • compare the information it (Service Provider, SP) has for a particular mobile phone user with that on file (and verified) by the mobile phone user's Operator in their own KYC records, in order for the SP to confirm the accuracy of the information and provide a specific service to the mobile phone use.
  • New API KYC Fill-In, v0.1.0, with a single operation for Fill-In identity form:

    • request and receive the information for a particular user, which on file (and verified) by the user's Operator in their own KYC records, in order for the SP to confirm the accuracy of the information and provide a specific service to the user.