Card numbers encrypted with AES-256

Learn how Paayes handles security.

A PCI-certified auditor has audited Paayes. We’re a certified PCI Service Provider Level 1. This is the most stringent level of certification available in the payments industry. To accomplish this, we use the best-in-class security tools and practices to maintain a high level of security at Paayes.

HTTPS and HSTS for secure connections
Paayes forces HTTPS for all services using TLS (SSL), including our public website and the Dashboard to ensure secure connections:
Paayes.js is served only over TLS.
Paayes’s official libraries connect to Paayes’s servers over TLS and verify TLS certificates on each connection.

We regularly audit the details of our implementation, including the certificates we serve, the certificate authorities we use, and the ciphers we support. We use HSTS to ensure that browsers interact with Paayes only over HTTPS. Paayes is also on the HSTS preloaded lists for both Google Chrome and Mozilla Firefox.

Sensitive data and communication encryption
All card numbers are encrypted at rest with AES-256. Decryption keys are stored on separate machines. None of Paayes’s internal servers and daemons can obtain plain text card numbers but can request that cards are sent to a service provider on a static allowlist. Paayes’s infrastructure for storing, decrypting, and transmitting card numbers runs in a separate hosting environment, and doesn’t share any credentials with Paayes’s primary services including our API and website.

Vulnerability disclosure and reward program
By submitting a security bug or vulnerability to Paayes through HackerOne, you acknowledge that you’ve read and agreed to the program terms and conditions. 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 Paayes’s prior written approval. Valid and in-scope reports might be eligible for a payment.