- Top reward
- $30,000
- Top severity paid
- Critical
- Assets in scope
- 8
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $30,000
- for critical bugs, from $50.
- Report by email
- [email protected]
- Partial safe harbor
- Some legal protection; read the terms.
- Replies within 2 days
- As the policy promises.
- Paid by USD
- No identity requirement stated.
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$30,000 from $20,000 |
| High |
|
$20,000 from $10,000 |
| Medium |
|
$10,000 from $1,000 |
| Low |
|
$1,000 from $50 |
- Top reward
-
$30,000
The minimum bounty amount for a validated bug submission is $50 USD and the maximum bounty for a validated bug submission is $30,000 USD.
- Lowest reward
-
$50
The minimum bounty amount for a validated bug submission is $50 USD and the maximum bounty for a validated bug submission is $30,000 USD.
- Response
-
Within 2 days
First Response │ 2 days
- Safe harbor
-
Partial
PayPal commits that, if we conclude, in our sole discretion, that a disclosure respects and meets all the guidelines of these Program Terms and the PayPal Agreements, PayPal will not bring a private action against you or refer a matter for public inquiry.
- Hall of fame
-
Yes
Top hackers
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
8 assets you may test, 8 excluded.
Domains 2
- braintreepayments.com
- paypal.com
Products and areas 6
- Braintree Payments
- Hyperwallet
- PayPal
- Swift Financial/ Loanbuilder
- Venmo
- Xoom
Out of scope (8)
- www.paypal-support.com
- Chargehound
- Honey
- Paidy
- Payflow Gateway (Payflow Pro, Payflow Link, PayPal Manager, and associated pilot/test endpoints)
- Simility
- The braintree-web-drop-in SDK
- Zettle
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Braintree's policy. "We" in these lines means the program, not this site.
While testing
-
Do not cause any damage or disruption to our systems or services.
-
Do not modify any files or data, including permissions, and do not intentionally view or access any data beyond what is needed to prove the vulnerability.
-
Provide your IP address in the bug report (kept private, used only for testing activity review)
-
DoS proof-of-concept (PoC) testing is only permitted against applications where a sandbox environment is available.
-
Under no circumstances are researchers permitted to perform any denial-of-service (DoS) tests or attacks against any of PayPal's production systems
-
No Automated Scanning: Automated tools or scripts designed to overload our infrastructure, or services are not permitted for use in testing.
-
Once your report is closed, securely delete any inadvertently accessed data.
-
Uploading files that allow arbitrary commands (i.e. a webshell)
-
Creating and maintaining a persistent connection to the server
Not accepted
-
Any physical attacks against PayPal property or data centers
-
Username enumeration on customer facing systems
-
Scanner output or scanner-generated reports, including any automated or active exploit tool.
-
Man-in-the-Middle attacks.
-
Vulnerabilities involving stolen employee/consumer/merchant credentials or physical access to a device.
-
Social engineering attacks
-
Open redirection
-
Host header injections without a specific, demonstrable impact.
-
Vulnerabilities found through DDoS or spam attacks.
-
Self-XSS, which includes any payload entered by the victim.
-
Login/logout CSRF
-
Content spoofing without embedding an external link or JavaScript.
-
Issues related to SSL certificates.
-
DNS configuration issues
-
Server configuration issues (e.g. open ports, TLS versions, etc.)
-
Vulnerabilities only affecting users of outdated, unpatched, or unsupported browsers and platforms
-
Information disclosure of public or non-protected information
-
Exposed credentials that are either no longer valid, or do not pose a risk to an in-scope asset.
-
Vulnerabilities on third party libraries without showing specific impact to the target application
-
Reports that involve secondary business accounts, and the impact is limited solely to the parent account.
-
Denial of Service
-
Vulnerabilities requiring a rooted, jailbroken, or otherwise modified device
-
Exposure of non-sensitive data on the device
-
Vulnerabilities requiring extensive user interaction
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.