Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Razorpay

Bug bounty on HackerOne razorpay.com

Accepting reports Full safe harbor
Go to program Website
Top reward
$3,000
Top severity paid
Critical
Assets in scope
6
Public CVEs
2
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $3,000
for critical bugs.
Report on HackerOne
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 5 days
As the policy promises.
No public write-ups
Keep findings private.

Rewards

What HackerOne lists as the payout for each severity.

Severity Reward
Critical $3,000 from $1,000
High $1,000 from $500
Medium $500 from $200
Low $200 from $100
Response
Within 5 days | First Response | 5 days |
Safe harbor
Full Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

6 assets you may test.

Web 6

  • api.razorpay.com Critical
  • checkout.razorpay.com Critical
  • dashboard.razorpay.com Critical
  • invoices.razorpay.com Critical
  • payroll.razorpay.com Critical
  • x.razorpay.com Critical

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Razorpay (via HackerOne)'s policy. "We" in these lines means the program, not this site.

While testing

  • Please use your [email protected] email address for registration where the username is your HackerOne username.
  • Include a custom HTTP header in all your traffic.
  • **DO NOT use automated tools or scanners**. Reports as such will be closed as N/A.
  • Never use a finding to compromise/exfiltrate data or pivot to other systems.
  • Post-exploitation should not be performed.
  • Please provide detailed reports with reproducible steps.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • Social engineering (Eg. phishing, vishing, smishing) is prohibited.
  • Make good faith and effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • Only interact with accounts you own or with the explicit permission of the account holder.

Not accepted

  • Issues without clearly identified security impacts such as missing security headers.
  • Role-Based Access Control (RBAC) issues and privilege escalation between different role levels
  • Clickjacking and issues only exploitable through clickjacking
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
  • Attacks requiring Man In The Middle (MITM) or physical access to a user's device.
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Missing best practices.
  • Any activity that could lead to the disruption of our service (DoS).
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Rate limiting or bruteforce issues on non-authentication endpoints and issues without impact
  • Missing best practices in Content Security Policy.
  • Missing HttpOnly or Secure flags on cookies
  • Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
  • Vulnerabilities only affecting users of outdated or unpatched browsers (Less than 2 stable versions behind the latest released stable version)
  • Software version disclosure / Banner identification issues / Descriptive error messages or headers (Eg. stack traces, application or server errors).
  • Tabnabbing
  • Open redirect - unless an additional security impact can be demonstrated
  • Issues that require unlikely user interaction
  • Price manipulation WITHOUT SUCCESSFUL TRANSACTION
  • Any services hosted by 3rd party providers and services not provided by Razorpay
  • IDOR references for objects that you have permission to access
  • Missing CAA headers
  • Vulnerabilities requiring physical access to the victim's unlocked device.
  • DOM Based Self-XSS and issues exploitable only through Self-XSS.

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour 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.

Search NVD
CVESeverityPublished
CVE-2024-10850 Medium 6.1 13 Nov 2024
CVE-2024-10851 Medium 6.1 13 Nov 2024

Original policy

Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Razorpay looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.

Response Targets

Razorpay will make the best effort to meet the following SLAs for hackers participating in our program:

Type of Response SLA in business days
First Response 5 days
Time to Triage 10 days
Time to Bounty 14 days
Time to Resolution depends on the severity of the bug

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

  • Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
  • Follow HackerOne's disclosure guidelines.

Program Rules

  • Please use your [email protected] email address for registration where the username is your HackerOne username.
  • Include a custom HTTP header in all your traffic. (Burp and other proxies allow easy automatic addition of headers to all outbound requests.) A header that includes your username: X-Bug-Bounty: HackerOne-
  • DO NOT use automated tools or scanners. Reports as such will be closed as N/A.
  • Never use a finding to compromise/exfiltrate data or pivot to other systems. Use a proof of concept only to demonstrate an issue. Post-exploitation should not be performed. (E.g., in case of a code execution found, stop and report)
  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • Social engineering (Eg. phishing, vishing, smishing) is prohibited.
  • Make good faith and effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.

Consequences of complying with this policy

  • We will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy.
  • We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act. We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.
  • If legal action is initiated by a third party against you and you have complied with Razorpay’s bug bounty policy, Razorpay will take steps to make it known that your actions were conducted in compliance with this policy.

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:

  • Issues without clearly identified security impacts such as missing security headers.
  • Role-Based Access Control (RBAC) issues and privilege escalation between different role levels
  • Clickjacking and issues only exploitable through clickjacking
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
  • Attacks requiring Man In The Middle (MITM) or physical access to a user's device.
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Missing best practices.
  • Any activity that could lead to the disruption of our service (DoS).
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Rate limiting or bruteforce issues on non-authentication endpoints and issues without impact
  • Missing best practices in Content Security Policy.
  • Missing HttpOnly or Secure flags on cookies
  • Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
  • Vulnerabilities only affecting users of outdated or unpatched browsers (Less than 2 stable versions behind the latest released stable version)
  • Software version disclosure / Banner identification issues / Descriptive error messages or headers (Eg. stack traces, application or server errors).
  • Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
  • Tabnabbing
  • Open redirect - unless an additional security impact can be demonstrated
  • Issues that require unlikely user interaction
  • Price manipulation WITHOUT SUCCESSFUL TRANSACTION
  • Any services hosted by 3rd party providers and services not provided by Razorpay
  • IDOR references for objects that you have permission to access
  • Missing CAA headers
  • Vulnerabilities requiring physical access to the victim's unlocked device.
  • DOM Based Self-XSS and issues exploitable only through Self-XSS.
  • Reports of spam
  • Reports that require social engineering/phishing
  • Subdomain takeover

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep Razorpay and our users safe!