User-Provided Data

OneID now supports returning unverified user-submitted data when no verified match is available.

This enhancement enables customers to capture user-provided information even when verification fails, improving journey completion rates - particularly in low-assurance use cases.

Feature Behaviour

When a verified match cannot be established:

• The end user may submit updated or corrected information (e.g., a revised address).
• The journey is not blocked.
• The submitted data is returned in a dedicated unverified_claims object.
• Verified and unverified data are clearly separated in the response payload.

This allows you to distinguish between high-assurance (verified) attributes and user-declared (unverified) attributes in your application logic. It is particularly useful for low-assurance use cases, where allowing users to continue without verified data improves completion rates and user experience.

For higher assurance cases, we recommend checking the relevant confidence level before choosing to use data not verified by us.

You’ll find user-provided data in the unverified_claims block in the Retrieve user info response. More technical information on how to use this can be found here.