Registration & identity testing
A guided test workbook for your first Hawiyati internet evaluation: account creation, invitations, verification, KYC and assurance.
Work through the recommended path first, then run the alternative and negative cases with the owner. These are expected outcomes derived from the current code, not a claim that the internet environment has passed. Use Blocked when setup or delivery prevents a test; use Fail when an action behaves incorrectly.
Public entry points
| Service | URL · Purpose |
|---|---|
| Documentation | https://docs.hawiyaty.com/ This guide and product documentation |
| Registration | https://idp.hawiyaty.com/idp/register Direct registration; availability depends on policy |
| Account | https://account.hawiyaty.com/ End-user login and Identity Verification |
| Admin | https://admin.hawiyaty.com/ Owner/admin setup and KYC review |
| OIDC demo | https://oidc-sp.hawiyaty.com/ Application-initiated OIDC login/registration |
| SAML demo | https://saml-sp.hawiyaty.com/ Application-initiated SAML login/registration |
Before you start
- Agree a test window with the owner. The local machine, services and Cloudflare tunnel must stay running. No hosts-file entries or local certificate installation should be needed for the public URLs.
- Use a dedicated test mailbox/phone you control. Use a short unique username such as
uat_1025_a01(3–30 allowed characters); use a new account for independent branches. - Ask the owner to record the active policy: open registration, email/phone channels, approval, required terms/custom fields, per-application KYC and bot protection. Settings are environment-dependent; this workbook does not change them.
- Use a private window for the end user and a separate browser profile for the admin/reviewer. The owner performs configuration and approval steps unless you were explicitly given a suitable test role.
- Agree test documents privately with the owner. Do not publish identity scans, real document numbers, passwords, OTPs, session tokens or invitation URLs in feedback. Synthetic files may fail real OCR; that is not automatically a defect.
Recommended first run
NET-01 → REG-01 → KYC-01 → one of KYC-02–05 → IAL-01 → IAL-02. Then run the admin-created path (REG-03), invitation path (REG-04), and review/negative cases. Owner-dependent cases can be performed together on a call. Restore changed test policies at the end.
What the assurance levels mean in this test
These are Hawiyati’s internal identity-proofing levels, separate from password/MFA authentication strength. They do not assert compliance with an external assurance framework.
| L0 | No KYC profile defaults to L0. Account creation or email verification alone does not demonstrate L2. |
|---|---|
| L1 | Recognized by the level model, but not a distinct outcome produced by the reviewed public registration/BASIC_KYC path. |
| L2 | Current approved document-proofing outcome; the reviewed KYC-required login gate checks for effective L2. |
| L3 / L4 | Names exist in the model/advanced workflows, but final approved decisions are capped at L2 in the current code. Do not expect to obtain L3/L4. |
Current product limits to watch: the account form submits BASIC_KYC (documents only) and records consent automatically through its compatibility endpoint. Selfie/liveness require another client; an explicit KYC consent control, a workflow picker, or an automatic return button is not implemented in that form. Reverification can also expose differences between the simplified displayed status and the backend flag: record these as findings.
Your test session & feedback
Progress is saved only in this browser on this origin. It is not sent to the owner automatically. Download the report and send it through your agreed channel. Downloads contain your notes; review them before sharing. Changing browser/device/domain does not transfer progress. EN/FR share progress on the same origin; private browsing may discard it.
Test scenarios (31)
NET-01 Open the public servicesNot run
Prerequisites / starting state: Owner confirms services and tunnel are running. Use an external connection, such as mobile data.
| Step | Action | Expected result |
|---|---|---|
| 1 | Open the documentation, account portal and one demo application using the links above. | Each opens over HTTPS without a certificate warning; an authentication redirect is normal. |
| 2 | Start Sign in from the account portal or demo application. | The login page stays on a public hawiyaty.com host. No localhost, private IP, dev hostname or local port is required. |
| 3 | If a page fails, record the service, time, visible error, and Cloudflare Ray ID if shown. | An access failure is recorded as Blocked for dependent tests; do not disable browser certificate checks. |
REG-01 Register from the direct linkNot run
Prerequisites / starting state: Owner enables self-service registration, confirms verification channels and disables admin approval for this case. Use a fresh username and an inbox you control.
| Step | Action | Expected result |
|---|---|---|
| 1 | Open https://idp.hawiyaty.com/idp/register in a fresh private window. | The identity form appears. If registration is closed, stop and coordinate with the owner. |
| 2 | Enter a unique username, first/last name, email, and any required phone/custom fields. Continue. | The configured verification step appears; a code reaches the correct destination. |
| 3 | Enter the received code; repeat for a second channel only if requested. Accept the displayed terms if required. | The password step becomes available after the configured checks. |
| 4 | Enter matching passwords of at least eight characters and complete registration. | A success page appears. This direct entry has no original application to return to. |
| 5 | Open the account portal and start Sign in using this account. | The same user can authenticate; further MFA/KYC depends on the owner’s application policy. Record the landing page. |
REG-02 Register from an application login pageNot run
Prerequisites / starting state: REG-01 prerequisites. Owner specifies whether to use the OIDC or SAML demo and records its registration/KYC policy. Use a new identity for each application run.
| Step | Action | Expected result |
|---|---|---|
| 1 | Open the selected demo, start its login, then choose the registration link on the identity page. | The registration form opens within the application-initiated flow. |
| 2 | Complete identity, configured verification, terms and password steps. | Registration completes and the active flow returns to login rather than looping between register and login. |
| 3 | Sign in with the new account and complete any required MFA/KYC. | The selected application receives this user after its gates pass. No duplicate account or unrelated application is used. |
| 4 | Repeat with the other demo in a fresh private session and a new test identity. | OIDC and SAML results are recorded separately in the notes. |
REG-03 Create an end user in AdminNot run
Prerequisites / starting state: Owner or designated admin uses their own authorized admin account. Create only a disposable end user, not an admin operator.
| Step | Action | Expected result |
|---|---|---|
| 1 | Open Admin → Users → Create User. Fill a unique username, reachable email, names and a password of at least eight characters; select locale and a test group if needed. | Required-field validation is clear; the form accepts valid data. |
| 2 | Create the user, find it in Users, and reopen its details. | One active user exists with the expected profile, locale and groups. Admin creation does not run the public email OTP flow. |
| 3 | In a separate private window, start login from the account portal with the created credentials. | The end user authenticates subject to application policy; creating the account alone does not award KYC L2. |
| 4 | Try creating the same username again once. | The duplicate is rejected clearly and no second record is created. |
REG-04 Register using an invitationNot run
Prerequisites / starting state: Owner closes open registration and enables admin approval for this isolated case; prepares a fresh invited email.
| Step | Action | Expected result |
|---|---|---|
| 1 | Owner: Admin → Users → Invite User. Enter the test email, create the invitation and privately share the one-time displayed URL. | Invitation is created; delivery status is shown. A link can be shared if email delivery is unavailable. |
| 2 | Tester: open the invitation in a fresh private window. | Registration is available despite closed open registration; the invitation binds the email address. |
| 3 | Complete the verification, terms and password steps. | The account is created without the admin-approval hold because invited users are pre-approved. Other checks still apply. |
| 4 | Owner: confirm user status. Tester: start login from the account portal. | The invited user can continue under the configured application policy. Record the outcome without copying the invitation token into feedback. |
REG-05 Reject used, revoked or expired invitationsNot run
Prerequisites / starting state: Owner prepares separate used, revoked and genuinely expired test invitations. Expiry is normally seven days; do not change the machine clock.
| Step | Action | Expected result |
|---|---|---|
| 1 | For each prepared link, open it in a new private session with open registration closed. | The invitation does not authorize a new registration; closed/invalid messaging is acceptable. Note each variant. |
| 2 | Return to a fresh valid invitation from REG-04. | A valid invitation still works; failure of an invalid link has not broken later registrations. |
REG-06 Closed registration without an invitationNot run
Prerequisites / starting state: Owner disables Allow self-service registration. Use a fresh private window with no invitation state.
| Step | Action | Expected result |
|---|---|---|
| 1 | Open the direct registration URL without query parameters. | A closed-registration view appears; no usable identity form is offered. The current implementation should not loop back to login. |
| 2 | Start an application login and inspect its registration entry. | The closed posture is respected. Record a misleading registration link as a usability issue. |
| 3 | Owner restores the agreed registration policy after this test. | Later registration tests can run under their documented prerequisites. |
REG-07 Validate identity fields and duplicate handlingNot run
Prerequisites / starting state: Open registration enabled; use only test identities. Reuse only your own earlier username for the duplicate attempt.
| Step | Action | Expected result |
|---|---|---|
| 1 | Try a two-character username, a username with a space, an invalid email, and an invalid required phone, correcting one field at a time. | Invalid data cannot finish registration. Username rules: 3–30 letters/digits/underscore/hyphen; phone, if required, uses international + format. |
| 2 | Repeat the flow with your already-created username and a fresh email you control. | No duplicate account is created; record the visible response without expecting the UI to reveal whether any other user exists. |
| 3 | Correct the data and continue with a new valid username. | Errors are recoverable and do not leave the user on an unusable page. |
REG-08 Wrong, expired and resent verification codesNot run
Prerequisites / starting state: Owner confirms actual OTP lifetime and attempt limits. Use a reachable email; SMS variant requires a configured provider and a test phone.
| Step | Action | Expected result |
|---|---|---|
| 1 | Reach the verification step and enter one deliberately wrong code. | The code is rejected; no account is created at this stage. |
| 2 | Choose Resend once, then enter the most recently received code. | A new code arrives and can advance the flow; the earlier code is no longer the current code. |
| 3 | In a separate fresh run, wait beyond the owner-confirmed expiry then submit the expired code. | The expired code is rejected and the current implementation sends a replacement. Use the new code to recover. |
| 4 | If both email and phone are required, complete them in the displayed order. | Both configured channels must be verified. Record delivery delay/channel separately; stop after a rate-limit message. |
REG-09 Terms, password and back navigationNot run
Prerequisites / starting state: Owner configures a required terms version for the terms variant. Start with a fresh registration.
| Step | Action | Expected result |
|---|---|---|
| 1 | At the terms step, try to continue without acceptance, then accept. | The unchecked terms block progress; acceptance allows the password step. |
| 2 | Try a password shorter than eight characters, then mismatched confirmation, then a valid matching pair. | Invalid values are rejected clearly; valid values can complete registration. |
| 3 | In another fresh run, use the form’s Back action before completion and correct identity details. | Identity fields return; previous verification/consent must be repeated as needed for the corrected details. No partial duplicate account appears. |
REG-10 Approve or reject pending registrationsNot run
Prerequisites / starting state: Owner enables self-service registration and Admin approval required; use two fresh non-invited identities.
| Step | Action | Expected result |
|---|---|---|
| 1 | Tester: finish registration for both users. | Both see pending approval rather than immediate account activation. |
| 2 | Tester: attempt an application login before approval. | The pending user cannot receive normal authenticated application access. |
| 3 | Owner: Users → pending-registration banner → Approve the first user. Tester retries login. | The first user becomes active and can proceed under application policy; check an approval email only if delivery is configured. |
| 4 | Owner: Reject the second disposable user and confirm the deletion prompt. Tester retries login. | The rejected pending registration is removed and cannot authenticate. Do not use an established account for this branch. |
REG-11 Custom fields and default groupsNot run
Prerequisites / starting state: Owner prepares a test custom field in Attribute Definitions, exposes it as required in Registration Policy, and selects an existing harmless default group.
| Step | Action | Expected result |
|---|---|---|
| 1 | Tester: open a new registration and leave the custom field empty; then try an invalid value if its type has validation. | The required field is visible and invalid/missing values block progress. |
| 2 | Complete registration with a valid value. | Registration succeeds under the remaining policy gates. |
| 3 | Owner: inspect this user’s attributes and group membership. | The correct normalized attribute value and the configured default group are present; no privileged group is assigned accidentally. |
REG-12 Application-specific policy and bot protectionNot run
Prerequisites / starting state: Owner records contrasting policies for the two demos and enables one configured bot provider for an isolated run. Do not change global settings without coordinating.
| Step | Action | Expected result |
|---|---|---|
| 1 | Start registration from each demo in separate private sessions and compare with the direct link. | The owner-confirmed application overrides govern each SP-initiated registration; the direct link uses the global policy. |
| 2 | For the bot-enabled case, omit the visible challenge completion once, then solve it normally. | An unsatisfied enabled challenge prevents progress; a valid challenge permits the normal flow. |
| 3 | If blocked by repeated attempts, stop and record the message/time instead of retrying rapidly. | The result is recorded as Blocked with the owner’s next action. This is a functional test, not a load test. |
REG-13 Bulk invitationsNot run
Prerequisites / starting state: Owner has two disposable reachable addresses and access to Users invitation tools. This creates invitations, not pre-created end users.
| Step | Action | Expected result |
|---|---|---|
| 1 | Open the bulk-invite dialog; enter two distinct test emails and use the displayed import/validation options. | The dialog previews or validates the intended recipients clearly. |
| 2 | Submit once and record the per-recipient outcome. | Each accepted address receives its own invitation outcome; failures are not hidden by an overall success message. |
| 3 | Redeem one valid link using REG-04 and inspect the remaining invitation. | The completed invitation is consumed independently; no duplicate or cross-recipient binding appears. |
KYC-01 Reach identity verification after registrationNot run
Prerequisites / starting state: Use a newly registered or admin-created end user. Owner confirms the account portal’s Identity Verification feature is enabled.
| Step | Action | Expected result |
|---|---|---|
| 1 | Sign in through the account portal and select Identity Verification. | Your own KYC status appears. A new user normally has no submitted verification; no other user’s evidence appears. |
| 2 | Inspect the form before submitting: document selector, required images, displayed size/type guidance and privacy information. | The current form offers document upload. It does not create a separate account or offer a workflow selector. |
| 3 | Read the privacy/consent information before proceeding. | Record missing or unclear consent as a usability/privacy issue. The current compatibility endpoint records consent automatically; an explicit checkbox is not promised. |
KYC-02 Algerian national ID: both sidesNot run
Prerequisites / starting state: KYC-01 complete. Use a separate fresh eligible test user for this document variant and owner-approved test evidence. Do not expect synthetic evidence to pass real OCR.
| Step | Action | Expected result |
|---|---|---|
| 1 | Select Algerian National ID (CIN); choose the front image, then the matching back image. | The expected upload fields appear. JPEG, PNG and PDF are offered by this UI; each file must respect the displayed limit (default 10 MiB). |
| 2 | Submit once; wait for the request to finish, then reload Identity Verification. | The submission remains visible with its status/history; no silent loss or duplicate is observed. |
| 3 | Record the resulting status and ask the owner to confirm the processing outcome for this fixture. | A valid fixture follows the configured provider’s approval/review route. Unreadable or unsupported content can be rejected; uploading a file alone does not prove identity. |
KYC-03 Algerian passport: data pageNot run
Prerequisites / starting state: KYC-01 complete. Use a separate fresh eligible test user for this document variant and owner-approved test evidence. Do not expect synthetic evidence to pass real OCR.
| Step | Action | Expected result |
|---|---|---|
| 1 | Select Algerian Passport; upload the photo/data page including the MRZ lines at the bottom. | The expected upload fields appear. JPEG, PNG and PDF are offered by this UI; each file must respect the displayed limit (default 10 MiB). |
| 2 | Submit once; wait for the request to finish, then reload Identity Verification. | The submission remains visible with its status/history; no silent loss or duplicate is observed. |
| 3 | Record the resulting status and ask the owner to confirm the processing outcome for this fixture. | A valid fixture follows the configured provider’s approval/review route. Unreadable or unsupported content can be rejected; uploading a file alone does not prove identity. |
KYC-04 Foreign passport: data pageNot run
Prerequisites / starting state: KYC-01 complete. Use a separate fresh eligible test user for this document variant and owner-approved test evidence. Do not expect synthetic evidence to pass real OCR.
| Step | Action | Expected result |
|---|---|---|
| 1 | Select Foreign Passport; upload the photo/data page including the MRZ lines. | The expected upload fields appear. JPEG, PNG and PDF are offered by this UI; each file must respect the displayed limit (default 10 MiB). |
| 2 | Submit once; wait for the request to finish, then reload Identity Verification. | The submission remains visible with its status/history; no silent loss or duplicate is observed. |
| 3 | Record the resulting status and ask the owner to confirm the processing outcome for this fixture. | A valid fixture follows the configured provider’s approval/review route. Unreadable or unsupported content can be rejected; uploading a file alone does not prove identity. |
KYC-05 Algerian driving licence: both sidesNot run
Prerequisites / starting state: KYC-01 complete. Use a separate fresh eligible test user for this document variant and owner-approved test evidence. Do not expect synthetic evidence to pass real OCR.
| Step | Action | Expected result |
|---|---|---|
| 1 | Select Algerian Driving License; upload the matching front and back images. | The expected upload fields appear. JPEG, PNG and PDF are offered by this UI; each file must respect the displayed limit (default 10 MiB). |
| 2 | Submit once; wait for the request to finish, then reload Identity Verification. | The submission remains visible with its status/history; no silent loss or duplicate is observed. |
| 3 | Record the resulting status and ask the owner to confirm the processing outcome for this fixture. | A valid fixture follows the configured provider’s approval/review route. Unreadable or unsupported content can be rejected; uploading a file alone does not prove identity. |
KYC-06 Missing images and invalid filesNot run
Prerequisites / starting state: Fresh eligible user; prepare harmless empty, non-image/text, and oversized (> owner-confirmed limit) fixtures. Do not upload executable or malicious files.
| Step | Action | Expected result |
|---|---|---|
| 1 | Try submitting without a front image, then choose CIN with a front but no back. | The UI prevents submission and explains the missing required image. |
| 2 | Try a zero-byte file, then a harmless disallowed file if the browser picker permits it. | The file is not accepted as valid evidence. If selection is blocked by the picker, record that result; no developer tools are required. |
| 3 | Try one file just above the agreed size limit, then replace it with a valid small fixture. | Oversized evidence is rejected without a crash; valid evidence can be retried. Note generic errors that fail to explain the reason. |
KYC-07 Poor quality, mismatch and document reuseNot run
Prerequisites / starting state: Owner supplies separate labeled fixtures: blurred/cropped, expired or mismatched data where supported, and a duplicate document on a second disposable user. Provider behavior must be agreed per fixture.
| Step | Action | Expected result |
|---|---|---|
| 1 | Submit each fixture using a fresh eligible user and the correct document type. | The processing outcome is recorded per fixture; unreadable evidence must not be reported as successfully proofed merely because upload succeeded. |
| 2 | Owner inspects the decision/risk/review information for each submission. | Compare with the agreed result. Automatic rejection versus manual review depends on provider and thresholds; unexpected approval is a defect to investigate. |
| 3 | For the duplicate-document fixture, compare the first and second identities with the owner. | Record whether reuse is detected and which decision follows. If the provider cannot extract the required fingerprint data, mark this variant Blocked rather than claiming the protection passed. |
KYC-08 Manual review and approvalNot run
Prerequisites / starting state: Owner prepares a real MANUAL_REVIEW_REQUIRED case; automatic approvals need not appear in the review queue. Use a designated reviewer account.
| Step | Action | Expected result |
|---|---|---|
| 1 | Reviewer: Admin → KYC Queue; locate the test submission and open its evidence viewer. | The correct user/session, document sides and risk information are displayed clearly. |
| 2 | Use the displayed assignment action if required, inspect the evidence and choose Approve → Confirm Approve. | The decision saves once, the case closes and the audit/history records the reviewer. |
| 3 | Tester: refresh Identity Verification and start a fresh login to the agreed KYC-protected demo. | Status becomes Verified/APPROVED. Access can proceed when required assurance is met; owner confirms achieved level is at most L2. |
KYC-09 Rejection, reason and resubmissionNot run
Prerequisites / starting state: Owner prepares a separate manual-review case for rejection and confirms the configured attempt allowance.
| Step | Action | Expected result |
|---|---|---|
| 1 | Reviewer: choose Reject; first leave the reason blank, then enter a clear test rejection reason and confirm. | Blank reason cannot be confirmed in the review UI; a valid reason records the rejection. |
| 2 | Tester: refresh Identity Verification and inspect the rejected entry. | Rejected status and an understandable reason are visible; record missing reason/details as a defect. |
| 3 | If another attempt is permitted, submit corrected evidence using the same user. | A new submission/history entry is visible and follows processing. A rejected or pending state must not grant protected application access. |
KYC-10 Pending state, refresh and double submissionNot run
Prerequisites / starting state: Owner provides a user with a pending submission. Use only this disposable account; do not repeatedly upload large files.
| Step | Action | Expected result |
|---|---|---|
| 1 | While an upload is running, inspect whether the submit button is disabled; do not repeatedly click it. | The UI clearly indicates progress and prevents accidental duplicate clicks. |
| 2 | After pending status appears, reload and revisit the verification page. | Pending status/history persist. The current UI should not offer a new submission while pending or approved. |
| 3 | Start a fresh login to the agreed KYC-required application while still pending. | Normal protected access remains unavailable; completion/review messaging should explain the next step without an endless redirect. |
IAL-01 Check assurance before and after proofingNot run
Prerequisites / starting state: Owner tracks one fresh test user through registration and successful BASIC_KYC. Account status JSON is available to the signed-in user; do not share tokens or full responses.
| Step | Action | Expected result |
|---|---|---|
| 1 | Before KYC, open https://account.hawiyaty.com/api/account/kyc/status in the signed-in browser tab, or ask the owner to inspect the equivalent status. | Record only currentLevel and status. With no KYC profile, currentLevel is L0; email verification/admin creation alone is not L2. |
| 2 | Complete an approved document-proofing run, then inspect the status again. | An approved BASIC_KYC session normally reports currentLevel L2. Record the actual level; do not substitute a workflow’s requested level. |
| 3 | Owner compares requested versus achieved level on the session. | The approved achieved level cannot exceed L2 in the current decision service. This internal level is distinct from MFA strength and does not claim external certification. |
IAL-02 KYC-required login and completion-only accessNot run
Prerequisites / starting state: Owner enables KYC required for one designated demo, provides an L0 test user and records a control application with KYC off.
| Step | Action | Expected result |
|---|---|---|
| 1 | Start login from the KYC-required demo with the L0 user. | The flow sends the user to account identity completion, not to normal protected application access. |
| 2 | In that completion session, try the account portal’s normal navigation to profile/security if offered. | Completion-only access must not unlock unrelated account functions. Record an exposed or usable normal function as a defect. |
| 3 | Submit evidence, wait for the owner-confirmed approval and retry a fresh login from the original demo. | With effective L2, protected login can proceed as the same user. Record if there is no clear return action; automatic return from the current KYC upload screen is not promised. |
| 4 | Repeat login to the control application in a fresh session with a separate unverified test user. | Behavior matches its KYC-off policy, demonstrating the gate is application-specific rather than a registration failure. |
IAL-03 Reverification and assurance invalidationNot run
Prerequisites / starting state: Owner/supervisor has one approved disposable user and authority for the specific lifecycle action. Record baseline status/level first; a supervisor may not have all invalidation permissions.
| Step | Action | Expected result |
|---|---|---|
| 1 | From the test user’s KYC actions, request reverification with a clear reason; record the exact action used. | The backend marks reverification required. If the account UI still shows Approved, record the discrepancy rather than treating the UI as authoritative. |
| 2 | Tester: start a fresh login to the KYC-required demo. | Previously obtained assurance should no longer satisfy the gate while reverification is required. |
| 3 | Owner: if the reset/invalidate action is in scope, select an allowed lower level and record a reason. | Assurance can be lowered, not raised by an override. Complete the supported reverification path with the owner, or mark Blocked if the current UI cannot continue. |
SEC-01 Separate users, sessions and reviewer permissionsNot run
Prerequisites / starting state: Two disposable end users A/B and a separate authorized reviewer. Owner supplies only the intended test roles; no shared super-admin credentials.
| Step | Action | Expected result |
|---|---|---|
| 1 | Use A in one browser profile and B in another; visit each account’s identity verification/history. | Each sees only its own evidence and status. Record any cross-user disclosure without copying the exposed document. |
| 2 | As a normal end user, open the admin service. | An admin login/access boundary appears; end-user credentials do not grant review or approval privileges. |
| 3 | Sign out A, then use browser Back and reload the account page. | A fresh request requires authentication; A’s active session is not available to the next user. Record any sensitive content remaining visible after logout. |
UX-01 Mobile, language, errors and interrupted flowNot run
Prerequisites / starting state: Use the browsers/devices agreed with the owner; do not treat the bilingual workbook as proof that every product screen is bilingual.
| Step | Action | Expected result |
|---|---|---|
| 1 | Repeat a registration and a document submission on a phone or narrow browser window. | Labels, errors, buttons and selected filenames remain readable; no essential control is clipped. |
| 2 | Try the product’s available language/theme controls and navigate using keyboard Tab/Enter. | Available controls work, focus is visible and validation remains understandable. Record untranslated or missing product controls as observations. |
| 3 | In a disposable unfinished flow, close the tab or briefly disconnect; reopen through the original public entry point. | There is a recoverable login/registration state or clear restart instruction, without duplicate users or silent success. Mark the interrupted variant separately in notes. |
EXT-01 Advanced workflows: owner-assisted onlyNot run
Prerequisites / starting state: Optional extension. Owner provides a supported client/harness and configured providers. The present account form has no selfie/liveness UI; do not invent browser steps.
| Step | Action | Expected result |
|---|---|---|
| 1 | Owner selects STANDARD_KYC, STRONG_KYC or HIGH_ASSURANCE_KYC through their supported client and identifies the test session. | STANDARD requires selfie; STRONG adds liveness; HIGH_ASSURANCE adds a manual-review gate. If no usable client exists, mark Not applicable or Blocked with the reason. |
| 2 | With the owner, complete the configured evidence/challenge/review stages and record workflow, requested level, achieved level and decision. | Required stages cannot be silently skipped. Despite workflow names, the current final approval remains capped at L2; no L3/L4 success is expected. |
EXT-02 Migrated accounts, claims and external provisioningNot run
Prerequisites / starting state: Optional extension outside the first browser registration pass. Owner prepares a staged disposable import or configured upstream identity and an actual supported entry point.
| Step | Action | Expected result |
|---|---|---|
| 1 | Owner identifies whether this run covers CSV import/approval/commit, account claim, or upstream/JIT provisioning; record only the chosen path. | These are distinct provisioning paths, not options on the public registration or KYC form. Mark unavailable UI/client paths Not applicable. |
| 2 | Follow the owner-provided claim/integration steps, then compare the resulting user and KYC level. | The intended identity is linked without granting verified assurance merely because it was imported or provisioned. Do not infer a finished customer journey from API existence. |
Finish and return feedback
- For every Fail/Blocked result, give a short issue title, impact, actual behavior, exact reproduction steps and timestamp with timezone. Name any privately shared screenshot; this page does not upload attachments.
- Leave unexecuted cases as Not run. Explain Not applicable results. Never count Blocked or Not applicable as passed.
- Download the report and send it to the owner through the agreed private channel. There is no automatic submission or central feedback inbox.
- Owner: keep the report/run label for retesting, restore changed policies, and remove only the disposable test accounts/evidence after both parties agree. Keep the initial findings before clearing a run.