Payhawk
Vulnerability disclosure program on Self-hosted payhawk.com
- Top reward
- No cash rewards
- 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.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- 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.
This program does not pay cash rewards.
- Pays cash
-
No
Unfortunately, due to the Payhawk funding structure, it is not currently possible for us to offer a paid bug bounty program.
- Response
-
Within 1 days
you will receive an acknowledgment reply email from the Payhawk Security Team, this is usually within 24 hours of your report being received.
- Safe harbor
-
Full
Payhawk will not seek prosecution of any security researcher who reports, in good faith and in accordance with this policy, any security vulnerability on an in-scope Payhawk service.
- Hall of fame
-
Yes
We will also offer to include reporters of qualifying vulnerabilities on our acknowledgments page and we’ll ask for the details you wish to be included.
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 2
- app.payhawk.com
- payhawk.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Payhawk's policy. "We" in these lines means the program, not this site.
While testing
-
Access unnecessary amounts of data. For example, 2 or 3 records are enough to demonstrate most vulnerabilities (such as an enumeration or direct object reference vulnerability)
-
Violate the privacy of Payhawk users, staff, contractors, systems, etc.
-
Communicate any vulnerabilities or associated details via methods not described in this policy or with anyone other than your dedicated Payhawk security contact
-
Modify data in our systems/services which is not your own
-
Disrupt our service(s) and/or systems
-
Disclose any vulnerabilities in Payhawk systems/services to 3rd parties/the public prior to the Payhawk confirming that those vulnerabilities have been mitigated or rectified.
-
We request that any and all data retrieved during research be securely deleted as soon as it is no longer required and at most, 1 month after the vulnerability is resolved, whichever occurs soonest.
-
please email [email protected] ensuring the communication is encrypted with our public key hosted at: https://payhawk.com/.well-known/pgp_key.asc.txt
Not accepted
-
Volumetric/Denial of Service vulnerabilities (i.e. simply overwhelming our service with a high volume of requests)
-
TLS configuration weaknesses (e.g. “weak” cipher suite support, TLS1.0 support, sweet32, etc.)
-
Issues surrounding the verification of email addresses used to create user accounts
-
Clickjacking vulnerabilities
-
Self XSS / DOM Based XSS (i.e. where a user would need to be tricked into pasting code into their web browser)
-
CSRF where the resulting impact is minimal
-
CRLF attacks where the resulting impact is minimal
-
Host header injection where the resulting impact is minimal
-
Network data enumeration techniques (e.g. banner grabbing, existence of publicly available server diagnostic pages)
-
Reports of improper session management/session fixation vulnerabilities.
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.