iOS SDKProve Auth
Enhancements
iOS SDK 6.13.0: bundled Mobile Auth SDK updated to 3.3.2Prove Auth iOS SDK 6.13.0 updates the bundled Mobile Auth SDK to 3.3.2, up from 3.3.0 in earlier releases. To adopt it, use version6.13.0 for the ProveAuth pod in your Podfile. With Swift Package Manager, use that version for the swift.proveauth package. Don’t add a separate ProveMobileAuth dependency. ProveAuth pulls in the right one. For repository setup, see Set up Prove SDKs in your project. For integration details, see the iOS SDK implementation guide.Android SDKProve Auth
Enhancements
Android SDK 6.13.2: bundled Mobile Auth SDK updated to 3.3.2Prove Auth Android SDK 6.13.2 updates the bundled Mobile Auth SDK from 3.3.1 to 3.3.2. Prove publishes its Android SDKs to its own Maven repository. Your Gradle build must listhttps://prove.jfrog.io/artifactory/libs-public-maven/ alongside public repositories such as Maven Central. To adopt the release, change the com.prove.sdk:proveauth dependency version to 6.13.2 and sync Gradle. See Set up Prove SDKs in your project for the repository setup and the Android SDK implementation guide for integration details.UnifyAndroid SDKAPI
Bug fixes
POST /v3/unify-status returns success=false when device authentication doesn’t completeFor Unified Authentication with possessionType=none, POST /v3/unify-status now returns success=false when device authentication doesn’t complete. The device object in the authentication result carries error code 10004 (Missing authenticator completion) and no Prove Key is created. Previously this case returned success=possession_required, which prompted integrations to call POST /v3/unify-bind. That bind request then failed with HTTP 403 because no Prove Key existed. On success=false here, do not call POST /v3/unify-bind. Start a new authentication session with POST /v3/unify instead. See the error code reference for details.Android SDK 6.13.1: main-thread crash fix on resetDeviceSettings() and unregisterDevice()The Prove Auth Android SDK now clears the Device Authentication Token on a background thread when you call resetDeviceSettings() or unregisterDevice() from the main thread. Apps that call these methods from the main thread no longer crash while the token clears. Calling from a background thread remains the recommended practice. No code changes are required to adopt the fix. Download the latest Android client-side SDK to stay up to date. See the Android SDK implementation guide for integration details.UnifyAPI
Enhancements
POST /v3/unify-status now returns keySource in authenticationResultsA successful POST /v3/unify-status response now includes a keySource field inside authenticationResults. Use it to see which authentication method created and bound the Prove Key. It’s distinct from the existing mobile field, which reports the method that completed the current session. Values include mobileauth, otp, instantlink, provekey, and fido. Prove returns keySource only when success=true, and omits it for every other result or when Prove can’t identify the method that created the key. See the Unify status reference for the full list of possible values.Android SDKProve AuthAPI
Enhancements
Android SDK can recover a device’s registration after app reinstallWhen enabled for your integration, the Prove Auth Android SDK now attempts to recover a device’s registration after the user uninstalls and reinstalls your app on the same device, so the user may not have to register again. Recovery is best-effort, not guaranteed. It requires a supported device with Google Play Services and relies on registration data stored locally on that device. That data isn’t synced or restored to other devices. When recovery isn’t possible, the user registers again as before. The behavior is transparent to your integration, so no code change is required. See Prove Key validity for platform behavior after reinstall.UnifyPre-FillAPI
Enhancements
finalTargetUrl now accepts up to 2048 charactersThe maximum length of finalTargetUrl increased from 128 to 2048 characters on both POST /v3/unify and POST /v3/start. This field is the Instant Link desktop redirect URL required for the desktop flow. The set of acceptable characters is unchanged. No integration change is required to adopt the higher limit.Verified UserAPI
Enhancements
Prove can disable automatic Identity Manager enrollment for Verified UserVerified User enrolls passing identities into continuous Identity Manager monitoring by default. Prove can now turn off automatic enrollment for your account. When enrollment is off, a verification that would otherwise pass returnsisEnrolled: false with no proveId, and the verification result and signals stay valid. Read the outcome from signals[0].verifiedUser.champion.label instead of isEnrolled. Already-enrolled identities stay monitored until you deactivate or disenroll them. There is no request field or self-serve toggle, so contact your Prove representative to change the setting. See the Verified User verify guide and the Verified User overview for details.New Verified User sandbox test user for failed verificationsSandbox test user Kelci Dimond (2001004091) returns a deterministic failed verification from POST /v3/verify in the Verified User flow. The response returns isEnrolled: false with no proveId, the same shape as the existing Alf Novotni failed test user, so you can exercise your fail-path handling when a phone number has no identity match. See the Verified User verify guide for the full sandbox test-user list.Pre-FillAPIUnify
Enhancements
Unify returns8008 for a missing or invalid correlationIdPOST /v3/unify-status and POST /v3/unify-bind now return code 8008 (Invalid Correlation ID) with HTTP 403 when correlationId is missing, unrecognized, or expired (for example, after a session timeout). Previously these cases returned code 8001 (Malformed Request) with HTTP 400. This matches the 8008/HTTP 403 pairing that Pre-Fill and Identity already return. correlationId remains required on these endpoints. Only the error Unify returns when it’s missing or invalid has changed. See the error code reference for details.New Unify Sandbox test users for deterministic failure testingTwo Sandbox test users now return a deterministic hard failure for POST /v3/unify-status, so you can exercise exception-path handling end-to-end without waiting for a live failure to reproduce. Delly Endricci (2001004094) covers the North America flow and Karrye Dunstane covers the international flow. Both users fail Mobile Auth on the client, and POST /v3/unify-status returns success=false with no Prove Key bound and empty deviceId and proveId values. See the prove-auth-then-customer implementation guide for the full Sandbox test-user list.API
Enhancements
Error responses now includeclientRequestId and correlationIdNon-200 error responses from the /v3 API now include two optional tracing fields. The clientRequestId field echoes back the value supplied in the request. The correlationId field identifies the request flow when a Correlation ID is available. Use them to correlate error responses with the originating request and the request flow. Prove omits clientRequestId when the request didn’t include one and omits correlationId when none is available for the flow. Success responses are unchanged.Pre-Fill
Enhancements
More accurate PO Box filtering for Pre-FillPO Box detection is now more exact for US Pre-Fill verifications. PO Box addresses are still excluded by default from the addresses returned in/v3/verify Pre-Fill responses. Contact your Prove representative if you need PO Box addresses included in your configuration.Server SDKGo SDKJava SDK.NET SDKTypeScript SDK
Java server-side SDK v0.21.7
What’s new
- Fixed an issue where the
evaluationobject wasn’t populated in API responses.
Impact
Download the latest server-side SDK to stay up to date with Global Fraud Policy (GFP) evaluation results.Go server-side SDK v0.14.8
What’s new
- Fixed an issue where the
evaluationobject wasn’t populated in API responses.
Impact
Download the latest server-side SDK to stay up to date with GFP evaluation results.TypeScript server-side SDK v0.14.10
What’s new
- Fixed an issue where the
evaluationobject wasn’t populated in API responses.
Impact
Download the latest server-side SDK to stay up to date with GFP evaluation results..NET server-side SDK v1.6.6
What’s new
- Fixed an issue where the
evaluationobject wasn’t populated in API responses.
Impact
Download the latest server-side SDK to stay up to date with GFP evaluation results.Web SDK
iOS SDK
iOS client-side SDK v6.12.3
What’s new
- General stability and bug fixes.
- Renamed API method
withInstantLinktowithInstantLinkFallback.
Impact
Download the latest iOS client-side SDK to stay up to date with Prove’s latest tools. If your code callswithInstantLink, update it to withInstantLinkFallback.Web SDK
iOS SDK
iOS client-side SDK v6.12.0
What’s new
- General stability improvements.
Impact
Download the latest iOS client-side SDK to stay up to date with Prove’s latest tools.Android client-side SDK v6.12.0
What’s new
- General stability improvements.
Impact
Download the latest iOS client-side SDK to stay up to date with Prove’s latest tools.web SDK
web SDK
iOS SDKAndroid SDK
iOS client-side SDK v6.10.4
What’s new
- Support for Instant Link in iOS apps
- Bugs fixes for crash related to Mobile Auth flow in iOS devices without cellular connection
- Other bug fixes and general stability improvements.
Impact
Download the latest iOS client-side SDK to stay up to date with Prove’s latest tools.Android client-side SDK v6.10.6
What’s new
- Support for Instant Link in Android SDKs
- Other bug fixes and general improvement
Impact
Download the latest iOS client-side SDK to stay up to date with Prove’s latest tools.iOS SDK
Instant Link
Android SDK
Android SDK
Android SDK
iOS SDK
iOS SDK 6.5.1 certificate fix
Action required
Prove’s iOS Distribution certificate was unintentionally revoked due to an administrative error. This certificate signs officially released Mobile Auth and Client-Side iOS SDKs.If you develop with the Prove iOS SDK, update to version 6.5.1 immediately. This resolves certificate issues that prevent your app from building or releasing to the App Store.If you have any questions or need further guidance with the iOS SDK update, please submit a support ticket through the Developer Portal or contact your Prove representative..NET SDKServer SDK
.NET server-side SDK
What’s new
- .NET server-side SDK is available for all Prove Platform products including Prove Pre-Fill®, Prove Identity®, and Prove Unify.
- .NET developers can integrate Prove’s identity verification and authentication services using familiar C# syntax and .NET conventions.
- The SDK provides the same comprehensive features as the other server-side SDKs, including OAuth authentication, Correlation ID management, and all API endpoints.
- Install via NuGet:
dotnet add package Prove.Proveapi --version 1.0.1 - Refer to the Pre-Fill server-side SDK guide for implementation details and code examples.
Impact
This addition provides .NET developers with native tooling for seamless integration. Organizations using .NET can now implement Prove’s identity verification solutions without requiring extra language dependencies or custom API integration work.Android SDK - OTP prompt fix
What’s new
Download the latest Android client-side SDK to stay up to date with Prove’s latest tools.Impact
This ensures consistent authentication flows across all Android-powered device configurations, improving user experience for customers using devices in Wi-Fi-only mode or with inactive SIM cards.Web SDK - Mobile Auth latency fix
What’s new
Updated web SDK to version2.10.1 to fix Mobile Auth latency issues.Impact
This improvement reduces authentication response times and provides a more responsive user experience during the Mobile Auth flow.Product Launch
Prove Identity Manager- This standalone product supports direct enrollment of customers for ongoing monitoring with real-time change event notifications.
- Eight API endpoints are available for comprehensive identity management:
- Enhanced webhook notifications.
- Refer to the Identity Manager flow documentation for complete implementation details.
- Available initially in the United States with plans for expansion to more regions.
Enhancements
EU Region Improvements- Enhanced Bring Your Own Possession (BYOP) flows in the EU region by allowing empty phone numbers in
/unifyendpoint calls whenpossessionType=none. - Added comprehensive country validation logic for improved regional support.
- Created new test user with two addresses for P1 that fails Mobile Auth but passes OTP authentication.
- Updated Mobile Auth test behavior for P1/P2 users for more reliable testing scenarios.
Bug Fixes
Possession Check ReliabilityFixed Mobile Auth behavior in Sandbox to ensure consistent testing results and proper fallback to OTP when Mobile Auth fails.Policy ValidationResolved corner case where missing address scores or name scores in Verify calls were incorrectly flagged as passing in Complete calls.Unified AuthenticationAndroid SDKiOS SDK
Enhancements
Prove Unified Authentication- Prove Unified Authentication is live. Use the endpoints
/v3/unify,/v3/unify-status, and/v3/unify-bindto implement the Prove Unified Authentication solution. - Refer to the Unified Authentication flow documentation for more details.
Enhancements
Mobile Auth Sandbox TestingWhen testing Mobile Auth in Sandbox, you can submit an empty phone number to/v3/start with test user, Van Moors.Bug Fixes
/v3/complete ErrorFixed an issue where the/v3/complete endpoint sometimes returned an error when a social security number was missing.Enhancements
Prove Identity Test UserAdded Identity Test User that fails Mobile Auth.Web SDK UpdateUpdated the web SDK to fix theblocked by new CORS policy error.Enhancements
Instant Link and SMS Message CustomizationInstant Link and SMS message customization is available in the Start endpoint.Challenge Response Update in SandboxThe full date of birthdob and full social security number ssn return in the Challenge response when success=true.Enhancements
Instant Link Error CodeThe errorstatus 1001 info IP address not supported no longer appears when using Instant Link on the web SDK.Date of Birth Field FormatThe dob field in the /challenge endpoint updates to always return in the format: YYYY-MM-DD.Multiple Data Sources ProvisionUpdated the underlying success=true/false logic to handle more than one data source.Request Field ParityParity improved on the request field validation between Sandbox and Production.Additional API ResponseUpdated the Know Your Customer (KYC) / Customer Identification Program (CIP) output in the API specification for the /complete endpoint.Mobile SDK JFrog CredentialsAndroid and iOS SDKs no longer require JFrog credentials to download.