Bug bounty program

GovPayPlan welcomes good-faith security research and offers monetary rewards for eligible, first-to-report vulnerabilities. Reports are accepted only by email at [email protected].

Monetary rewardsEmail-only reportingGood-faith safe harborCoordinated disclosure

Report a vulnerability

Email [email protected]. This email address is the only accepted submission channel. Reports sent through sales, support, agency contacts, social media, or third-party platforms are not accepted into the program.

Use the subject “GovPayPlan security vulnerability report” and include:

  • The affected hostname, endpoint, and vulnerability type.
  • Reproducible steps and a minimal proof of concept using your own test data.
  • The demonstrated impact, with redacted requests or screenshots where useful.
  • The time of testing and your test account identifier so we can investigate.

Do not email passwords, API keys, full card numbers, or customer records. If sensitive evidence is needed, ask us to arrange a secure exchange through the same email address.

Email a security report

Before you test

Use accounts and data you own or are authorized to use. Stop if you encounter personal, payment, government, or another customer’s data, and report the issue without retaining or sharing that data.

Program scope

Only the exact GovPayPlan-controlled hostnames listed below are authorized for testing under this program. This is not a wildcard authorization for other subdomains.

In scope

  • govpayplan.com
  • www.govpayplan.com
  • app.govpayplan.com
  • help.govpayplan.com
  • api.govpayplan.com
  • demo.govpayments.io

Explicitly out of scope

  • payments.govpayplan.com
  • portal.govpayplan.com
  • All Payrix and Payrix Canada systems
  • Any other third-party service or infrastructure

Agency systems

Government agency websites, agency-owned domains and networks, agency staff accounts, and custom domains that point to GovPayPlan are out of scope unless GovPayPlan gives you written authorization naming the exact asset.

Scope applies to the hostname and service you are testing, not to every system it connects to. A link, redirect, embedded payment form, shared IP address, or CNAME does not authorize testing the destination or its infrastructure. If a flow reaches Payrix or another excluded system, stop testing that part of the flow.

Research rules

Make a good-faith effort to avoid privacy violations, interruption of service, degradation of systems, and destruction or modification of data. Test only what is necessary to demonstrate the vulnerability and its impact.

Do not perform:

  • Denial-of-service, load, stress, resource-exhaustion, or automated high-volume testing.
  • Social engineering, phishing, impersonation, spam, or attacks against employees, agencies, payers, vendors, or support channels.
  • Physical testing, credential stuffing, password spraying, or use of credentials obtained from third parties.
  • Destructive testing, persistence, lateral movement, malware deployment, or modification of production data.
  • Accessing, downloading, changing, deleting, or sharing data that does not belong to you beyond the minimum necessary to establish that exposure exists.
  • Testing against Payrix, Payrix Canada, payment-network infrastructure, banks, government agencies, or any other third party.

Eligible reports

To be eligible, you must be the first person to report a previously unknown vulnerability, follow this policy, provide enough information for us to reproduce the issue, and cooperate with reasonable validation questions. A finding must demonstrate a meaningful security impact; scanner output or a theoretical concern without an exploitable condition is not sufficient.

Commonly ineligible reports include duplicates, previously known issues, missing security headers without demonstrated impact, self-XSS, clickjacking on pages without sensitive actions, rate-limit observations without a practical attack, software version disclosure, and findings that affect only unsupported browsers or obsolete software.

Rewards

Eligible findings may receive a monetary reward. Reward amounts are determined after validation based on severity, exploitability, demonstrated impact, report quality, and whether the issue affects multiple assets. Multiple symptoms caused by one underlying issue are treated as one finding. GovPayPlan confirms the reward in writing and may decline rewards for duplicate, known, ineligible, or policy-violating reports.

There is no published minimum or maximum reward. We assess the demonstrated impact on account access, customer data, payment integrity, and agency operations. You do not need to increase the impact of an exploit, access another person’s records, or complete a real payment to qualify.

What to expect

  • We acknowledge email reports and request any information needed to reproduce the finding.
  • We review scope, eligibility, and demonstrated impact during initial triage.
  • We will provide material status updates while a validated issue is being remediated.
  • Reward decisions are made after validation and may require identity and payment information through a separate secure process.

Safe harbor

If you make a good-faith effort to comply with this policy, we will treat your research as authorized under this program and will not pursue legal action based solely on that research. If a third party initiates legal action related to compliant research, we may confirm that your activity was conducted under this program. This safe harbor does not authorize activity against third-party systems, excuse violations of law, or bind organizations other than GovPayPlan and eCourtDate.

Coordinated disclosure

Do not publicly disclose a suspected or confirmed vulnerability, customer information, or technical details without written permission from GovPayPlan. We will work with researchers on a reasonable coordinated-disclosure timeline after the issue is validated and remediated.

Contact

Send reports only to [email protected]. For non-security questions, use the contact page.