This document covers Toqen.app mobile-client behavior.
- The user scans a Toqen.app QR payload.
- The app parses public QR fields.
- The app resolves request context through Toqen.app services.
- The app shows request context.
- The user approves or denies.
- Approval signs a challenge through the device-key module.
- The app sends the decision through the mobile-facing client contract.
Manual code entry is a mobile fallback when QR scanning is unavailable. Once the request is resolved, the confirmation behavior is the same as QR.
The app can start or continue mobile authorization from service access actions. The user reviews context and approval requires device-bound cryptographic authorization.
The app should fail closed on malformed QR input, missing request context, local authentication failure, user denial, network failure, invalid response schema, or invalid signed response where signature verification is required.