New API Enhancement Proposal KYC-Match Scoring #46
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jgarciahospital
requested review from
TEF-RicardoSerr,
NoelWirzius and
caubut-charter
as code owners
|
Hi Jorge, Looks good to me, except for one point. According to related discussions in KnowYourCustomer SP, some operators and markets (including Japan) do not need 'Scoring' for KYC Match, so, the enhanced Match API should be able to work without Scoring. If you could add this point to the template, it would be much appreciated. (Same comment for Issue #45) Best regards, |
|
To be closed and merged, as agreed in camaraproject/KnowYourCustomer#85 |
|
@camaraproject/api-backlog_codeowners |
|
@caubut-charter can you please approve and merge? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
API template for enhancement on the KYC-Match API
Which issue(s) this PR fixes:
Fixes #45