Online Cards/ Phone/ Paypal
KEEMAT would like to inform you that we (the merchant) are responsible for website transactions.
Credit or debit card details are entered on a secured page and transferred using SSL (secure sockets layer) from Stripe. This provides a secure connection allowing us to transmit private data online.
In order to make any payments online, we will require you to supply your card information.
You will have to provide us with CVV2 (card verification value)/CVC2 (card validation code). These numbers are usually displayed on your card (last three digits on the back of your credit or debit card).
KEEEMAT accepts 3-D Secure transactions
3-D Secure was developed by Visa® and Mastercard® to guard you against unauthorised use of your card while shopping online with participating merchants. It works on the same principle as chip and pin and once enrolled you'll have the added confidence knowing that MasterCard SecureCode® or Verified by Visa® performs an extra authentication step to protect your account from unauthorised users online.
How does it work:
For instance, whenever someone makes a purchase from a vendor who is using 3-D Secure. The payment system automatically prompts the card holder to provide more information to verify that they are owners of that credit card. This authentication is usually carried out by prompting the card holder to input a pre-specified password. Once correct information is provided, the system verifies that information from the user’s bank, thus completing a secure cycle where any unauthorized person should not be able to use the credit card.
The 3-D secure transactions will be processed by Stripe
You can find listed below all information related to the Stripe online payments system:
Security is one of the biggest considerations in everything we do. If you have any questions after reading this, or encounter any issues, please contact us at [email protected].
Stripe has been audited by a PCI-certified auditor, and is certified to PCI Service Provider Level 1. This is the most stringent level of certification available.
SSL and HSTS
Stripe forces HTTPS for all services, including our public website. We regularly audit the details of our implementation: the certificates we serve, the certificate authorities we use, and the ciphers we support. We use HSTS to ensure browsers interact with Stripe only over HTTPS. Stripe is also on the HSTS preloaded lists for both Chrome and Firefox.
For more about implementing SSL on your own website, read our SSL guide.
All card numbers are encrypted on disk with AES-256. Decryption keys are stored on separate machines. None of Stripe's internal servers and daemons are able to obtain plaintext card numbers; instead, they can just request that cards be sent to a service provider on a static whitelist. Stripe's infrastructure for storing, decrypting, and transmitting card numbers runs in separate hosting infrastructure, and doesn't share any credentials with Stripe's primary services (API, website, etc.).
We rapidly investigate all reported security issues. If you believe you've discovered a bug in Stripe's security, please get in touch at [email protected] (optionally using our PGP key at the bottom of this page). We will respond as quickly as possible to your report. We request that you not publicly disclose the issue until it has been addressed by Stripe.
Vulnerability Reward Program
We understand the hard work that goes into security research. To show our appreciation for researchers who help us keep our users safe, we operate a reward program for responsibly disclosed vulnerabilities. Stripe rewards the confidential disclosure of any design or implementation issue that could be used to compromise the confidentiality or integrity of our users' data (such as by bypassing our login process, injecting code into another user's session, or instigating action on another user's behalf). A minimum reward of $500 USD may be provided for the disclosure of qualifying bugs. At our discretion, we may increase the reward amount based on the creativity or severity of the bugs.
If you report a vulnerability that does not qualify under the above criteria, we may still provide a minimum reward of $100 USD if your report causes us to take specific action to improve Stripe's security.
As with most security reward programs, we ask that you use common sense when looking for security bugs. Vulnerabilities must be disclosed to us privately with reasonable time to respond, and avoid compromise of other users and accounts, or loss of funds that are not your own. We do not reward denial of service, spam, or social engineering vulnerabilities. Although Stripe itself and all services offered by Stripe are eligible, vulnerabilities in third-party applications that use Stripe are not.
And finally, as with most security reward programs, we have a couple restrictions:
We will only reward the first person to responsibly disclose a bug to us.
Any bugs that are publicly disclosed without providing us a reasonable time to respond will not be rewarded.
Whether to reward the disclosure of a bug and the amount of the reward is entirely at our discretion, and we may cancel the program at any time.
Your testing must not violate any laws.
We can't provide you a reward if it would be illegal for us to do so, such as to residents of countries under current U.S. sanctions (e.g., North Korea or Libya).