FAQ

Common questions about integrating Paspo ID.

Does my app need internet access during the sign-in call? The client SDK itself does not on Android — it talks to the Paspo ID app over an Intent. The Paspo ID app and your server both need to be online. Web/QR sign-in requires the browser to be online, since it polls your server for the QR session status.

What happens if the user uninstalls the Paspo ID app mid-integration? On Android, authenticate detects this, opens the Play Store listing, and returns NotInstalled instead of failing silently. See Android reference.

Can I use the Android SDK from Jetpack Compose? Yes — see Custom integration, or use the ready-made button.

What data can I actually request from a user? Whatever you request in scope: phone numbers, e-mail addresses, national ID, or the user's permanent Paspo ID. See PaspoScope. Face ID / Voice ID matching itself never leaves the user's device — you only ever receive the profile fields you asked for.

Where do I register my app (package name, signature, redirect/callback URL)? Through onboarding — see Support.

Is iOS or Web/QR ready for production yet? Not yet — both SDKs are in development. See iOS and Web / QR SDK for the intended API shape, and Support if you need one sooner.