- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 2
- 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
- [email protected]
- Replies within 1 day
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
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
Our minimum reward or bounty is ₹1000.
- Pays cash
-
Yes
Our minimum reward or bounty is ₹1000.
- Response
-
Within 1 days
First response - 1 business day
- Hall of fame
-
Yes
Critical & High severity valid bug reporters will be listed on Zaakpay’s wall of Fame.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
2 assets you may test.
Domains 1
- zaakpay.com
Wildcard domains 1
- *.zaakpay.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Zaakpay's policy. "We" in these lines means the program, not this site.
While testing
-
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service and only interact with accounts you own or with the explicit permission of the account holder.
-
Trying DOS/DDOS attacks
-
Automated Scanning
-
Using vulnerability testing tools that automatically generate significant traffic
-
Accessing private information (use your own accounts)
-
Performing actions that may negatively affect Zaakpay users (social engineering, phishing, spam, denial of service)
-
Submitting reports from automated tools without verifying them.
-
Performing brute force testing to determine whether rate limiting is in place for particular APIs or pieces of functionality.
Not accepted
-
Issues related to software/application not under Zaakpay’s control or owned by some third party
-
Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)
-
Missing security headers which do not lead directly to a vulnerability
-
Clickjacking without an impact
-
Text Injection
-
Known-vulnerable library (without evidence of exploitability)
-
Spam & rate limiting
-
SSL/TLS protocol vulnerabilities
-
Best practice concerns will be reviewed, but in general, we require evidence of a vulnerability
-
Vulnerabilities only affecting users of outdated or unpatched browsers and platforms
-
The brute force of promo/coupon code
-
Social engineering attacks
-
Email/Phone number enumeration (user enumeration)
-
Any activity that could lead to the disruption of our service (DoS)
-
Open Redirection
-
Missing Security Headers
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 6 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.