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 each first alpha or release-candidate API version, all changes since the release of the previous public API version
- for subsequent alpha or release-candidate API versions, the delta with respect to the previous pre-release
- for a public API version, the consolidated changes since the release of the previous public API version
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
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
- API definition with inline documentation:
Main changes
- Includes Score functionality
- Includes updated endpoint and API documentation
- Includes test plan
- Include test plan for kyc-match operation by @fernandopradocabrillo in camaraproject#140
- Remove countryMatchScore property by @fernandopradocabrillo in camaraproject#137
- Update endpoint description to reflect all use cases by @fernandopradocabrillo in camaraproject#138
- Fix score type and change version by @fernandopradocabrillo in camaraproject#148
- n/a
kyc-fill-in v0.2.0 is the first initial version for the CAMARA KnowYourCustomer Fill-in API
- API definition with inline documentation:
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.
- Include test plan for kyc-match operation by @ToshiWakayama-KDDI in camaraproject#142
- n/a
- n/a
- n/a
- n/a
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.
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
- Include score functionality by @fernandopradocabrillo in camaraproject#104
- Alignment of info, servers objects and security scope names by @rartych in camaraproject#114
- n/a
- n/a
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.
- n/a
- Scope changed from
know-your-customer:fill-in
tokyc-fill-in:fill-in
- n/a
- n/a
- @rartych made their first contribution in camaraproject#114
- @jgarciahospital made their first contribution in camaraproject#111
This is a bugfix release for the first version of the KYC APIs.
- API definition
- This is an alpha version, it should be considered as a draft.
- Update the description of the
country
field to reflect that the ISO 3166-1 alpha-2 format should be used.
N/A
N/A
N/A
This is the first alpha version of the KYC APIs.
- API definition
- Note: API documentation is embedded in the YAML files.
- This is an alpha version, it should be considered as a draft.
-
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.