# NotaryCentral Remote Online Notarization requirements ## Access & digital assets ### RON onboarding eligibility Offer RON setup only when the account is eligible and distinguish pending access. - The onboarding visibility rules distinguish enabled access from pending or ineligible settings. Evidence: Passing linked suites. ### Local certificate password storage Handle certificate passwords through the local password vault. - Vault reads, writes, and deletion follow the storage contract tested for the current device. Evidence: Passing linked suites. ### Digital asset availability Retrieve certificate availability through the authenticated asset API. - Availability requests include the account authentication context and handle API responses. Evidence: Passing linked suites. ## Joining & signer preparation ### Invitation-bound video access Issue video access only for the session host or a valid invited participant. - Anonymous access, impersonation, excessive token lifetimes, and cross-session invitation reuse are rejected. Evidence: Passing linked suites. ### Participant preparation progress Persist participant preparation progress before broadcasting it. - Duplicate or backward stages are ignored and link-open progress is flushed before its broadcast. Evidence: Passing linked suites. ### Connection error guidance Translate video connection failures into an appropriate user-facing recovery message. - Known connection failures map to the tested guidance instead of an unexplained generic failure. Evidence: Passing linked suites. ## Identity verification ### Credential analysis lifecycle Handle credential-analysis starts and synchronization without leaking another signing’s state. - Processing and already verified sessions return structured responses; foreign signing context is forbidden. Evidence: Passing linked suites. ### Scoped knowledge-based authentication Bind KBA start and answer submission to the authorized signer context. - Invalid context and attempts to verify another participant fail; lockouts return structured errors. Evidence: Passing linked suites. ### Identity and presence readiness Block RON completion until the required identity, participant presence, and recording evidence is ready. - Failed or expired identity checks, absent signers, and missing evidence prevent finalization. Evidence: Passing linked suites. ## Video & recording ### Session recording status Record session completion and retain unexpected recording interruptions until a confirmed restart. - Completion persists the recording; interruption state is not cleared by an unconfirmed recording attempt. Evidence: Passing linked suites. ### Screen video and meeting audio Select the current notary’s screen video and the meeting audio for the recording. - Foreign, muted, audio-only, and ambiguous screens are rejected; overlapping stop/start calls cannot start a second recording. Evidence: Passing linked suites. ### Human participant detection Distinguish real meeting participants from recorder, ingress, and agent connections. - Recorder and agent connections do not count as human attendance. Evidence: Passing linked suites. ## Document fields & finalization ### Document-scoped annotations Store notary and participant annotations in the document annotation table under their scope. - Scope replacement upserts current items and removes missing items; scope presence is loaded from annotation rows. Evidence: Passing linked suites. ### Authoritative finalization checks Use persisted fields, participant evidence, and recording state when deciding whether a document can finish. - Missing signer fields or participation and recording interruptions block completion. Evidence: Passing linked suites. ### Idempotent document completion Complete a document once and replay the same finalization result for a matching retry. - A changed PDF or conflicting key is rejected; validation failure leaves no finalized side effects. Evidence: Passing linked suites. ## Journal & completion evidence ### RON journal finalization Finalize the linked journal with the correct owner, timestamp, sequence, and participants. - Foreign actors cannot finalize another owner’s journal and the tested timestamp and numbering rules are preserved. Evidence: Passing linked suites. ### Completion certificate generation Generate completion certificates for the specific finalized attempt and recover from transient generation failure. - Certificate keys are deterministic for an attempt and distinct correction attempts retain independent keys. Evidence: Passing linked suites. ### Completion certificate retrieval Retrieve the completion certificate for the selected notarization attempt. - The certificate hook uses the tested request and download flow for the selected attempt. Evidence: Passing linked suites. ## Session guidance & synchronization ### Guided next steps Choose the next session action from the current signing, recording, journal, and release state. - Guidance waits for document and recording prerequisites before journal completion or document release. Evidence: Passing linked suites. ### Consistent room status responses Normalize room-status responses from the supported API response formats. - CamelCase and snake_case status fields are read from API envelopes; non-object payloads are rejected. Evidence: Passing linked suites. ### Realtime room subscriptions Manage room subscriptions and their connection lifecycle. - Connection and subscription behavior follows the tested STOMP client lifecycle. Evidence: Passing linked suites.