Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Current Challenge: Patients often need to share medical records and test results securely across different healthcare providers. This process is cumbersome, requiring manual handling of paper documents or insecure sharing via email and other communication channels.
Solution with Verifiable Credentials: Healthcare providers can issue VCs for vaccination records, allergies, or medication history. VCs can securely store and share medical records, test results, and vaccination history digitally. Patients can then easily share these credentials with other providers, ensuring continuity of care and faster treatment. Patients can control access to their data, ensuring only authorized healthcare providers can verify and access their information.
Benefits:
Reduced Friction: Patients can easily share verified medical credentials with healthcare professionals, streamlining the consultation and treatment process
Enhanced Privacy and Security: Verifiable credentials use cryptography to ensure data integrity and protect sensitive medical information
Current Challenge: Students often require verified academic transcripts and certificates when applying for further education or job opportunities, which they often carry physical transcripts or certifications. Requesting and verifying these documents can be time-consuming and prone to fraud.
Solution with Verifiable Credentials: Educational institutions can issue VCs such as digital diplomas, certificates, and transcripts. Students can share these credentials with potential employers or other educational institutions quickly and securely, streamlining verification and reducing wait times.
Benefits:
Efficient Verification: Employers and educational institutions can instantly verify the authenticity of academic credentials without relying on manual checks or third-party verification services
Prevention of Fraud: Verifiable credentials use cryptographic signatures to ensure the integrity and authenticity of educational documents, reducing the risk of forgery
Current Challenge: Customers often need to prove their identity and financial history when applying for loans, opening bank accounts, or accessing other financial services. This process typically involves submitting multiple paper documents and undergoing lengthy identity verification procedures.
Solution with Verifiable Credentials: Financial institutions can issue VCs that include identity information, credit scores, and financial history. Customers can use these credentials to securely and selectively share their information with authorized institutions.
Benefits:
Streamlined Onboarding Process: VCs enable faster and more efficient customer onboarding, reducing paperwork and administrative overhead for financial institutions
Enhanced Data Privacy: Customers have greater control over their personal and financial data, minimizing the risk of identity theft and unauthorized access
Current Challenge: Travelers often face challenges proving their identity and vaccination status when crossing borders. Paper-based documents are prone to loss or damage, leading to delays and disruptions during travel. Travelers juggle multiple documents for border crossings (passports, visas, health certificates) leading to delays and frustration.
Solution with Verifiable Credentials: Governments and health authorities can issue verifiable credentials for vaccination records, identity verification, and travel permissions. Travelers can present these digital credentials at checkpoints or border crossings securely and efficiently. These credentials can be easily accessed via mobile wallets and verified electronically, speeding up border processing and reducing queues.
Benefits:
Facilitated Cross-Border Travel: Verifiable credentials enable seamless verification of identity and vaccination status, reducing wait times and administrative hurdles at immigration checkpoints
Improved Public Health Measures: Authorities can track and verify vaccination records more effectively using digital credentials, supporting efforts to manage public health crises such as pandemics
Challenge: Job seekers often face delays due to lengthy background checks and verification of employment history and skills
Solution: Employers can issue verifiable credentials for past employment and skills acquired. Job seekers can then share these credentials with potential employers, allowing for faster verification and a smoother hiring process
Challenge: Citizens often need to present physical documents (birth certificates, proof of residence) to access government services, leading to inefficiency and potential loss of documents
Solution: Government agencies can issue verifiable credentials for citizen information. These credentials can be securely accessed and shared for various services, reducing administrative burdens and streamlining access
Reduced Friction: Verifiable credentials eliminate the need for physical documents, simplifying processes and speeding up transactions
Enhanced Security: Cryptographic verification ensures the authenticity and integrity of credentials, reducing the risk of fraud
User Control: Individuals control their data, choosing what information to share and with whom
Improved Efficiency: Streamlined workflows and faster access to services for both users and institutions
Verifiable credentials offer versatile solutions across various domains by leveraging digital technologies to enhance data security, privacy, and efficiency. By addressing common challenges associated with identity verification and data sharing, verifiable credentials empower individuals and organizations to streamline processes and improve trust in digital interactions.
In the rapidly evolving and interconnected world we live in today, ensuring widespread access to essential services such as healthcare, financial equality, global mobility, and support is of paramount importance. Central to accessing these services is the authentication of individuals' identities and the secure sharing of data to validate eligibility. Currently, individuals often juggle multiple physical identification documents and certificates, each necessary for various rights and services. It’s cumbersome for anyone to manage a pile of physical documents and can be prone to loss or fraud.
To gain a deeper understanding of the Inji ecosystem including Inji Wallet, Inji Verify, Inji Web, and the Inji Certify backend service you can watch the video titled 'Inji Stack End To End Usecase Demonstration'. This video provides a visual walkthrough of the features and a persona-based presentation for QR code-based verifiable credential (VC) verification.
The video will help you get a quick and comprehensive understanding of how Inji Stack operates and how each component works together to facilitate secure and efficient credential verification. You can access this video for further insights and a practical demonstration.
Inji (meaning "knowing" or "recognizance" in Korean) is evolving into a user-centric digital credential stack. It aims to streamline all types of credentials and identification solutions by enabling:
Secure issuance of verifiable credentials in both digital and physical formats
User-centric credential management: Empowering individuals to hold and share their credentials securely
Easy verification tools: Tools and utilities help verify the authenticity of credentials, simplifying the process of credential verification
Interoperability by leveraging global standards and specifications such as Verifiable Credentials Data Model (W3C VC) and OpenID for Verifiable Credential Issuance (OI4VCI) to enable various actors (governmental, social, and private market) to participate, offer solutions, and solve for diverse use-cases Trust and governance framework: Providing tools and services to foster trust and governance, ensuring a secure and reliable ecosystem for all
In Summary, Inji provides a complete solution for managing verifiable credentials across their entire lifecycle. It offers a suite of tools to Create, Issue, Manage, Share, Verify and Consume Credentials. Key modules include:
Inji Wallet: Secure, trustworthy, dependable, and decentralized mobile wallet enabling users to Download, Manage, Share, Verify verifiable credentials.
INJI Web: Easy to use web portal making credentials accessible to all, allowing users to download, print, store, and share verifiable credentials physically.
INJI Certify (issuance): Empowering issuers to create, sign, issue, bind, and store/hold verifiable credentials in multiple formats.
INJI Verify: Tools and utilities to consume and verify authenticity of credentials.
INJI Infra: Support essential functionality for Revocation, Ledger, Status, Resolution, Federation of verifiable credentials.
INJI Govern: Frameworks to define Policies, Schemas, Assurance, and Parties in context of verifiable credentials.
In essence, Inji is a comprehensive digital verifiable credentials' stack, designed to foster a high-trust, low-cost ecosystem..
Inji Wallet is a product of the combined efforts of multiple stakeholders. Contributions from the community form the backbone and drive its growth and stability. The contributions have come in multiple ways, ranging from direct code contributions, review of design and architecture, bug fixing, and support for technology evaluation.
For code contributions, refer here.
To engage with us on our community forum, visit here.
Open source projects can have a variety of contributors. This can potentially lead to confusion or conflict. This document sets forth a simple transparent set of guidelines to describe the roles and process to be followed. As part of that it covers:
Process of open source contributions and review of code in this project.
Decision-making process on backlogs and including contributions.
The MOSIP project follows a simple structure with 3 levels.
Level 1 - MOSIP Technology Committee. This committee is responsible for high level roadmap and policy decisions such as licensing, and technology stack.
Level 2 - Project leadership. This is the executive leadership at MOSIP that includes key project roles within MOSIP such as product owner, engineering lead, and architects. These members will be appointed as maintainers and lead in the project by MOSIP.
Level 3 - Members. This is a set of people who are working on the project.
Given below is a list of specific roles and their responsibilities.
Maintainers are individuals who have “Commit” rights; And are the primary caretakers of the code and the strategic vision of the project. They are empowered to make decisions and resolve disputes for all contributions. They are appointed by MOSIP.
Project Lead is the chair of the committee of maintainers. They are appointed by MOSIP.
Contributors are the people or organisations who take part actively in the project and its meetings, code, design, and test and are recognized for their contributions. The contributors are part of the GitHub Members and would be actively involved in the discussion of a PR and review. Members strongly influence the Maintainer's decision.
Members are either individuals or persons affiliated with contributing organisations. All contributions are bound by the licensing of the project.
Product Owner is responsible for the analysis, design, development, and implementation of business solutions to meet the needs of the organisation. He/She must have a strong understanding of the business domain, processes, and software development lifecycle Agile development methodologies).
Scope of Contributions
The whole of the project is open to contributions. The kind of contributions that are welcome include:
Code
Documentation
Design
Raising Bugs
Feature Request
Code, Documentation & Design
All artefacts including the code are maintained in the github repository.Contributions can be made by raising a Pull Request.
Reporting Issues & Feature Request
Issues and backlog are maintained in Jira and members of the project team will have access to Jira to add feature requests and report bugs
One off users will not have access for bug reports and feature requests. They can report the same in the community pages
Regular users who do not have access, can request the same and the maintainers can provide access after considerationWe use Jira to track the work associated with the project (account required). That is where issues open for community contribution can be found.Pull Request Review ProcessThe process to contribute the code is present here. Once code is submitted, it is reviewed through the following process:
We use Jira to track the work associated with the project (account required). That is where issues open for community contribution can be found.
The process to contribute the code is present here. Once code is submitted, it is reviewed through the following process:
At least two members should have reviewed the submitted contribution for the pull request to be accepted. The maintainers may request for more reviews of the code from other relevant members.
If the members deem the submitted code to be critical to overall product development, they can seek the inputs of the relevant product owners for the review process.
The maintainers review the two (or more) sets of comments received from the tech leads and the submitted code before taking a decision regarding committing the code to the appropriate branch.
The decision by the maintainer is communicated to the contributor via Jira as well as Pull Request.
In exceptional cases such as an emergency or an urgent requirement or a very trivial but time-sensitive correction, a maintainer may - at their discretion - choose to directly review the submitted pull request and take a decision on the commit.
Project Lead initiates the release process. The process can be found here.
Attribution is in accordance with the relevant licence. Individual and affiliated contributors will be listed.
The key decisions to be taken are for the following activities
Roadmap and backlog priority
Triaging of bugs and requirements
Accepting a contribution Pull Request)
Releases
Most decisions will be made in periodical meetings where owners of the relevant aspect of work present a case for a decision and the decision will be made either by consensus, or by majority where a quorum exists. The maintainers of the project will be the decision makers. The project lead will have veto power on decisions due to their expertise and commitment to the vision of the project. Contributors can share their views in these meetings for consideration.
Community was created to foster an open, innovative and inclusive community around open source & open standards. To clarify expected behaviour in our communities we have adopted the Contributor Covenant. This code of conduct has been adopted by many other open-source communities and we feel it expresses our values well.
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, colour, religion, or sexual identity and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
Examples of behaviour that contributes to a positive environment for our community include:
Demonstrating empathy and kindness toward other people
Being respectful of differing opinions, viewpoints, and experiences
Giving and gracefully accepting constructive feedback
Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
Focusing on what is best not just for us as individuals, but for the overall community
Examples of unacceptable behaviour include:
The use of sexualized language or imagery, and sexual attention or advances of any kind
Trolling, insulting or derogatory comments, and personal or political attacks
Public or private harassment
Publishing others' private information, such as a physical or email address, without their explicit permission
Other conduct which could reasonably be considered inappropriate in a professional setting
Community leaders are responsible for clarifying and enforcing our standards of acceptable behaviour and will take appropriate and fair corrective action in response to any behaviour that they deem inappropriate, threatening, offensive, or harmful.
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
This Code of Conduct applies within all community spaces and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
Instances of abusive, harassing, or otherwise, unacceptable behaviour may be reported to the community leaders responsible for enforcement at MOSIP. All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
Community Impact: Use of inappropriate language or other behaviour deemed unprofessional or unwelcome in the community.
Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behaviour was inappropriate. A public apology may be requested.
Community Impact: A violation through a single incident or series of actions.
Consequence: A warning with consequences for continued behaviour. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
Community Impact: A serious violation of community standards, including sustained inappropriate behaviour.
Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behaviour, harassment of an individual, or aggression toward or disparagement of classes of individuals.
Consequence: A permanent ban from any sort of public interaction within the community.
This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.
For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
The recommended Github workflow here is for developers to submit code and documentation contributions to Inji open-source repositories.
Fork the repository.
Clone the fork to your local machine. E.g.:
Set the upstream project as the original from where you forked. E.g.:
Make sure you never directly push upstream.
Confirm the origin and upstream.
This should display origin and upstream as below:
1. Create a new issue in GitHub.
Follow the issue template provided.
Please provide as much information as possible.
If you want to develop a new feature, please elaborate on the idea and discuss the design before starting development. 2. In your local repository, fetch the upstream.
3. On your local repo, switch to a branch if you are working on an older release or stay in main/develop
branch.
You will get a warning from git. Don't worry, our next step will take care of this warning.
4. Create a new issue branch with the name of the issue.
5. Make sure you are up-to-date with the upstream repo.
You should do this quite often to ensure you are up to date.
6. Now feel free to make the change in the code or documentation. Reach out to our community for any queries. Once done with the work, commit your changes by referring to the Issue ID in the commit message. Eg:
7. Once again ensure that you are up-to-date with the upstream repo as it may have moved forward.
8. Build and test your code. Make sure to follow the coding guidelines. Provide unit test cases for the changes you have built.
9. Push to your forked repo (origin).
10. On your forked remote repository from GitHub, create a pull request using the Contribute button. Direct the pull-request to main
or any specific branch upstream.
Most often it's the same branch in the upstream (as in Step 3).
11. Make sure the automatic tests/checks on GitHub for your pull request pass.
12. Reviewers shall review the pull request. Reach out to the community for a faster response.
The documentation is licensed under a Creative Commons Attribution 4.0 International License.
All MOSIP's core repositories are licensed under the terms of Mozilla Public License 2.0.
All trademarks are the property of their respective holders. Other products and company names mentioned herein may be trademarks and/or service marks of their respective owners.
Q1: Jan24 - Mar24
Q2: Apr24 - Jun24
Q3: Jul24 - Sep24
Q4: Oct24 - Dec24
Q1: Jan24 - Mar24
Q2: Apr24 - Jun24
Q3: Jul24 - Sep24
Q4: Oct24 - Dec24
Q1: Jan24 - Mar24
Q2: Apr24 - Jun24
Q3: Jul24 - Sep24
Q4: Oct24 - Dec24
Q1: Jan24 - Mar24
Q2: Apr24 - Jun24
Q3: Jul24 - Sep24
Q4: Oct24 - Dec24
Welcome to the "Try It Out" section! Here, we offer you hands-on experience to better understand how our product works and how you can leverage its features. This section will guide you through some simple steps to get started.
If you're a developer or a partner interested in experiencing or integrating with Inji Web, we invite you to explore our designated sandbox environments.
Collab serves as our development integration environment, featuring QA-tested dockers. It's a dedicated space where our partners and contributors can build on the platform or integrate with the latest QA-tested version of the code.
This environment undergoes regular nightly builds from our engineering team, making it a hub for continuous development activities.
Access resources on Collab, our sandbox environment, through the provided link.
Synergy: Stable Integration Environment
Synergy represents our stable environment, where the most recently released version of the MOSIP platform and applications are deployed for partners to seamlessly integrate and conduct testing.
For quick access to environment related resources, please visit the provided link.
If you require any assistance or encounter any issues during the testing and integration process, kindly reach out to us through the support mechanism provided below.
Navigate to Community.
Provide a detailed description about the support you require or provide detailed information about the issue you have encountered, including steps to reproduce, error messages, logs and any other relevant details.
Explore the Try it Out sections of Inji Modules from below:
\
Quarter
Feature
Status
Feature Details
Release Details
Q1-Q4
Threat modelling.
In-progress
Q1
Abstract INJI features (Tuvali, Secure-keystore) in to SDK/NPM libraries
Completed
Q1
Sunbird RC - Issuer integration
Completed
Q1
User data backup
Completed
Q1-Q2
INJI new UI - Gendermag (P1, P2, P3)
Completed
Q2
Different Views of Cards
Completed
Q2
VC Sharing Flow Optimisation
Completed
Q2
Credential Type Selection
Completed
Q2
VC Verification
Completed
Q2
QR Code Generation (PixelPass)
Completed
Q3
Native artefacts:
inji-vci-client
Secure keystore
Tuvali
PixelPass
Completed
Q3
Ease of Deployment
In-progress
Q3
Inji Certify Integration
In-progress
v0.14.0
Q3
Draft 13 changes of OpenID4VCI spec
In-progress
v0.14.0
Q3
Java upgrade to 21
In-progress
v0.14.0_Mimoto:
Q4
OpenID4VP
In-progress
v0.15.0
Q4
VC render spec based wallet rendering
In-progress
v0.15.0
Q4
OpenID4VP for BLE: Implementation of non QR based sharing as per OpenID for BLE specification
In-progress
v0.15.0
Q4
Support for different VC formats and proof types
In-progress
v0.15.0
Q4
Data Model 2.0
In-progress
v1.0.0
Q4
Performance Testing
In-progress
v1.0.0
Q4
Security Testing
In-progress
v1.0.0
Q4
OpenID4VCI enhancements
In-progress
v1.1.0
Q4
Wallet Login
In-progress
v1.1.0
Q4
BBS+ support
In-progress
v1.1.0
Quarter
Feature
Status
Feature Details
Release Details
Q2
Fetch & download credentials in PDF format
Issuer and credential type selection
Completed
Q2
Localization
Completed
Q2
Responsive View
Completed
Q2
Theme customization
Completed
Q2
Tech Upgrades:
Movement from Material UI to Tailwind
Conversion of JS to TS
Completed
Q2
QR Code in PDF
In-progress
v0.10.0
Q2
Online Sharing
In-progress
v0.10.0
Q2
Persistent storage
In-progress
v0.10.0
Q3
Secure time bound storage
Planned
v1.0.0
Q3
Performance Testing
Planned
v1.0.0
Q3
Security Testing
Planned
v1.0.0
Q3
Web UI enhancements:
Home Page
svg template in PDF
Planned
v1.0.0
Q4
User login, VC management, profile management (profile menu)
In-progress
v1.1.0
Q4
VC Validation & Verification
Planned
v1.1.0
Q4
OpenID4VCI enhancements
Planned
v1.1.0
Q4
Categorization of issuers
Planned
v1.2.0
Q4
mDoc/mDL & CBOR VC download
In-progress
v1.2.0
Quarter
Feature
Status
Feature Details
Release Details
Q2
Easy deployment of Inji Certify v0.8
Docker compose for Sunbird and eSignet for Verifiable Credential Issuance
Helm charts for Sunbird and eSignet.
Completed
Q2
Inji Certify - Base code v0.9
Publish as an independent module (VCI + C)
VCI segregation from eSignet and moving to Inji Certify.
Plugin Support :
MOSIP Identity Plugin
Sunbird Plugin
Mock Identity Plugin
Implementors Draft 13 OpenIDVCI
In-progress
Q3
Movement to Data Model 2.0
In-progress
v0.10.0
Q3
OpenID for Verifiable Credential Issuance - draft 13 Spec
Pre-Authorized Code Flow
Credential Offer End Point
In-progress
v0.10.0
Q3
VC Generation: Create Credentials from the Request Payload
W3C VC Issuance API
Planned
v0.10.0
Q3
Simplify the process of onboarding an issuer for a single entity
Planned
v0.11.0
Q3
Multi-tenancy: Onboarding of multiple issuers
Planned
v0.11.0
Q3
Persistent store for credentials
Pre-generated credentials
Credentials Registry (Hosted Infra)
Planned
v0.11.0
Q4
Issue a physical credential (PDF / Printable)
Support PDF or other formats of presentation based on plugins - PDF, PCF, PKPASS
Planned
v0.11.0
Q4
Vault Integration - Key manager support
Planned
v0.12.0
Q4
Vault - Key management
Planned
v0.12.0
Q4
Revocation Mechanism
Planned
v0.12.0
Q4
Discovery and Metadata
DNS based Well Known specifications for publishing PK, Schema, credential types and other meta data (Proposed by MOSIP and included in standards)
Planned
v0.12.0
Q4
Allow Bulk/Batch Issuance
Issue certificates from an existing database
Planned
v0.12.0
Q4
Deferred Credential Endpoint
OpenIDVCI - Draft 13
Planned
v0.12.0
Q4
Inji Certify - Beta 1 - LTS
Planned
v1.0
Q1-Q4
Extend Credentials
Ability to issue extension on existing credential
Moved to 2025
Depriortized
Q1-Q4
Credential Correction
Support to retire the old credential and issue the new credential
Moved to 2025
Depriortized
Q1-Q4
Credential Formats Support - Selective Disclosure - Support SD JWT
Moved to 2025
Depriortized
Q1-Q4
[Credential Formats Support - Support mDocs
Moved to 2025
Depriortized
Q1-Q4
Business models (central, third-party SaaS, self-hosted)
Moved to 2025
Depriortized
Quarter
Feature
Status
Feature Details
Release Details
Q2
Web-based VC Verification functionality
Completed
Q2
UI/UX Enhancements based on GenderMag
Completed
Q2
Mobile Responsive Version - Upload and Scan feature
Completed
Q2
Material UI to Tailwind
Completed
Q2
Bug Fixes
Completed
Q3
Request Credential - OpenIDVP - OVP Flow
In-progress
v0.10.0
Q3
Docker Compose
In-progress
v0.10.0
Q3
Support for Country QR code - CWT Format
In-progress
v0.11.0
Q3
Verification SDK
In-progress
v0.11.0
Q3
Displaying Issuer Details post validation on UI
On-Hold
v0.11.0
Q3
Templatizing post-VC verification on Inji Verify(Render)
Planned
v0.11.0
Q3
Receive Credentials
(QR-based Verifiable Presentation)
Planned
v0.11.0
Q4
Multi-lingual UI Support - Localization
Planned
v0.12.0
Q4
VP requestor SDK
Planned
v0.12.0
Q4
Consume Data from credential
Planned
v0.12.0
Q4
Production Ready - Inji Verify - LTS Release 1.0.0
Planned
v1.0
Q1-Q4
BLE based verifiable presentation
Moved to 2025
Depritoritized
Q1-Q4
Credential Correction
Moved to 2025
Depritoritized
Q1-Q4
Revoked Credentials
Moved to 2025
Depritoritized
Q1-Q4
VC Reciever SDK
Moved to 2025
Depritoritized
Q1-Q4
Upload document(pdf) with multiple QR Codes
Moved to 2025
Depritoritized
Q1-Q4
Verify mDoc and mDL
Moved to 2025
Depritoritized
Q1-Q4
Mobile App (Login with Inbox & Logout)
Moved to 2025
Depritoritized
Q1-Q4
Offline Verification SDK
Moved to 2025
Depritoritized