The Short Answer
A learner wallet is a digital record the person keeps, holding the degrees, certificates, badges, licenses and skills they have earned as signed credentials an employer can verify without contacting the issuer. Platforms that offer one include WGU's Achievement Wallet, Credly, the open-source Learner Credential Wallet and ibl.ai's Agentic Wallet, where you own all the code and the data.
The two standards underneath are the W3C's Verifiable Credentials Data Model v2.0, a W3C Recommendation since May 15, 2025, and 1EdTech's Open Badges 3.0, which aligns with that data model.
A learner wallet is not a payments wallet. If you came for wallets that let AI agents pay for things, that is a different story, covered in AI agents are getting wallets.
What is a learner wallet for skills and credentials?
A learner wallet for skills and credentials is software that stores a person's achievements as credentials they hold and choose to share. The W3C model names three roles: an issuer that asserts claims, a holder that keeps the credentials, and a verifier that receives them.
In a learner wallet the holder is the person who earned the credential. A university, an employer's training team or a licensing body is the issuer. A hiring manager, a graduate program or a regulator is the verifier.
The difference from a transcript or a PDF certificate is the signature. A verifiable credential carries a cryptographic proof, so a verifier can check who issued it and that nobody altered it, without a records request.
Jobs for the Future calls these collections Learning and Employment Records, or LERs. JFF describes digital wallets as critical technology infrastructure for shifting to skills-first hiring practices.
Is a learner wallet only for students, or for employees too?
A learner wallet serves anyone who learns, which includes employees as much as students. The record follows the person, so a nurse's license, a technician's safety certification and an engineer's cloud badge belong in the same wallet as a degree.
WGU shows the horizontal reach in practice. When it launched its Achievement Wallet on September 10, 2025, it opened it to more than 588,000 students and alumni and to its nearly 10,000 employees.
The JFF demonstration project with veterans made the same point from the workforce side. Veterans collected training records, occupational badges and military service documents in a wallet and shared them with a civilian talent platform.
How do Open Badges 3.0 and W3C Verifiable Credentials fit together in a learner wallet?
Open Badges 3.0 and W3C Verifiable Credentials are layers of one stack.
The W3C defines the general shape of a signed, verifiable claim; 1EdTech's Open Badges 3.0 defines what an achievement looks like inside that shape, and its abstract says it aligns with the Verifiable Credentials Data Model v2.0.
That alignment is why a badge issued as Open Badges 3.0 can sit in a general-purpose credential wallet. Open Badges 2.0 badges are typically hosted assertions checked against the issuer's own URL, so a wallet that accepts both should say which is which.
JFF's interoperability work builds on W3C Verifiable Credentials, with Open Badges v3 and European Learning Model v3 credentials among those tested.
Its three plugfests, in June 2022, November 2022 and October 2023, drew 39 organizations testing that their wallets and issuers worked together.
Why do learner wallets still disagree about whether a credential is verified?
Learner wallets still disagree because the format is standard while each application reads it in its own way. In JFF's veterans demonstration with eight partners, the same credential showed as "verified" in one wallet and "unverified" in another.
The same report lists the other failure points a buyer should test: credentials that appeared only after staff approval, transfers that failed with vague errors, and QR-code sharing that behaved differently on Android and iPhone.
The lesson for a buyer is to test verification end to end with your own issuers and your own verifiers, not to accept a standards logo as proof. A wallet is only as useful as the hiring manager's ability to trust what it shows.
Which platforms offer a learner wallet for skills and credentials?
Several platforms offer a learner wallet for skills and credentials, and they differ most on who holds the record and who runs the software. The table below lists four, each described from its own published material.
| Platform | What it is | Standards it names | Who runs it |
|---|---|---|---|
| WGU Achievement Wallet | Skills, credentials and experience in one record, skill gaps against careers, a generated résumé | Not named in the launch release | WGU, on technology developed by iQ4, for its own students, alumni and employees |
| Credly | A hosted profile for digital badges, with upload and verification of badges from other platforms | Open Badges 2.0 and 3.0 | Credly, in its own cloud |
| Learner Credential Wallet | An open-source iOS and Android app to store and share credentials | W3C Verifiable Credentials | The holder's phone; built by MIT with the Digital Credentials Consortium |
| ibl.ai Agentic Wallet | Credentials from every source in one record, skills mapped to roles, a résumé drafted from the record by the platform's agent | Open Badges 2.0 and 3.0, W3C Verifiable Credentials | You: MIT-licensed code on infrastructure you choose |
WGU's press release reports early users' views: 87% valued having their career and education information in one place, and 78% said seeing skill gaps helped them understand how they qualify for jobs.
Credly announced on October 16, 2024 that earners can upload and verify any badge built to Open Badges 2.0 or 3.0, whichever platform issued it.
MIT Open Learning describes the Learner Credential Wallet as built under a 2020 agreement with the U.S. Department of Education, with its full source code on GitHub.
What should you ask before choosing a learner wallet platform?
Before choosing a learner wallet platform, ask four questions, each tied to a failure point the sources above document. They apply whether the holders are students, alumni or employees.
| Question | Why it matters |
|---|---|
| Who holds the record? | If the issuer's subscription ends, a record held by the vendor can go with it |
| How is a credential verified, and does revocation reach every share? | JFF saw one credential read as verified and unverified in two wallets |
| Does it import and export Open Badges 3.0? | A wallet that only reads its own format traps the record |
| Who owns the code and the data? | Ownership decides where the record lives and how pricing scales |
Pricing shape belongs in the same conversation. A hosted service priced per badge or per seat grows with every credential and every person, whether or not anyone shares them; a usage-based or flat license does not.
How does ibl.ai's Agentic Wallet handle skills and credentials?
ibl.ai's Agentic Wallet is an open-source credential wallet, published under the MIT license at github.com/iblai/wallet, that keeps every credential a person has earned in their own ibl.ai profile, across every organization they belong to.
Credentials arrive from three places, and the wallet says which is which.
Credentials issued on ibl.ai verify live against the platform's public assertion endpoint.
Imported Open Badges 2.0 or 3.0 badges, from Credly, Badgr, Canvas Credentials or any hosted badge, carry the issuer's link. Self-reported records are labelled self-reported everywhere.
Revocation reaches every share link: a revoked credential shows as revoked, with its reason. A person can share the whole record, a collection for one application, or a single credential, and export as Open Badges 3.0 JSON.
Every credential attests skills, and every skill maps to roles. A person picks a target role and sees the weighted gap and what typically closes it, using their own data.
Organizations issuing on ibl.ai can draw on courses in Agentic LMS and records in Agentic SIS.
The résumé is written from the record, with every credential line linking to its verification. The summary can be drafted with the platform's AI, which runs on Agentic OS, and the person edits it.
Why does owning the learner wallet matter for an institution or an employer?
Owning the learner wallet matters because the record outlives any single subscription.
On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.
For an institution, that means the alumni record is not rented. For an employer, workforce skills data stays inside its own perimeter, next to the HRIS and the training systems that issue the credentials.
Agentic Wallet also connects to the badging work many teams already run. Our earlier post on skills profiles and badging ecosystems covers how skills profiles drive personalization.
1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University. ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.
Sources: W3C Verifiable Credentials Data Model v2.0 status, date and roles from the W3C Recommendation; Open Badges 3.0 alignment from the 1EdTech specification; plugfest dates, the 39 participants and the standards tested from JFF; the veterans demonstration from JFF; WGU figures from WGU's press release; Credly's Open Badges support from Credly; the Learner Credential Wallet from MIT Open Learning; Agentic Wallet capabilities from its public repository. The brief named "the JFF Labs digital wallet work" as the framework engines cite; JFF's own pages describe it as Learning and Employment Records and plugfests, which is the wording used here.