We are excited to announce the launch of tools.multipaz.org, a web-based suite of tools designed to make working with digital identity payloads—such as ISO 18013-5 mDocs, CBOR/COSE structures, and SD-JWT tokens—easier than ever. This new application leverages the fact that the core Multipaz SDK is written in Kotlin Multiplatform. Because the codebase is multiplatform by design, compiling the SDK to Kotlin/JS was a natural step, allowing us to run the exact same cryptographic, parsing, and validation logic natively inside the browser that runs on Android, iOS, and server backends minting and verifying credentials.
First off, we owe our community a quick apology: we missed writing a blog post for the Multipaz 0.99.0 release back in May! The team was completely heads-down and fully occupied preparing for the France Interop event in La Ciotat. It was an incredibly busy but rewarding experience showcasing real-world digital identity interoperability, and we are absolutely thrilled with how everything went.
But now we're back, and we have not one, but two major releases to share! We launched Multipaz 0.99.0 on May 4, 2026, and Multipaz 0.100.0 on July 8, 2026.
You can check out the full release notes and changelogs on GitHub:
We've significantly expanded our support for the upcoming ISO/IEC 18013-5 Second Edition, which we've been actively helping to finalize within the ISO/IEC SC17 WG10 committee. This update brings powerful new capabilities to Multipaz, including support for Alternative Data Element Sets, Encrypted Documents, Document Sets, and SD-JWT VCs. We also conducted extensive interoperability testing against other implementations, giving us high confidence in both the evolving standard and our robust implementation in Multipaz.
One of the most exciting, user-visible features in ISO 18013-5 Second Edition is NFCv2—a highly optimized version of the NFC engagement protocol used when tapping a mobile device against an mdoc reader.
In the first edition of ISO 18013-5, NFC engagement came in two flavors—static and negotiated—and was built on top of NFC Forum Connection Handover, which in turn relied on NDEF. While this mechanism works, its layered architecture requires the two devices to complete around 10 communication round-trips just to establish the Bluetooth Low Energy (BLE) connection. On typical consumer devices, this translates to a noticeable delay of several hundred milliseconds.
NFCv2 drastically simplifies the exchange of APDUs, saving hundreds of critical milliseconds during the tap to deliver an incredibly responsive experience. When combined with another ISO 18013-5 Second Edition feature—conveying the BLE L2CAP PSM directly in the engagement—presenting an mdoc in person becomes up to 10x faster!
A video is worth a thousand words. See it in action below:
Notice how the entire presentment takes only ~400 milliseconds—well under the critical 500 ms threshold typically expected for a seamless transaction. We think NFCv2 is going to be a game-changer for Digital Credentials!
We've also been busy crafting high-level verifier APIs perfect for server-side integration. Check out the new VerificationSession and related types in the org.multipaz.verification package.
These APIs make it incredibly easy to request credentials from wallets using a wide range of protocols, including:
ISO/IEC 18013-7 Annex C over the W3C Digital Credentials API
ISO/IEC 18013-7 Annex A over the custom URI scheme mdoc://
OpenID4VP 1.0 over the W3C Digital Credentials API
OpenID4VP over the custom URI scheme haip-vp://
This means websites can now request credentials from multiple different wallets, even if they implement completely different transport protocols and formats. The APIs fully support both ISO mdoc and SD-JWT VC-based credentials.
Check out this video showing all of these capabilities working together in harmony:
In this video, a verifier's mdoc reader communicates with a wallet using NFC for engagement and BLE for data transfer. The request sent from the reader is for identification, allowing the holder to present one of several document types, including a Mobile Driving License (mDL), an EU PID in mdoc format, an EU PID in SD-JWT VC format, an Aadhaar credential, a Photo ID, or a Google Wallet ID Pass (source code).
You'll see the holder choose to return the EU PID, and on the reader side, the operator receives and displays the credential details—demonstrating that an SD-JWT VC was successfully transmitted over the BLE connection used for the ISO 18013-5 Second Edition transaction. Pretty sweet!
Beyond the core Multipaz SDK, we've been busy driving several exciting initiatives across the broader Multipaz project, including exploring how Multipaz can be used for Agentic use cases, as well as starting to build out a playground of issuers and relying parties. Additionally, the application shown in the videos above is the new Multipaz Wallet—a project we kicked off just a couple of months ago!
While we want the core SDK to remain boring, stable, and predictable, the Multipaz Wallet effort is a different beast: an active playground to showcase our SDK, experiment with cutting-edge features (like link-based verification and account-bound credentials), run the entire Multipaz SDK in-browser for a "web wallet", and try out other ideas. Remarkably, a huge chunk of it is being built by Antigravity and other AI tools! We can't wait to share more about these experiments in future blog posts.
But shifting our focus back to the core SDK: the team recently aligned on our roadmap, and our official plan of record is to reach 1.0.0 around Q4 2026, depending on the time needed to get the codebase fully in shape for this important milestone! With our steady 6-to-8 week release cadence, the 1.0.0 milestone will likely follow a few more 0.x.0 releases, and then it will be time for the big 1.0.0 release. This is also the perfect time to remind everyone that Multipaz is a fully open-source project, and we warmly welcome contributions from both existing downstream users and new contributors alike! The team meets every Tuesday—check out the OWF community calendar for details if you want to get involved.
Parallel to the 1.0 roadmap, we are actively participating in the DCHP (Digital Credentials Harmonized Presentation) working group and plan to implement early drafts into Multipaz for interoperability testing with other early adopters, routing feedback back to the standards organizations—just like we've done with ISO 18013-5 and OpenID4VP. We are also prioritizing support for OpenID4VCI server-to-server issuance flows and, of course, we'll continue contributing to the ISO/IEC SC17 WG10 and OpenID DCP working groups.
We are thrilled to announce the release of Multipaz 0.98.0!
This release brings a wealth of capabilities tailored for the evolving digital identity ecosystem.
Whether you are a software developer building the next generation of digital wallets, standards architect working on interoperable standards and protocols, or just casually tracking the wallet ecosystem, this release delivers critical updates designed to make digital credentials more accessible, standardized, and user-friendly.
Here is a deep dive into the significant changes arriving with Multipaz 0.98.0 (full changelog).
As digital identity crosses borders, standardization and localization are more important than ever.
Global Accessibility: We have rolled out brand-new translation infrastructure alongside full translations for 21 languages, ensuring digital credentials can be seamlessly adopted by diverse populations globally.
Leading the ISO Evolution: Multipaz now supports the ISO/IEC 18013-5 Second Edition query language, according to the latest drafts from ISO JTC1 SC17 WG10.
Furthermore, we’ve integrated support for ISO/IEC 18013-7:2025 Annex A, which is now live on verifier.multipaz.org and within the Multipaz TestApp.
Aadhaar Expansion: Broadening our support for major national identity frameworks, 0.98.0 includes support for the Aadhaar doctype in our online verifier at https://verifier.multipaz.org.
One of the greatest friction points in digital identity is the disconnect between how credentials are used in-person versus online. We have heavily prioritized creating a cohesive experience across all platforms.
Unification of Proximity and Online Presentment UI/UX:
The lines between tapping your phone at a physical terminal and presenting credentials online are blurring.
We have unified the UI/UX for proximity and online presentment to provide users with a consistent, intuitive flow regardless of the interaction context.
To that end, presenting a credential to a website is now using the same UI/UX as when presenting it to a proximity reader.
New Vertical Document Lists & QuickAccessWallet:
Developers using both Compose (Android) and SwiftUI (iOS) can take advantage of our new vertical document list composables/views (VerticalDocumentList composable, VerticalDocumentList SwiftUI view).
On Android, we've also engineered our PresentmentActivity so it can easily
be used to implement a QuickAccessWallet on Android, allowing users to rapidly access their most essential credentials (example).
For verifiers and developers testing physical infrastructure, flexibility is key.
USB-Connected NFC Readers: We've introduced support for USB-connected NFC readers, opening up new deployment architectures for physical terminal verifiers. Release 0.98.0 supports three USB readers with more planned in the future.
Event Logging Framework: To address the growing need for accountability and security auditing, we've implemented a new event logging framework. This records significant user lifecycle events, such as credential presentment, ensuring compliance, robust debugging, and enabling forensic analysis. The recorded events are intended to be saved on the user's device and never shared but the storage format is flexible enough to be exported by the user if they wish to share it with someone else for analysis.
Migration to Maven Central: Starting with 0.98.0, all Multipaz releases will be distributed via Maven Central, moving away from GMaven. This streamlines dependency management for the broader open-source Java/Kotlin community.
Enhanced Sharing & Reliability: We've added native support for sharing files seamlessly on both Android and iOS using the standard share sheets functionality of each platform. This makes it easy for wallet applications to e.g. share events recorded by our new event logging framework.
Looking to the Future: Rounding out the release, we are introducing preliminary support for Digital Payment Credentials, paving the way for the convergence of identity and payments in a single wallet ecosystem. For the next release we'll be working on adding support for transaction data in both our OpenID4VP and ISO/IEC 18013-5:2021 implementations and build demos showcasing this.
Here you'll find the latest news, updates, and stories from the Multipaz team. Stay tuned for announcements, technical deep-dives, and community highlights.