Chapa

Chapa Financial Technologies S.C

Get started

Chapa recognizes the importance of the security community in our quest to provide a safe and secure experience for our customers and stakeholders. So, if you are a security researcher that has found a vulnerability in any Chapa product or service, we would like to hear from you.

By submitting a security bug or vulnerability to Chapa through email, you acknowledge that you have read and agreed to the Program Terms and Conditions below. By providing a submission, you agree that you may not publicly disclose your findings or the contents of your submission to any third parties without Chapa’s prior written approval.

Submit Vulnerability via Email

You are about to submit a report to Chapa via Email. Please include detailed reporting and a working Proof of Concept.

send your report to bugs[at]chapa[dot]co


Program terms and conditions

  • You must show that you could exploit a vulnerability, but you must not exploit it. You must not: access, modify, copy, download, delete, compromise or otherwise misuse others’ data; access non-public information without authorization; degrade, interrupt or deny services to our users; and/or incur loss of funds that are not your own.
  • You must not leverage the existence of a vulnerability or access to sensitive or confidential data to make threats, extortionate demands, or ransom requests.
  • Your testing must not violate any applicable laws or regulations.
  • By providing a submission, you agree that you may not publicly disclose your findings or the contents of your submission to any third parties without Chapa’s prior written approval.
  • You will be responsible for any tax implications related to any bounty payment you receive, as determined by the laws of Ethiopia.
  • You must be 18 years of age or older.
  • You must not be employed by Chapa or any of its affiliates. You must also not be an immediate family member of someone employed by Chapa or any of its affiliates.
  • By reporting a bug, you grant Chapa and its affiliates a perpetual, irrevocable, worldwide, royalty-free license to use, copy, adapt, develop, create derivative work from, or share your submission for any purpose. You waive all claims arising from your submission, including breach of contract or implied-in-fact contract.
  • Whether to provide a payment for the disclosure of a bug and the amount of the payment is entirely at our discretion, and we may cancel or modify the program at any time.
  • Only the first responsibly-disclosed submission of a vulnerability instance will be marked as valid, and any subsequent reports will not be eligible for our program.

Ineligible Vulnerabilities 

Chapa does not consider the following to be eligible vulnerabilities:

  • Denial of service
  • Reports of spam
  • Social engineering
  • Self-XSS
  • Content/text spoofing
  • Unconfirmed reports from automated vulnerability scanners
  • Disclosure of server or software version numbers
  • Hypothetical subdomain takeovers without supporting evidence
  • Session invalidation or other improved security related to account
  • management when a credential is already known (e.g., password reset link
  • does not immediately expire, adding MFA does not expire other sessions, etc.)
  • Perceived security weaknesses without concrete evidence of the ability to compromise a user (e.g., missing rate limits, missing headers, etc.)
  • Reports exploiting the behaviour of, or vulnerabilities in, outdated browsers
  • User/merchant enumeration
  • Best practice reports without a valid exploit (e.g. use of “weak” TLS ciphers)

More Information at chapa