Account, users & compliance

How to register and verify trade access

Email, Telegram, and WhatsApp are separate verification channels. Email is required and is the current live trade-login verification route; Telegram and WhatsApp become trusted only after their own OTP routes are live and confirmed.

Step 1 — Register

open the Siemme registration page, choose exactly one account role: buyer, retailer, supplier, or Siemme team member. Then enter contact name, company, city, country, ZIP/postal code, email, preferred language, preferred currency, and phone details. One registered email has one role and cannot be reused for another side.

Step 2 — Verify on the website

after submit, Siemme opens the Verify access screen. Choose Email, Telegram, or WhatsApp, enter the one-time code, and submit. If you are not ready, return later to https://siemme.com/verify. Each code has no time expiry, but it can be used only once.

Email verification

email is mandatory for trade login. Siemme verification emails must come from info@siemme.com. Codes from Mozilla, Firefox, Google, Microsoft, or another service are not Siemme verification codes.

Telegram verification

Telegram is separate from email. First open @Siemme_bot and press Start or send /start. Telegram user OTP delivery is staged separately from owner alerts. Until the website channel-verification route is fully live, use email to open trade login.

WhatsApp verification

WhatsApp is separate from email and Telegram. Automated WhatsApp OTP will be enabled after the WhatsApp provider connection is live; until then email remains the mandatory verification baseline.

Changing channels later

after login, use Profile to add or change Telegram, WhatsApp, phone, address, preferred language, or preferred currency. Any new or changed channel stays pending until its own verification is completed.

Device rule

buyer and supplier users are limited to two active devices. Siemme team members can use up to five devices and login locations are recorded.

Was this helpful? Feedback capture will connect to the support database in the next support iteration.