OdyCust/ GUIDE
УКР

Mobile and Desktop application

Native login source, session controls, workspace preview and current limits.

Desktop, Android 12+ and iOS 17.4+ include system-browser sign-in. Matching backend/CRM versions, an operator-registered client and configured mobile HTTPS associations are required. Source, Android-emulator and iOS-simulator compilation checks do not qualify physical-device login or a hosted deployment. Financial screens remain a separate fictional preview.

Desktop sign-in and session controls

  • Enter the public API HTTPS origin, CRM HTTPS origin, organization UUID and registered Native client ID supplied by the operator. Choose Sign in. Never enter your password, recovery code or wallet seed in the desktop configuration.
  • In the system browser, check Sign in to the app, the organization, application ID and return address. Continue confirmation requires the organization password; Confirm with key and return verifies the existing WebAuthn key. Only approve a request you started.
  • The browser returns a one-time code, not its session cookie or API tokens. Desktop creates its own tenant-local API session. Select organization is explicit; it grants no role. Confirm MFA applies only to that original session.
  • Refresh session rotates credentials explicitly. Sign out clears local credentials and asks the server to revoke the session. A network error means server revocation is uncertain; no request is automatically replayed. Closing/restarting the app loses its memory-only credentials and needs a new login.
  • If a key needs setup or recovery, complete that in the ordinary web flow and restart native login. Native financial screens, Android/iOS app links, installed distribution and physical MFA are not qualified by source tests.

Mobile sign-in and protected session storage

  • The operator must configure the signed app and exact HTTPS return domain. Android checks a verified App Link; iOS uses the system authentication session. An unverified domain or arbitrary custom URL scheme cannot replace this association.
  • Sign in through the system browser with your organization password and existing WebAuthn key, then explicitly choose Return to the app. Never enter a seed, private key or recovery code in app configuration.
  • The one-time code is bound to the login you started. If the app process ends, start an unfinished login again. Browser cookies are never handed over.
  • Mobile stores only a refresh credential in protected device storage, scoped to the organization and client. Access credentials remain in memory. Android uses Keystore and a file excluded from backup; iOS uses a nonsynchronizing Keychain item available only on the unlocked device.
  • An uncertain credential-rotation result requires fresh login. Sign out clears local credentials and requests server revocation; a network failure is not evidence that server revocation succeeded. Session persistence does not connect financial actions.

Sign in to the website with your phone

  • On the organization login page, choose Sign in with the app. Keep this page open; its QR code expires after two minutes.
  • In the Android or iOS app, sign in with MFA and select the same organization. Choose Scan QR to sign in and allow camera access. The phone uses its configured API; scanning cannot change the server.
  • Compare the website, organization and six digits on both screens. Only confirm a login you started. Select the comparison checkbox, then confirm with your existing security key through the system browser. Return to the app to send the approval.
  • The original website receives a new browser session. Complete any requested consent and organization selection. No mobile access token, password or browser cookie is carried in the QR.
  • Cancel on the website retires that request. Reject on the phone clears the local review and cannot undo approval already sent. If the result is uncertain, use Check sign-in on the website; do not repeat approval. An expired request needs a new QR.
  • This requires compatible reviewed web/backend and QR-capable app builds, configured HTTPS return associations and an existing MFA identity. Source tests and simulator builds do not qualify a physical camera, security key or hosted installation. A scan or phone unlock alone is not authentication.

Recognize the preview

The separate OdyCust Preview build displays Preview · Fictional data throughout the workspace. Its Northstar Demo organization, records and amounts are synthetic. They are not your account or evidence of a payment. The standard application contains no demo business records.

Move around the workspace

  • On Mobile, choose Overview, Wallets or Activity in the bottom bar. More opens Customers, Settings and Help. Desktop places these sections in the sidebar.
  • Select a wallet or record to open its details. Back to list returns to the current list and filters. Android system Back also leaves the detail screen.
  • Search filters only the loaded records. In Activity, select a record type or open Status to choose a state. Clear filters restores the loaded list.

Read amounts and states

Amounts include the asset and network. The selected-wallet amount describes one illustrative ledger book; different assets are not combined. Document confirmed refers to payout terms, not a successful payment. Invoice and transaction states keep their separate meanings.

Hide amounts removes amounts from visible and accessible text in this view. This is a visual privacy setting, not a permission change. The received-at label describes the loaded view, not transaction finality.

Make the view comfortable

  • Open Settings and choose Українська or English, then Light or Dark. These preferences apply to the current run.
  • On Desktop, Tab moves focus, Enter activates a control and Ctrl/Cmd+K opens section search. Escape closes search or returns from details. No shortcut sends funds.
  • In-app Help explains the same navigation, data meaning and preview limits.

What is not connected

Desktop/Android/iOS authentication is implemented and locally checked within available environments. Signed installed builds, real domain associations and physical MFA still need separate qualification. Business API reads and financial actions remain disconnected. The preview cannot create, sign, send or confirm a real operation. Continue using your configured web console for currently supported financial work.

Development builds and interface screenshots do not establish a store release, signed installer, physical-device authentication or production custody readiness.

If the sign-in service is unavailable

The system-browser sign-in and confirmation page uses the same service check as CRM. While We’ll be back shortly is shown, new sign-in and confirmation requests are paused. Keep the page open and wait for the connection check, or choose Check again.

Recovery does not sign you in, submit a key proof again or return to the app automatically. Passwords may need to be entered again, and confirmation or return links can expire during the interruption. If the attempt expires, is cancelled or has an unknown result, start a new sign-in or confirmation from the app. Do not reuse a copied return link or another app’s request.

The separate key-confirmation window can remain open while the API is unavailable. Completing that device prompt alone does not establish successful sign-in: the initiating browser page still needs the API to finish.

Related reading

OdyCust · User documentation2026-10-13

Search documentation

Search stays within this guide. It does not request console data.