Password, PIN, one-time code, or complete API key.
Tijarat support does not need any of these to investigate a problem. Anyone asking for one is not using the support process correctly.
Loading Tijarat
See which protections are available in beta, which controls are coming with live accounts, and what to do if something looks wrong.
Tijarat support does not need any of these to investigate a problem. Anyone asking for one is not using the support process correctly.
Do not pay for early activation or follow a deposit instruction from an inbound message, social account, agent, or copied screenshot.
A control is marked available only when it is connected and testable.
| Control | Status | What ready means |
|---|---|---|
| Authentication | Beta foundation | Phone or email verification and the current beta sign-in path |
| Two-step verification | Coming soon | A production-backed second factor with recovery rules |
| Devices | Coming soon | Active sessions, device context, and revocation evidence |
| Login history | Coming soon | Recent sign-in time and available device or location context |
| Passkeys | Coming soon | Supported device credentials and server enforcement |
| Withdrawal protection | Coming with funding | Additional checks or holds after sensitive changes |
| Freeze account | Coming with live accounts | A rapid restriction route with visible scope and status |
| Recovery case | Coming with live accounts | Tracked identity checks, actions, and resolution |
| Security activity | Coming with live accounts | Timestamped sensitive events and dispute references |
Do not continue with an inbound caller or message asking for secrets, a transfer, or remote access.
Open the app or type tijarat.pk yourself. Do not use the link in the suspicious message.
Use the live freeze control when available, or contact verified support for the applicable restriction.
Keep the case, order, transaction, device, or document reference and follow the formal status.
The planned API uses explicit market, account, order-history, and trade scopes. Withdrawals remain inside verified account controls, and full secrets are shown once.
Describe what happened and include a safe reference. Do not attach a CNIC image, full bank details, password, PIN, or one-time code to the public form.
Devices, sign-ins, sensitive changes, restrictions, and recovery all need a clear status and timestamp when live service opens.