Title
Create new category
Edit page index title
Edit category
Edit link
February 2026
Release notes for Febuary 2026
Feature
Retrieve User-Provided Data from End Users
Date: 12/02/26
We’ve introduced a new feature that allows customers to receive unverified data from end users when no verified match is found. This update helps improve user experience and journey completion, particularly for low-assurance use cases.
What’s New
- End users can now submit data that we’re unable to verify (for example, a corrected address).
- Instead of preventing the user from completing their journey, we’ll return the submitted data in an unverified block.
- This means you can still capture and review user-provided data even when it’s not verified.
Technical Details
- Unverified data is available in the unverified_claims block in the retrieve userinfo.
- This data is distinct from verified claims and should be handled appropriately in your integration.
- Ideal for low-assurance scenarios where flexibility and user flow continuity are priorities.
Why It Matters
Previously, users without verified matches were unable to complete their journey. With this update, you can now maintain smoother user experiences while still distinguishing between verified and unverified data.
Getting Started
No configuration changes are required to begin receiving unverified data - simply update your integration to parse the new unverified_claims block from the /userinfo response.
For more details or support, please contact us at askus@oneid.uk.
This is a non-breaking change.
You’ll find user-provided data in the **unverified_claims** block in the Retrieve user info response. More technical information on this can be found here, or contact us for further details.
@Copyright OneID Limited 2024