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-Match: Matches the subscriber or phone user data? #124

Open
sfnuser opened this issue Aug 1, 2024 · 0 comments
Open

KYC-Match: Matches the subscriber or phone user data? #124

sfnuser opened this issue Aug 1, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@sfnuser
Copy link

sfnuser commented Aug 1, 2024

Problem description
This is more of a question rather than an issue - just to understand interpretations

API says An endpoint to verify the matching of a number of attributes related to a mobile phone user identity against the account data bound to their phone number

When this api is accessed, what is considered as the identity when an access token is issued - subscriber or the phone number?
Unlike some of the other device oriented APIs, this API returns the user details - are they associated with the subscriber or the phone number? For e.g a subscriber can have multiple phone numbers (all operated by the same subscriber) or the case where the multiple phone numbers are operated by different users (a family head being the subscriber and family members operating the phone or business account use cases)

What will be the sub field of the ID token returned - it identifies the subscriber or the phone user?

@sfnuser sfnuser added the enhancement New feature or request label Aug 1, 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

1 participant