- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 23
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- https://bugbounty.paytm.com/
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Paid by UPI
- No identity requirement stated.
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
The policy page has no reward table. Here is what it says, in its own words.
- Lowest reward
-
₹1,000
The minimum reward for eligible bugs is 1000 INR, Bounty amounts are not negotiable.
- Pays cash
-
Yes
The minimum reward for eligible bugs is 1000 INR, Bounty amounts are not negotiable.
- Hall of fame
-
Yes
Our Hall of Fame page recognizes the contributions of reporters who have demonstrated a high level of dedication to our program.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
23 assets you may test, 25 excluded.
Wildcard domains 7
- *.mypaytm.com
- *.paytm.com
- *.paytm.in
- *.paytminsurance.co.in
- *.paytmmall.com
- *.paytmmoney.com
- *.paytmpayments.com
Domains 1
- paytmfoundation.org
Products and areas 15
- Authentication Bypass
- Cross Origin Resource Sharing
- Cross-Site Request Forgery
- Cross-Site Scripting
- Directory Traversal
- Leakage of Sensitive Data
- Local File Inclusion
- Open Redirects
- Payment Manipulation
- Privilege Escalation
- Prompt Injection
- Remote Code Execution
- Remote File Inclusion
- Server Side Request Forgery
- SQL injections
Out of scope (25)
- Attacks that require a rooted/jailbroken device
- Automated scanner-generated reports
- Content Injection/ Content Spoofing
- CSRF on forms that are available to anonymous users (e.g. login or contact form)
- CSV injection
- Disclosure of known public files or directories, (e.g. robots.txt)
- Email Rate Limiting or Spamming
- Error messages with non-sensitive data
- Fingerprinting / banner disclosure on common/public services
- Logout / Login Cross-Site Request Forgery (logout CSRF)
- Misconfigured CORS Headers
- Missing Cookie Attributes
- Missing HTTP security headers
- Non-application layer Denial of Service or DDoS
- Open ports without demonstrating any significant impact
- Presence of application or web browser 'autocomplete' or 'save password' functionality
- Reports related to the disclosure of Exif metadata from uploaded files
- Social engineering of our service desk, employees or contractors
- Social Engineering/ Phishing attacks
- SPF / DMARC / DKIM Mail and Domain findings
- SSL Attacks such as BEAST, BREACH, Renegotiation attack,SSL weak/insecure cipher suites
- Staging, dev and QA environments
- TapJacking/Clickjacking and issues only exploitable through TapJacking/Clickjacking
- Vulnerabilities requiring MITM or physical access to an unlocked device
- Zero-day vulnerabilities or recently disclosed CVE
Rules
What the policy asks of you, and the bug types it won't reward, quoted from PayTm's policy. "We" in these lines means the program, not this site.
While testing
-
Don't violate the privacy of other users, destroy data, disrupt our services, etc.
-
Only target your own accounts in the process of investigating any bugs/findings.
-
Don't target our physical security measures, or attempt to use social engineering, spam, distributed denial of service (DDOS) attacks, etc.
-
In case you find a severe vulnerability that allows system access, you must not proceed further.
-
Disclosing bugs to a party other than Paytm is forbidden, all bug reports are to remain at the reporter and Paytm's discretion.
-
Exploiting or misusing the vulnerability for your own or others' benefit will automatically disqualify the report.
-
Researchers must destroy all artifacts created to document vulnerabilities.
-
You agree to keep any communication with Paytm private.
Not accepted
-
Self-XSS is out of scope
-
Zero-day vulnerabilities or recently disclosed CVE will not be considered eligible until more than 90 days have passed since patch availability.
-
Fingerprinting / banner disclosure on common/public services.
-
Disclosure of known public files or directories, (e.g. robots.txt).
-
TapJacking/Clickjacking and issues only exploitable through TapJacking/Clickjacking.
-
Social engineering of our service desk, employees or contractors.
-
Missing HTTP security headers.
-
SPF / DMARC / DKIM Mail and Domain findings.
-
Email Rate Limiting or Spamming.
-
SSL Attacks such as BEAST, BREACH, Renegotiation attack,SSL weak/insecure cipher suites.
-
Non-application layer Denial of Service or DDoS.
-
Missing Cookie Attributes.
-
CSRF on forms that are available to anonymous users (e.g. login or contact form).
-
Logout / Login Cross-Site Request Forgery (logout CSRF).
-
Presence of application or web browser 'autocomplete' or 'save password' functionality.
-
Error messages with non-sensitive data.
-
Social Engineering/ Phishing attacks.
-
Attacks that require a rooted/jailbroken device.
-
Vulnerabilities requiring MITM or physical access to an unlocked device.
-
Automated scanner-generated reports.
-
Reports related to the disclosure of Exif metadata from uploaded files.
-
Open ports without demonstrating any significant impact.
-
Content Injection/ Content Spoofing.
-
Misconfigured CORS Headers.
-
CSV injection.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.