Retake Flow UI
The Entrupy Android SDK provides startRetakeCapture(authenticationId) to launch the retake capture workflow for an existing authentication. The retake flow focuses only on the images needed to complete the authentication, guided by Entrupy's analysis of the original submission.
Overview
- Initiates directly from an existing authentication using its
authenticationId. - The SDK guides the user through capturing only the additional images needed.
- Uses the same smart capture features (blur detection, glare feedback, alignment assistance) as the primary capture flow.
- The retake session shares the same timeout behavior as a standard capture (default: 2 hours).
1. Prerequisites
Before launching a retake workflow:
- Ensure the SDK is initialized (
EntrupyApp.init(application)called in yourApplication.onCreate()). - Verify the user is authorized (
isAuthorizationValid()returnstrue). - Have the
authenticationIdfrom the original authentication — typically received via webhook on your backend.
2. Launching the Retake Flow
import com.entrupy.sdk.app.EntrupyApp
fun startRetake(authenticationId: String) {
val entrupyApp = EntrupyApp.sharedInstance()
if (!entrupyApp.isAuthorizationValid()) {
Log.e("Retake", "User not authorized. Please log in first.")
return
}
entrupyApp.startRetakeCapture(authenticationId)
}
The SDK launches the retake capture activity, guiding the user through the required additional photos. After submission, the images are uploaded and the authentication is re-processed.
Final results for retake submissions are delivered to your backend via webhook, the same as initial captures. The retake flow is self-contained — once launched, the SDK manages the capture, upload, and result delivery.
3. When to Use Retakes
Retakes are typically triggered when:
- Entrupy requests additional images — the original submission needs more data for a reliable assessment.
- Image quality issues — the original photos had quality problems (blur, glare, poor framing).
- Support resolution — after a flag review, Entrupy's team may request a retake.
Your backend receives retake requests through webhooks. Surface these to users through your app's UI, then launch startRetakeCapture() with the relevant authenticationId.
Next Steps
- Capture Flow UI — the primary capture workflow.
- Detail View Controller — displays authentication status and results.
- Customer Support Integration — support workflows that may lead to retake requests.