Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KYC-Fill-in: When provider decides which information to not send - expected response/Output? #133

Open
Natylee93 opened this issue Aug 13, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@Natylee93
Copy link

Problem description

Hi, I was reading the KYC fill in documentation and a question came up.
In the Know Your Customer fill in(v0.2.0-rc.1) document, it says it is up for the Provider to decide which information the 3rd Party will receive,

Possible evolution

Which is the expected response/output in this case? Will it not have a response and not send the parameter or should it send the parameter with a blank value?

Thank you in advance!

@Natylee93 Natylee93 added the enhancement New feature or request label Aug 13, 2024
@Natylee93 Natylee93 changed the title When provider decides which information to not send - expected response/Output? KYC-match: When provider decides which information to not send - expected response/Output? Aug 13, 2024
@ToshiWakayama-KDDI
Copy link
Collaborator

Thank you, @Natylee93 .

It seems that your question is about KYC Fill-in, not KYC Match.

As KYC Fill-in API specification, which parameters to send is up to API provider/ Network Operator, because it may be related to national/market regulation, API provider/Network Operator's privacy policy and so on.

For KDDI, when we make contract with 3rd party customers (API users), it is fixed which parameters are to be sent to each of them. When a 3rd party customer calls the KYC Fill-in API, we will send the fixed parameters only with values, based on the contract with the 3rd party customer. It means we will not send the parameter with a blank value.

I hope this could help you.

Best regards,
Toshi

@Natylee93 Natylee93 changed the title KYC-match: When provider decides which information to not send - expected response/Output? KYC-fill-in: When provider decides which information to not send - expected response/Output? Aug 20, 2024
@Natylee93 Natylee93 changed the title KYC-fill-in: When provider decides which information to not send - expected response/Output? KYC-Fill-in: When provider decides which information to not send - expected response/Output? Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants