--- title: "Hosting the CSE library" description: "Host the Client-Side Encryption library on your server." url: "https://docs.adyen.com/online-payments/classic-integrations/classic-api-integration/client-side-encryption/hosting-the-cse-library" source_url: "https://docs.adyen.com/online-payments/classic-integrations/classic-api-integration/client-side-encryption/hosting-the-cse-library.md" canonical: "https://docs.adyen.com/online-payments/classic-integrations/classic-api-integration/client-side-encryption/hosting-the-cse-library" last_modified: "2019-04-22T23:28:00+02:00" language: "en" --- # Hosting the CSE library Host the Client-Side Encryption library on your server. [View source](/online-payments/classic-integrations/classic-api-integration/client-side-encryption/hosting-the-cse-library.md) **The Client-Side Encryption (CSE) Web integrations are being phased out**\ This means we are: * No longer developing the CSE integration. * Not accepting new CSE integrations. Switch to one of our latest [Web integrations](/online-payments/build-your-integration/sessions-flow?platform=Web), to accept payments on your website. Mobile integrations aren't affected. We strongly recommend that you let Adyen host the Client-Side Encryption (CSE) library for you, [while you are retrieving it from a unique URL](/online-payments/classic-integrations/classic-api-integration/client-side-encryption). However, you can optionally host this library by yourself or embed it into your form, as explained in this topic. ## Requirements * Get the [Public key from your Customer Area](/online-payments/classic-integrations/classic-api-integration/client-side-encryption/cse-library-public-key-location-and-token). Save a copy as you'll need it for using the CSE library to encrypt the payment details on the client side. ## Merchant hosted This integration binds to existing HTML in the page, adding a hidden input containing the encrypted card data to the form at the moment the form is submitted. The complete integration requires HTML markup to be present in the page, as well as accompanying JavaScript to enable the behavior. 1. Download `adyen.encrypt.min.js` and host it yourself. This supports both HTML-based and JavaScript-only integrations. 2. Download `adyen.encrypt.nodom.min.js` and host it yourself. Only supports JavaScript-only integration. ### Form template Build your payment form using this template and add a way to reference to this form from JavaScript. For example, define a unique `id` attribute value for this form by adding `id="adyen-encrypted-form"`. ```xml
``` Also, do the following: * For the `form.action` attribute, replace #handler to the payment handler URL on your server. * Card input fields should not have a `name` attribute, but are annotated by the `data-encrypted-name` attribute, to mark them for encryption. Replacing name with `data-encrypted-name` restricts raw card data from being posted to your servers and avoids impact transaction security and violate [PCI regulations](https://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Security_Standard). * Add a hidden `generationtime` field to include a server-side timestamp in the data you submit with the form. It determines whether a payment request is valid or not: transactions submitted later than 24 hours from the timestamp value are refused. * Format: [ISO 8601](http://www.w3.org/TR/NOTE-datetime); YYYY-MM-DDThh:mm:ss.sssTZD[](http://www.w3.org/TR/NOTE-datetime) * Example: *2017-07-17T13:42:40.428+01:00* The generation time value must be created server-side, because the client browser system clock may not be correctly synchronized, which would cause the payment transaction to fail. ### JavaScript In addition to the above the HTML template, there are two variants to including the library. The original plain JavaScript variant relies on a global `adyen.encrypt` object, while on popular demand an AMD style module has been added. ### Plain JavaScript Include the Adyen encryption library to your page. ```xml ``` Enrich a form in your page with the library on submit and (optionally) validation behaviors. ```js // The form element to encrypt. var form = document.getElementById('adyen-encrypted-form'); // The public key. var key = "your key as retrieved from the Customer Area Web Service user page"; // Form and encryption options. See adyen.encrypt.simple.html for details. var options = {}; // Bind encryption to the form. adyen.encrypt.createEncryptedForm(form, key, options); ``` ### Require.js Make sure that you include require.js or an alternative AMD module loader in your page. ```xml ``` You can either rename the `adyen.encrypt.min.js` to `adyen/encrypt.js`, or add a paths configuration: ```xml // Your paths config, or rename the adyen.encrypt.min.js to adyen/encrypt.js require.config({ paths: { 'adyen/encrypt' : '../simple/js/adyen.encrypt.min' } }); ``` In the `main.js` or a similar file, enrich the form using a `require` call. ```js require(['adyen/encrypt'], function(adyenEncrypt) { // The form element to encrypt. var form = document.getElementById('adyen-encrypted-form'); // The public key. var key = "your key as retrieved from the Customer Area Web Service user page"; // Form and encryption options. See adyen.encrypt.simple.html for details var options = {}; // Bind encryption to the form. adyenEncrypt.createEncryptedForm(form, key, options); }); ``` ## JavaScript only In case the HTML integration does not fulfill your setup requirements, the library has been split up into two parts. The newly introduced part is an HTML-independent encryption. Make sure that you encrypt the card data before sending to your server. ```xml ```