Encryption (Direct API) | Novalnet Docs

 Encryption (Direct API)

This section explains how you could initiate and handle the API call in Novalnet with encrypted parameters in request and response.

If your server has PCI-DSS compliant for credit card payments, you can directly send the card data (it must be in an encrypted format).

If the card is in the PSD2 region, you will receive the redirect URL(result.redirect_url) in response to authenticate the user. Also, you need to send the return URL (transaction.return_url) of your webshop here to redirect back the end-user to your webshop.

Integration Steps

Follow the below steps to perform the encryption process in your webshop,

Step 1: Generating an Unique Key

We need a unique key (A non-NULL Initialization Vector) to carry out the encryption & decryption techniques. It has to be created by you and included in the request header as the custom header (X-NN-Unique-Key).

Step 2: Header Setup

In the request header, you have to send the generated unique key in the X-NN-Unique-Key, and also, it should be a base64 encoded.

Before base64 encode the unique key, please store the unique key in your system, which will help to decrypt your response parameter(s). Since all the parameters in the response will be encrypted using the same unique key.

Step 3: Encrypting sensitive parameters

You can encrypt the sensitive data or all the request parameters before processing the transaction with Novalnet. The Payment access key and the generated unique key (from Step 1) are needed here to encrypt the parameters. However, irrespective of the encrypted parameters, Novalnet encrypts the entire payment response.

We highly recommend encrypting sensitive parameters like transaction.amount, transaction.test_mode, transaction.currency and transaction.payment_data parameters like card_number, card_cvc etc.,

Step 4: Submit the parameters to Novalnet

After handling the encryption technique, need to post the necessary parameters to Novalnet.

Each payment request is separated into so-called objects, which indicate an entity like Merchant, Customer, Transaction, etc. Use the objects which are relevant to your business model/payment type.

To know more about Direct API parameters, refer this >>link<<

Run

Step 5: Handling payment response

Once the customer completes the payment process, Novalnet will return the payment result in an encrypted format. You have to decrypt the result parameters using your Payment access key & generated a random unique key (from step 1).

Decrypt


If you received the redirect URL (result.redirect_url) in the response, please follow the steps (from 2 to 4) mentioned in the >>link<<.