Move kyc-fill-in API to a stable status

[ToshiWakayama-KDDI]

As discussed during previous KYC-SP meetings, it may be interesting to see if kyc-fill-in 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.05)

[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,

Regarding the Stable v1.0.0 version of kyc-fill-in, I feel it is a bit premature. This is because there are only a few commercial implementations according to the GSMA Open Gateway Launch Map, and I also believe we have not yet had sufficient discussion on kyc-fill-in within the sub-project.

WDYT?

[albertoramosmonagas]

Hi, from TEF side, we support moving KYC Fill-in towards Stable v1.0.0, provided that the mandatory Stable readiness assets are completed and validated.

I agree that the market-adoption evidence seems more limited than for KYC Match. The GSMA Launch Map shows fewer visible commercial references, although there is at least visibility in Japan and we understand that Brazil has also been certified, even if the public map may not be fully up to date.

However, commercial adoption is a maturity signal, not the formal gating criterion for Stable. The formal gate should be 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.

KYC Fill-in is already at version 0.4.1 and has participated in several CAMARA meta-release cycles, so I would not use limited Launch Map visibility as an automatic blocker. If there are no specific functional blockers, TEF would support progressing KYC Fill-in to Stable v1.0.0 after validating the mandatory readiness assets.