Clear answers.
Known boundaries.

The current website provides public market and platform guides, account comparison, registration and demonstration registration, plus prototype client-security and account-workflow features. External trading, payment, KYC and production messaging providers are not yet connected.

Open the registration page, choose one of the account structures currently displayed and submit the required profile details. Registration creates a UPM Traders website profile; it does not by itself confirm a funded or externally provisioned trading account.

Yes. The demonstration-registration route is available for exploring the current portal workflow. Demonstration interfaces and figures are illustrative and must not be treated as live execution or market data.

The Accounts page presents the five structures currently approved for this prototype. Use its comparison table for the latest displayed names, minimums, leverage choices and spread labels rather than relying on an older document or screenshot.

No. Only values explicitly approved for the current website are displayed. Final commissions, swaps, stop-out levels, margin rules, execution policy and provider-specific pricing require verified commercial and legal information before production launch.

No availability should be assumed. Leverage depends on the selected account structure, eligibility, provider configuration, jurisdiction and applicable risk controls. The registration interface validates only the choices approved for its current prototype plan.

Educational guides are available for Forex, Metals, Shares, Indices, Commodities and Digital Assets. Examples, prices and charts are marked or intended as indicative demonstrations and do not confirm that a product is available for live trading.

No. The MT5 pages describe a planned experience. Official server names, account-group mappings, download links and provider connectivity remain pending verified documentation and approved integration work.

No official Web Trader endpoint, App Store listing or Google Play listing has been verified for this website. Buttons remain disabled or status-labelled until ownership, provider and official destination details are confirmed.

Passwords are processed by the application backend and stored as BCrypt hashes. Protected actions also use server-side authorization, session controls, validation and CSRF protection; a hidden frontend link is never treated as access control.

The current protected security workflow supports authenticator codes and one-time recovery codes. MFA secrets are encrypted at rest and recovery codes are stored only as hashes. Keep recovery codes private and never send them through chat or email.

The password-reset lifecycle is implemented, but production email delivery remains behind a safe provider boundary until an approved mail service, public HTTPS URL, rate limits and operational handling are configured.

No. It is an internal prototype review workflow. Production use requires an approved identity, AML and sanctions-screening provider together with compliance rules, retention controls, private storage and operational review.

No. Current deposit and withdrawal screens record workflow requests only. They do not settle funds, confirm balances or connect to a payment provider. Real processing requires a verified ledger, payment adapter, signed callbacks and reconciliation.

Verified legal entity, registration, licence, regulator, registered-address and jurisdiction information has not yet been supplied for publication. No regulatory status should be inferred from this prototype.