Use this section to tell people about which versions of your project are currently being supported with security updates.

We take the security of the ABT2Pay API Integration project seriously. If you believe you have found a security vulnerability, please report it to us as described below.

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report them via email to security@abt2pay.com.

You should receive a response within 48 hours. If for some reason you do not, please follow up via email to ensure we received your original message.

Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:

• Type of issue (e.g., buffer overflow, SQL injection, cross-site scripting, etc.)
• Full paths of source file(s) related to the vulnerability
• The location of the affected source code (tag/branch/commit or direct URL)
• Any special configuration required to reproduce the issue
• Step-by-step instructions to reproduce the issue
• Proof-of-concept or exploit code (if possible)
• Impact of the issue, including how an attacker might exploit it

This information will help us triage your report more quickly.

We prefer all communications to be in English.

The ABT2Pay API Integration project follows the principle of Responsible Disclosure.

When using this API integration:

1. Never commit API keys or sensitive credentials to version control
2. Use environment variables for configuration
3. Validate all input before sending to the API
4. Implement proper error handling to avoid information leakage
5. Use HTTPS for all API communications
6. Keep dependencies updated to avoid known vulnerabilities
7. Implement rate limiting to prevent abuse
8. Log security events for monitoring and auditing

Before deploying to production:

• API keys are stored securely (environment variables, secret management)
• Input validation is implemented
• Error messages don't leak sensitive information
• HTTPS is enforced
• Dependencies are up to date
• Security headers are configured
• Rate limiting is implemented
• Logging is configured for security events

• 48 hours - Initial response to security report
• 7 days - Status update and timeline for fix
• 30 days - Public disclosure (if not fixed)
• 90 days - Public disclosure (regardless of fix status)

Security updates will be released as patch versions (e.g., 1.0.1, 1.0.2) and will be clearly marked in the release notes.

We would like to thank all security researchers who responsibly disclose vulnerabilities to us. Their contributions help make our project more secure for everyone.

Thank you for helping keep the ABT2Pay API Integration project secure! 🔒