{ "$schema": "https://govschema.org/spec/v0.3/govschema.schema.json", "govschemaVersion": "0.3.0", "id": "mn/mfa/evisa-application", "version": "1.0.0", "title": "Mongolia Electronic Visa (e-Visa) Application", "description": "The Immigration Agency of Mongolia's Electronic Visa Application System, served unauthenticated at evisa.mn (immigration.gov.mn's own e-visa channel, live since 2021 under the Law on the Legal Status of Foreigners). The live wizard has four named parts: (1) Document type & Nationality (nationality, passport type, and an \"applying for\" purpose category, plus an email address); (2) Personal information (passport and biographic details, current-residence and emergency-contact details, an address-in-Mongolia block with a real cascading Province -> District/Soum -> Subdistrict/Bag selector, a facial-photo upload, an optional supporting-document upload, three yes/no declarations, and an accommodation-confirmation document-type selector); (3) Purpose & Duration (a fifteen-question supplementary declaration plus expected arrival/departure dates); and (4) Data confirmation (a terms-and-conditions attestation followed by payment). This schema models parts 1-3 in full plus the part-4 attestation. Reaching part 2 onward requires confirming a one-time emailed link (a genuine double-opt-in email-confirmation gate, not a CAPTCHA or biometric check) sent to the address entered in part 1; this session controlled a real disposable-inbox address for that purpose (no real applicant's identity or a real government-issued credential was used or impersonated). Every field name, required-asterisk marking, and dropdown option list documented here was read directly from the wizard's own live-rendered HTML (all four parts' markup is present in a single page load via the jquery.steps plugin, gated only by CSS visibility, not by separate page requests) after that link was followed, not inferred or guessed. This schema does NOT model: the Guardian-information sub-flow (b_/e_-prefixed fields), which the site's own client-side logic shows only when its passport-photo OCR reads an applicant date of birth indicating an age under 18 -- a real-time computed condition this registry's Condition grammar cannot express (it references only static field-to-field comparisons, not a computed age-from-date-of-birth threshold), and which this session could not otherwise trigger without a fabricated minor's passport image; the three read-only \"Purpose of visit / Duration of stay / Number of entries requested\" spans on the Purpose & Duration step, which are server-computed displays driven by the Part 1 selections, not applicant-editable fields; and the payment step's own bank-transfer/merchant fields (`paymentPurpose`, `paymentRecipient`, `paymentAccount`, `paymentConsulate`, `paymentPayerType`, `paymentFullName`, `paymentEmail`, `paymentAmount`, `paymentFee`), excluded as payment mechanics rather than government-form data, consistent with this registry's own established convention. No application was actually submitted for payment and no fee was paid in producing this schema. Filing this application is a traveller action performed directly with the Immigration Agency of Mongolia through evisa.mn; this schema does not file the application itself, and the live source is always authoritative. GovSchema is independent and is not affiliated with, endorsed by, or operated by Mongolia or its Immigration Agency.", "status": "draft", "jurisdiction": { "country": "MN", "level": "national" }, "authority": { "name": "Immigration Agency of Mongolia", "abbreviation": "IAM", "url": "https://www.evisa.mn" }, "process": { "type": "application", "language": "en" }, "source": { "url": "https://www.evisa.mn/en/apply", "retrievedAt": "2026-07-16", "documentRef": "The live Electronic Visa Application System's own multi-step wizard at evisa.mn/en/apply, parts 1-4 (Document type & Nationality; Personal information; Purpose & Duration; Data confirmation), rendered server-side and inspected directly via a real browser session after confirming a one-time emailed continuation link." }, "verification": { "method": "manual-source-review-v1", "lastVerifiedAt": "2026-07-16", "verifiedBy": "GovSchema Engineering (Standards Engineer)", "nextReviewBy": "2027-01-16", "notes": "GOV-3375 (\"GovSchema Standard Research\"), opening Mongolia as a new jurisdiction in this registry. Fetched https://www.evisa.mn/en/apply directly (HTTP 200) and drove it live with Playwright/Chromium (a real desktop-Chrome user agent, no login/CAPTCHA/WAF gate on the initial wizard load). Part 1 (nationality Egypt, passport type Ordinary, applying-for Tourism, a disposable-inbox email address) was submitted, producing a genuine emailed confirmation link from e-visa@immigration.gov.mn (SPF/DKIM-signed, sha256-verifiable headers recorded in VERIFICATION.md) rather than advancing the in-browser wizard directly -- a double-opt-in email-confirmation gate, not a CAPTCHA. Following that link reached parts 2-4's full markup in one page load (jquery.steps-based, not a lazy-loaded SPA), from which every field name, required-asterisk marking, and dropdown option list documented here was read directly, including a live-confirmed three-level cascading Province -> District/Soum -> Subdistrict/Bag address selector (Ulaanbaatar -> Bayangol -> 1-r khoroo among the real returned values) and the passport-photo upload's own OCR auto-fill behavior (confirmed from the wizard's own client-side logic, not just its instructional text). Models 49 `fields[]` across four steps, 3 `documents[]` (a passport-photo-page scan with declared OCR auto-fill, a facial photo, and an optional supporting document), and 2 `crossFieldValidation` rules (passport expiry after issue date; expected departure after expected arrival). 2 valid conformance fixtures (0 errors each) plus 7 mutation-control fixtures (each raising exactly 1 error, including both crossFieldValidation violations, an enum violation, and a pattern violation) are committed under `conformance/mn/mfa/evisa-application/1.0.0/`. Both validators pass. See VERIFICATION.md for the full sourcing record, including the disclosed Guardian-sub-flow and payment-step scope boundaries." }, "maturity": { "level": "structural-reference", "criteria": { "structuralReference": true, "verifiedSchema": false, "agentReadySchema": false, "executionTestedSchema": false }, "method": "maturity-self-assessment-v1", "assertedBy": "GovSchema Engineering (Standards Engineer)", "assertedAt": "2026-07-16" }, "license": "CC-BY-4.0", "steps": [ { "id": "document_type_and_nationality", "title": "Document type & Nationality", "fields": [ "nationality", "passportType", "applicationPurpose", "email" ], "next": "personal_information" }, { "id": "personal_information", "title": "Personal Information", "fields": [ "firstName", "lastName", "identificationNumber", "gender", "passportNumber", "dateOfBirth", "passportNationality", "countryOfBirth", "passportIssuingCountry", "placeOfBirth", "maritalStatus", "passportIssuedDate", "passportExpiryDate", "currentOccupation", "homeAddress", "homeContactPhone", "emergencyContactName", "emergencyContactPhone", "mongoliaProvince", "mongoliaDistrict", "mongoliaSubdistrict", "mongoliaFullAddress", "mongoliaContactPhone", "hasCriminalRecord", "wasVisaDenied", "appliedWithDifferentName", "addressConfirmationDocumentType" ], "next": "purpose_and_duration" }, { "id": "purpose_and_duration", "title": "Purpose & Duration", "fields": [ "declaredFullName", "declaredCitizenship", "previousCitizenship", "declaredPassportNumber", "purposeOfVisitDetail", "intendedLengthOfStay", "needsVisaExtension", "lostPassportHistory", "priorInvitationDetails", "transitCountries", "socialNetworkUsage", "countriesVisitedLast10Years", "specializedSkillsOrTraining", "mongolianRelatives", "travelExpensesPayer", "expectedArrivalDate", "expectedDepartureDate" ], "next": "data_confirmation" }, { "id": "data_confirmation", "title": "Data Confirmation", "fields": [ "agreesToTermsAndConditions" ] } ], "fields": [ { "name": "nationality", "label": "Nationality", "type": "string", "required": true, "description": "The applicant's nationality, selected from the live wizard's own 136-entry `#applicantCountryId` dropdown (a subset of all countries -- the applicant-facing list of nationalities this e-visa channel actually serves, not a full ISO country list). Modelled as a free-text string carrying the site's own opaque numeric option value (e.g. `1002` for Azerbaijan), matching this registry's own precedent for large source-controlled option lists (see `am/mfa/evisa-application`'s `birthCountry`) rather than reproducing all 136 values as an enum.", "sourceRef": "Part 1, ``, populated via `POST /en/callPasstypeData`; confirmed required via its own asterisk label marker" }, { "name": "applicationPurpose", "label": "Applying for", "type": "string", "required": true, "description": "The applicant's broad purpose-of-application category. Also populated dynamically per selected `nationality`/`passportType` via a live POST to `/en/checkPassportType`; two values, `TOURISM` (wire value `20`) and `SPORT OR CULTURAL EVENTS` (wire value `21`), were returned for the tested nationality this session -- other nationalities may unlock additional categories, not exhaustively tested. Modelled as a free-text string carrying the site's own opaque numeric option value for the same reason as `passportType`.", "sourceRef": "Part 1, ``, confirmed required via its own asterisk label marker", "validation": { "pattern": "^[^@\\s]+@[^@\\s]+\\.[^@\\s]+$" } }, { "name": "firstName", "label": "First name", "type": "string", "required": true, "classification": "pii", "description": "The applicant's first name. The passport-photo-page upload (see `documents[]`, `passportPhotoPage`) auto-fills this field via the site's own OCR pipeline; the field remains a plain, editable text input either way.", "sourceRef": "Part 2, ``, confirmed required via its own asterisk label marker" }, { "name": "lastName", "label": "Last name", "type": "string", "required": true, "classification": "pii", "description": "The applicant's last name. Auto-fillable from the passport-photo-page OCR upload, same as `firstName`.", "sourceRef": "Part 2, ``, confirmed required via its own asterisk label marker" }, { "name": "identificationNumber", "label": "Identification number", "type": "string", "required": false, "description": "An optional national/personal identification number for the applicant. The live field carries no asterisk and no `required`-class marker.", "sourceRef": "Part 2, `` (no asterisk)" }, { "name": "gender", "label": "Gender", "type": "enum", "required": true, "classification": "pii", "description": "The applicant's gender, a three-option radio group with real, confirmed wire values.", "sourceRef": "Part 2, `` / `id=\"F\" value=\"2\">` / `id=\"O\" value=\"5\">`, confirmed required via the group's own asterisk label marker", "validation": { "enum": [ "1", "2", "5" ] } }, { "name": "passportNumber", "label": "Passport number", "type": "string", "required": true, "classification": "sensitive-pii", "description": "The applicant's passport/travel document number. Auto-fillable from the passport-photo-page OCR upload.", "sourceRef": "Part 2, ``, confirmed required via its own asterisk label marker" }, { "name": "dateOfBirth", "label": "Date of Birth", "type": "date", "required": true, "classification": "pii", "description": "The applicant's date of birth, entered in the site's own `yyyy/mm/dd` format (confirmed via the live `pickadate` widget's own `format: \"yyyy/mm/dd\"` configuration). Auto-fillable from the passport-photo-page OCR upload; the site's own client-side logic computes the applicant's age from this value to decide whether to show the (unmodelled, disclosed) Guardian-information sub-flow for applicants under 18.", "sourceRef": "Part 2, `` with `pickadate({format:\"yyyy/mm/dd\"})`, confirmed required via its own asterisk label marker", "validation": { "pattern": "^\\d{4}/\\d{2}/\\d{2}$" } }, { "name": "passportNationality", "label": "Current Nationality (as in Passport)", "type": "string", "required": true, "classification": "pii", "description": "The applicant's nationality as it appears on their passport -- a distinct field from Part 1's own `nationality` selector, pre-filled with the Part 1 value by the site's own JavaScript but independently editable (a live, searchable country dropdown, not a fixed subset). Auto-fillable from the passport-photo-page OCR upload.", "sourceRef": "Part 2, ``, 255 `