Skip to content

Management of an optional threshold for tenureDate #56

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.

Sign up for GitHub

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

Merged
GillesInnov35 merged 3 commits into from
Feb 3, 2026
Merged

Management of an optional threshold for tenureDate #56

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3d14443
Management-of-an-optional-threshold-for-tenureDateCheck
GillesInnov35 Oct 17, 2025
e49260d
Update kyc-tenure.yaml
GillesInnov35 Nov 3, 2025
fb65702
Update kyc-tenure.yaml
GillesInnov35 Nov 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions code/API_definitions/kyc-tenure.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,8 @@ info:
- `tenureDate`: The date from which continuous tenure of the identified network subscriber is required to be confirmed. This field is always required.
- `phoneNumber`: The network subscription identifier (i.e. the phone number of the subscriber). This field is only required if no network subscription identifier is associated with the access token.

Note: MNOs may implement a threshold for the tenureDate aligned with their respective regulations. In that case if the tenureDate value in the request body is over the operator's threshold an error `400 OUT_OF_RANGE `is returned with an explicit message to explain the limitation.

## Outputs

If successful, a JSON object is returned containing the following data:
Expand Down