r2.1

Release Notes

This release candidate contains the definition and documentation of

• kyc-match 0.5.0-rc.1

The API definition(s) are based on

• Commonalities 0.8.0
• Identity and Consent Management 0.5.0

kyc-match 0.5.0-rc.1

kyc-match 0.5.0-rc.1 is a release-candidate version of this API.

Changes documented below are compared to version 0.4.0.

• API definition with inline documentation:
  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Breaking changes

• Replace 403 INVALID_TOKEN_CONTEXT with 422 UNNECESSARY_IDENTIFIER by @GillesInnov35 in #84
• Previously, when the API consumer provided both a 3-legged access token and an explicit phoneNumber, the API would return 403 INVALID_TOKEN_CONTEXT if they did not match, but proceed as normal if they did match.
• Now, the API will always return 422 UNNECESSARY_IDENTIFIER if both a 3-legged access token and an explicit phoneNumber are provided. This will be a breaking change for those API consumers who provide a matching 3-legged access token and phoneNumber - their API calls would have succeeded before, but now they will fail.

Added

• Add bankaccountnumber as an attribute to KYC Match by @ToshiWakayama-KDDI in #73

Changed

• Alignment with Guidelines and linting rules for OWASP API Security by @GillesInnov35 in #72
• Commonalities 8.0.0 alignment and fix validation warnings by @GillesInnov35 in #81
• Replace 403 INVALID_TOKEN_CONTEXT with 422 UNNECESSARY_IDENTIFIER by @GillesInnov35 in #84
• Another update to fix validation warnings by @GillesInnov35 in #83

Fixed

• Correction of test definitions by @GillesInnov35 in #58

Removed

• Remove idDocument related errors by @fernandopradocabrillo in #54
• Remove Flows Image from yaml file by @GillesInnov35 in #64

Full Changelog: r1.2...r2.1