Move kyc-age-verification API to a stable status

[ToshiWakayama-KDDI]

As discussed during previous KYC-SP meetings, it may be interesting to see if kyc-age-verification API should be moved to a stable status regarding how it is adopted and implemented by operators in countries.

(Note: KYC SP Action Item #48.06)

[ToshiWakayama-KDDI]

Hi all,

During our meeting on 2026-04-28, @albertoramosmonagas kindly shared the following information:

(1) Mandatory task to move to stable:

• API Definition,
• Commonalities compliance,
• API documentation,
• User stories,
• Test cases (basic),
• Test Cases (enhanced),
• API Description (wiki)

(2) And also:

• Demonstrate long-term specification maturity by having participated within two CAMARA release cycles with at least one Stable API version.
• Demonstrate wide market adoption across multiple companies or projects, by demonstrating that the API has been deployed within at least one complete market or by #n operators across #m markets.
• Maintainers of the Incubating Repository apply for Graduation by opening an issue in the API Backlog working group.
• The API Backlog working group will do a pre-check on behalf of the TSC, which will confirm (or not) the inclusion of the repository as Graduated.

Information is here: https://github.com/camaraproject/Governance/blob/main/documentation/API-Onboarding-and-Lifecycle.md#3-graduated-stage
camaraproject/Commonalities#589

My understanding of the above is that:

• The items in (1) are included in the API Readiness Checklist.

• Regarding the items in (2), by clicking the link 'Information is here', I can see these four bullets in '2. Incubating Stage' and these are requirements for Transition from 'Incubating Stage' to 'Graduated Stage'.

If my understanding is correct, the items in (1) are mandatory tasks for releasing a Stable API version, and the items in (2) are not required for this.

Best regards,

[ToshiWakayama-KDDI]

Hi all,

Here is my opition regarding the Stable v1.0.0 version of kyc-age-verification.

Current implementation status according to the GSMA Open Gateway Launch Map:
BT (v0.1.0), Drei Austria (v0.1.0), KDDI (v0.1.0), KPN (v0.2.1, v0.1.0), Three Ireland (v0.2.0), Three UK (v0.1.0), VMO2 UK (v0.1.0), VDF UK (v0.2.1), Wind3 IT (v0.1.0)

There have already been several commercial implementations according to the GSMA Open Gateway Launch Map, so, we may be able to apply for the Stable Version of Age Verification. However, some of the major contributors to the sub-project, such as Orange, DT, and Telefonica, have not implemented it yet. Therefore, my proposal is that, if the sub-project agrees, let's aim to release the stable version for Sync26.

WDYT?

[albertoramosmonagas]

From TEF side, we support moving KYC Age Verification towards Stable v1.0.0 for Sync26, provided that the mandatory Stable readiness assets are completed and validated.

The API already shows a reasonable maturity level: it has participated in several CAMARA meta-release cycles, and the GSMA Open Gateway Launch Map shows commercial adoption across multiple markets and operators. Even if the map may not be fully up to date, the visible adoption signal is strong enough to justify progressing the API to Stable assessment.

I would separate this from the later Graduation discussion. For Stable v1.0.0, commercial adoption is a useful maturity signal, but the formal gate should remain the Stable Public API readiness checklist: API definition, Commonalities/ICM alignment, API documentation, user stories, basic and enhanced test cases, API description, release plan, etc.

The fact that some major contributors have not yet implemented the API should not automatically block Stable status. Unless there are unresolved functional issues or expected non-backward-compatible changes, TEF supports targeting KYC Age Verification v1.0.0 Stable for Sync26.

[GillesInnov35]

as you say @ToshiWakayama-KDDI items (1) are all covered/included in the API Readiness Checklist.
I'm a bit uncomfortable with the fact that not many MNO/contributors have not yet implemented the API even if it's actually a important current need. Does it mean the API design is not in line with what king of information related to age verification operators could return ?
Nevertheless regarding item bellow, I support updating the API to Stable v1.0.0.

Demonstrate long-term specification maturity by having participated within two CAMARA release cycles with at least one Stable API version.

Thanks
Gilles

[ToshiWakayama-KDDI]

Thanks @GillesInnov35 . It was just my observation. We have enough number of Age Verification implementation according to the GSMA launch map as I wrote above, however, I am a bit worried about no Orange, TEF, DT's implementation. But, as Alberto TEF and Gilles Orange support updating the API to Stable v1.0.0 in Sync26 as above, it seems fine. Let's aim at Stable v1.0.0 in Sync26.

[albertoramosmonagas]

Hi! At Telefónica, we provide support to Virgin Media O2 in the UK for age verification for version 0.1.0

[ToshiWakayama-KDDI]

Hi @tanjadegroot , @hdamker , @eric-murray ,
cc: @GillesInnov35 , @fernandopradocabrillo , @albertoramosmonagas ,

First of all, thank you for your continuous support of our release activities.

We, the KYC Age Verification sub-project team, have reached a consensus in Discussion #36 to transition the API to a stable version (v1.0.0) for the upcoming Sync26 release.

We have reviewed the API Readiness Checklist and believe we understand the requirements for a stable release. However, we would be grateful if you could advise us on the official procedure to make this happen.

For example, is the process as simple as us starting to use the v1.0.0 version number for our next Release Candidate (RC) and the subsequent public release? Or are there other specific steps we need to take?

We would appreciate your guidance on this.

Best regards,
Toshi

[tanjadegroot]

Hi all, the same process as provided by Herbert here can be applied: camaraproject/KnowYourCustomerMatch#48 (comment)

[GillesInnov35]

Thanks @tanjadegroot , it has just been done.