BursaPay Logo
Knowledge Base
Ticket Sign In
Help Center > Account Setup, Security & Navigation > Reporting a Security-Sensitive Account Problem

Reporting a Security-Sensitive Account Problem

Published 2026-08-23 5 min read
Who is this article for?
This guide is for All Users, Support Staff seeking operational guidance on BursaPay workflows.

UI Navigation Path (Step-by-Step)

  1. Stop sharing credentials or verification codes.
  2. Record the affected BURSA-ID/email and the exact workflow involved.
  3. Describe what changed and when it was observed.
  4. Submit the issue through the normal support channel.
Verified workflow guide: Shows what information support needs when an account may be compromised or incorrectly privileged.

1. Overview & Purpose

Security-sensitive problems include suspicious access, incorrect role/approval state and unexpected payout or account changes.

2. What You Need

Provide identifying metadata and the affected workflow without including passwords, OTPs or secret keys.

3. Step-by-Step Workflow

  1. Stop sharing credentials or verification codes.
  2. Record the affected BURSA-ID/email and the exact workflow involved.
  3. Describe what changed and when it was observed.
  4. Submit the issue through the normal support channel.

4. Rules, Boundaries & Troubleshooting

Support cases should minimize sensitive data. Authentication secrets should never be pasted into tickets or chat.

5. Verification & Next Steps

Support can then correlate the report with account state, activity records and the relevant role workflow.

Was this article useful?

Related Articles

Understanding BursaPay Account Verification States Creating a BursaPay Support Ticket
Ask Bursa AI