Developer
php-encryption ===============  [](https://codecov.io/gh/defuse/php-encryption) [](https://packagist.org/packages/defuse/php-encryption) [](https://packagist.org/packages/defuse/php-encryption) [](https://packagist.org/packages/defuse/php-encryption) ```terminal composer require defuse/php-encryption ``` This is a library for encrypting data with a key or password in PHP. **It requires PHP 5.6 or newer and OpenSSL 1.0.1 or newer.** We recommend using a version of PHP that [still has security support](https://www.php.net/supported-versions.php), which at the time of writing means PHP 8.0 or later. Using this library with an unsupported version of PHP could lead to security vulnerabilities. The current version of `php-encryption` is v2.4.0. This library is expected to remain stable and supported by its authors with security and bugfixes until at least January 1st, 2024. The library is a joint effort between [Taylor Hornby](https://defuse.ca/) and [Scott Arciszewski](https://paragonie.com/blog/author/scott-arcizewski) as well as numerous open-source contributors. What separates this library from other PHP encryption libraries is, firstly, that it is secure. The authors used to encounter insecure PHP encryption code on a daily basis, so they created this library to bring more security to the ecosystem. Secondly, this library is "difficult to misuse." Like [libsodium](https://github.com/jedisct1/libsodium), its API is designed to be easy to use in a secure way and hard to use in an insecure way. Dependencies ------------ This library requires no special dependencies except for PHP 5.6 or newer with the OpenSSL extensions (version 1.0.1 or later) enabled (this is the default). It uses [random\_compat](https://github.com/paragonie/random_compat), which is bundled in with this library so that your users will not need to follow any special installation steps. Getting Started ---------------- Start with the [**Tutorial**](docs/Tutorial.md). You can find instructions for obtaining this library's code securely in the [Installing and Verifying](docs/InstallingAndVerifying.md) documentation. After you've read the tutorial and got the code, refer to the formal documentation for each of the classes this library provides: - [Crypto](docs/classes/Crypto.md) - [File](docs/classes/File.md) - [Key](docs/classes/Key.md) - [KeyProtectedByPassword](docs/classes/KeyProtectedByPassword.md) If you encounter difficulties, see the [FAQ](docs/FAQ.md) answers. The fixes to the most commonly-reported problems are explained there. If you're a cryptographer and want to understand the nitty-gritty details of how this library works, look at the [Cryptography Details](docs/CryptoDetails.md) documentation. If you're interested in contributing to this library, see the [Internal Developer Documentation](docs/InternalDeveloperDocs.md). Other Language Support ---------------------- This library is intended for server-side PHP software that needs to encrypt data at rest. If you are building software that needs to encrypt client-side, or building a system that requires cross-platform encryption/decryption support, we strongly recommend using [libsodium](https://download.libsodium.org/doc/bindings_for_other_languages) instead. Examples --------- If the documentation is not enough for you to understand how to use this library, then you can look at an example project that uses this library: - [encutil](https://github.com/defuse/encutil) - [fileencrypt](https://github.com/tsusanka/fileencrypt) Security Audit Status --------------------- This code has not been subjected to a formal, paid, security audit. However, it has received lots of review from members of the PHP security community, and the authors are experienced with cryptography. In all likelihood, you are safer using this library than almost any other encryption library for PHP. If you use this library as a part of your business and would like to help fund a formal audit, please [contact Taylor Hornby](https://defuse.ca/contact.htm). Public Keys ------------ The GnuPG public key used to sign current and older releases is available in [dist/signingkey.asc](https://github.com/defuse/php-encryption/raw/master/dist/signingkey.asc). Its fingerprint is: ``` 2FA6 1D8D 99B9 2658 6BAC 3D53 385E E055 A129 1538 ``` You can verify it against Taylor Hornby's [contact page](https://defuse.ca/contact.htm) and [twitter](https://twitter.com/DefuseSec/status/723741424253059074). Due to the old key expiring, new releases will be signed with a new public key available in [dist/signingkey-new.asc](https://github.com/defuse/php-encryption/raw/master/dist/signingkey-new.asc). Its fingerprint is: ``` 6DD6 E677 0281 5846 FC85 25A3 DD2E 507F 7BDB 1669 ``` A signature of this new key by the old key is available in [dist/signingkey-new.asc.sig](https://github.com/defuse/php-encryption/raw/master/dist/signingkey-new.asc.sig).
Developer
The Kueue Pay Payment Gateway is an innovative technology that facilitates seamless and secure transactions between merchants and their customers. It enables businesses to accept debit and credit card payments both online and in physical stores.
The Kueue Pay Payment Gateway acts as a bridge between a merchant’s website or point-of-sale system and the payment processing network. It securely transmits payment information, authorizes transactions, and provides real-time status updates.
The Kueue Pay Developer API empowers developers and entrepreneurs to integrate the Kueue Pay Payment Gateway directly into their websites or applications. This streamlines the payment process for customers and provides businesses with a customizable and efficient payment solution.
To access the Kueue Pay Developer API, you need to sign up for a developer account on our platform. Once registered, you’ll receive an API key that you can use to authenticate your API requests.
The Kueue Pay Developer API allows you to initiate payments, check the status of payments, and process refunds. You can create a seamless payment experience for your customers while maintaining control over transaction management.
Yes, the Kueue Pay Developer API is designed to accommodate businesses of varying sizes and industries. Whether you’re a small online store or a large enterprise, our API can be tailored to fit your specific payment needs.
The Kueue Pay Developer API is designed with simplicity and ease of use in mind. Our comprehensive documentation, code samples, and developer support resources ensure a smooth integration process for any web platform.
We offer competitive pricing plans for using the Kueue Pay Payment Gateway and Developer API. Details about fees and pricing tiers can be found on our developer portal.
Absolutely, the Kueue Pay Developer API offers customization options that allow you to tailor the payment experience to match your brand and user interface. You can create a seamless and cohesive payment journey for your customers.
We provide dedicated developer support to assist you with any issues or questions you may have during the API integration process. Reach out to our support team at developersupport@NFCPay.com for prompt assistance.
Remember, our goal is to empower your business with a robust and efficient payment solution. If you have any additional questions or concerns, feel free to explore our developer portal or contact our support team.