Loading
Loading
Mesta Payments LLC ("Mesta", "we") welcomes good-faith security research on the Mesta developer sandbox. This policy says what you may test, how to report what you find, and what we commit to in return.
This is the vulnerability disclosure policy referred to in section 13 of the Mesta Sandbox Terms. Where this policy and the Terms differ on security testing, this policy governs. In all other respects the Terms apply.
Effective date: 17 November 2026. Version 1.0.
Only the systems listed as in scope are covered. This policy does not authorize testing anything else.
To report an issue in Mesta's production systems or the mesta.xyz website, write to security@mesta.xyz.
Not accepted as vulnerabilities unless you show a concrete security impact:
Email security@mesta.xyz. A good report includes:
You may report anonymously, though we then cannot update you. Do not put real personal data, credentials or secrets in your report; describe them instead.
To be covered by section 5, you must:
Research carried out in good faith and in line with this policy is authorized by Mesta. For that research, Mesta:
Limits. This commitment does not cover research outside scope or in breach of section 4, and it ends if you act in bad faith. Mesta cannot authorize testing of other companies' systems, and cannot bind law enforcement, regulators or other third parties. If a third party takes action against you over research this policy covers, tell us and we will do what we reasonably can to make clear it was authorized.
This authorization does not affect the limitation of liability in section 19 of the Sandbox Terms, which continues to apply.
Mesta aims to acknowledge reports within 3 business days and to fix confirmed issues within 90 days. These are targets, not guarantees.
| Stage | Mesta's target |
|---|---|
| Acknowledge your report | 3 business days |
| Confirm or decline the issue, with reasons | 10 business days |
| Progress updates | At least every 30 days |
| Fix confirmed issues | 90 days, sooner for critical issues |
Please do not disclose the issue publicly until it is fixed or 90 days have passed since your report, whichever comes first. If a fix needs longer, we will explain why and agree a new date with you. Give us at least 5 business days' notice of what you plan to publish, and leave out any personal data or secrets.
Your personal data. We use what you give us only to handle your report and contact you, as described in Mesta's privacy policy at mesta.xyz/privacy. The details of your sandbox account are covered by the Sandbox Privacy Notice. We will not share your identity outside Mesta without your consent, except with providers helping us fix the issue under a duty of confidentiality, or where the law requires it.
Your report. You keep ownership of your report. By submitting it, you give Mesta a non-exclusive, worldwide, perpetual, royalty-free license to use, copy and share it to investigate and fix the issue and to protect Mesta's users. You confirm the report is your own work and that you are free to share it.
Sanctions. Mesta cannot correspond with, credit or provide anything to a person subject to U.S. sanctions or located in a comprehensively sanctioned country or region. We may still act on a report from such a person.
No reward. Mesta does not run a bug bounty and does not pay for reports. With your permission, we will thank you by name or handle once the issue is fixed.
No other relationship. Reporting under this policy does not make you an employee, contractor or agent of Mesta, and creates no obligation on Mesta beyond what this policy states.
Changes. Mesta may update this policy by publishing a new version with a new effective date. A change does not withdraw the protection in section 5 for research already carried out under an earlier version.
Questions. Send questions about this policy to the reporting address in section 3.