The interactive platform simulator is part of the authenticated Myaza Trust documentation experience. It uses your current sandbox environment and the canonical Risk Intelligence, Monitoring, Transaction Intelligence, and Investigations workflows.

Open the platform simulator

Production execution is disabled. Scenarios that require controlled service fixtures remain clearly locked until those fixtures are configured.

Test monitoring in context

Create a Sandbox customer, then filter the catalogue to Monitoring. The lifecycle journeys cover:

• immutable policy scope across all supported lower-case Entity types;
• pause and resume without a scheduled check or charge while paused;
• permanent Off with retained history;
• an hourly Entity override against a daily policy default;
• removing the override and returning to the policy default;
• re-enabling an ended period as a distinct active subscription.

Monitoring scenarios reuse stable Simulator policies by check set. Running the same journey again does not create another policy version or a new timestamped policy.

Results link to the Entity for state and history, Risk Intelligence for material changes, Review Queue for action, and Rules & Policies for defaults. The public integration remains under /api/v1/monitoring.

Set up Sandbox Travel Rule

Travel Rule scenarios need a compatible published policy. If the Simulator shows Setup required or Policy incompatible, select Set up Travel Rule. The action opens Risk Intelligence → Rules & Policies → Fraud rules → Travel Rule with the server-owned sandbox-travel-rule-simulator preset selected.

1. Select Create Sandbox draft or Replace with Sandbox draft. This creates a new draft, or supersedes the current unpublished draft; it does not change the active policy.
2. Review the draft, then select Publish draft separately.
3. Return to the Simulator and refresh. After the Simulator refetches the published policy, the setup shows Ready for Simulator and the scenario shows Runnable.

The explicit Simulator fixture is deterministic and has no charge in local development and Sandbox. Ordinary Sandbox requests without a scenario still use configured pricing, and Production behaviour is unchanged. Remove sandboxScenario from Production requests.

See Travel Rule for crypto transfers for policy design, API requests, remediation and webhook events.