Configuration Console · MOI Virtual Agent

Secure access

Use the configured staff key. Credential reveal, configuration changes, SOAP mutations, and MCP mutations require the separate staff key. Every reveal and accepted change is audited.

Staff access key

ACTIVE RAIL

-

PAYMENT LOG

Disabled

AUDIT

0 changes

Atomic configuration and redacted old to new values.

EFFECTIVE PRECEDENCE

GUI-owned values win

TIER A

Integration endpoints

Use deployment values or apply an admin-authenticated portal override.

CONTRACT MAP

Mapped operations

Enable only operations backed by an MOI-supplied contract.

Use installed mapping

Delivery modes, courier companies and areas

Validated delivery JSON

AUTHENTICATED REVEAL

Service credentials

Full effective values come from the running app server. Edit to add or replace; tick Clear to remove. Unsaved values are never used by tests.

READ-ONLY VERIFICATION

Authenticated integration tests

Each test uses the saved server credential and one bounded read. No payment, mutation, or write operation is available here.

Traffic file numberEmirates IDVehicle chassis numberReceipt numberExisting payment ID

PAYMENT LOG

MOI payment-log lifecycle

Endpoint URLPayment merchant IDMOI service-kind codesDate wire formatCredential ownerSOAP dialectSOAP action template

Service action to MOI service-kind mapping

The Utility document shows service kind 328 as a sample, not a universal code. Configure the MOI-issued code for each action. Its prose says SOAP 1.2 while its screenshots show SOAP 1.1, so save the candidate dialect and action, enter an existing payment-log ID above, then run the read-only Payment log test.

Enable only when readiness is green

OFFICIAL RECEIPT

MOI GetReceiptDetail PDF

Credential ownerSOAP dialectSOAP action

The endpoint is the receipt_detail row in Contract Map. Configure the MOIUserProfile identity, save a candidate dialect and action, enter an Emirates ID and optional receipt number above, then run the Official receipt PDF test. This optional read never gates payment approval.

SECURITY

SOAP mutation gate

Enabling this opens only the second, audited portal gate. The immutable deployment gate must also allow writes; each write still requires the exact acknowledgement in SOAP Workbench and makes one attempt.

Allow acknowledged SOAP Workbench mutations

FLOW POLICY

Decision parameters and order

Every editable value below is validated, audited, and applied to the next request. Reordering never removes a gate.

Mock and presented fee values · minor units

Licence renewal fine scope

Fines that affect licence renewal

Driver/licence-level means an outstanding fine with no vehicle plate. Vehicle-attached fines stay with their vehicle unless staff explicitly choose the broader scope.

Restriction continuation policy

Governing sourceError envelope 275

Safe hand-offs

Runtime precedence · one token per line

Exact copy anchors

REAL SERVICE EXECUTION

Production flow editor

Every runtime call is shown with its exact dependencies, IF, THEN, ELSE, typed input and output, pricing inputs, failure evidence, and source. This runtime editor is separate from scenario and persona authoring. Only fields the runtime safely honors are editable. Locked identity and money-integrity steps remain visible.

Validated production operation-plan JSON

COMPLETE CONFIGURATION

YAML editor

Endpoints, credentials, mappings, rules, production plans, payment log, and staff controls in one validated document.

Server configuration YAML (write-only secrets stay masked)

CROSS-SERVICE ELIGIBILITY

Vehicle, licence, fines, black points and confiscation

These are the executed IF/THEN rules. The last line on each card identifies the matching GUI control or locked safety gate.

ALL FLOW KNOBS

Runtime flow settings

These replace environment-only flow tuning. Clear “Use deployment value” to apply an audited portal override without restarting.

FLOW PRODUCT TABLES

Insurance requirements, pickup, time windows and centres

Edit validated flow records. Insurance records remain reference data until an authorized provider contract is installed; editing them cannot enable quotes, purchases, or coverage changes.

Validated product JSON

JOURNEY STEP COPY

Every live plan-node label

Edit the English and Arabic label shown for each journey step. The step IDs, phases, required gates and allowed transitions remain visible but locked.

Journey step JSON

APPROVED COPY

Configurable catalog messages

Edit English or Arabic variants as validated JSON. Unknown keys and format placeholders are refused; only differences from the deployed catalog are stored.

Catalog JSON

VISIBLE · LOCKED

Safety-critical flow rails

Only controls protecting money, identity, authorisation, audit, or deployment trust remain locked.