Documentation Monext Online

Arborescence des pages


Content




Introduction

This function allow merchants to use a double layer encryption :

  • The whole traffic is encrypted through the SSL tunnel ;
  • The card object is encrypted inside the message.

Please contact our sales team to access this feature.

Encryption step

The processing takes place in 3 steps: 

  1. The merchant requests parameters to generate the encryption key.
  2. The merchant encrypts the sensitive data on his server.
  3. The merchant calls the Payline web services with the encrypted data.


How to integrate

To start this step, you must have a merchant and a merchant access key.

You must integrate Payline web services and know RSA data encryption :

  • getEncryptionKey : allows you to retrieve the encryption settings to encrypt your message. 


Step 1 : Call the getEncryptionKey to obtain the key.

Merchant calls the getEncryptionKey service on the usual endpoint.

This service can be called multiple times if needed (for instance multiple place to store the public key).
The parameters are the version and merchantKeyName. It must be set to 32.

You must integrate the Payline web services: 

  • The merchant performs a getEncryptionKey : retrieves the encryption parameters.
  • The merchant retrieves the encryption parameters and the key.keyId from getEncryptionKey.

These data must be stored by the merchant in order to encrypt further messages.


If the merchantKeyName don't respect the format, you will receive the following error : 02204 - ERROR


Process for the call response with multiple keys (version 32) 

If keypair named with the "merchantKeyName" filled in, does not exist /OR/ keypair named with the "merchantKeyName" filled in exists and dateKeyPair > 60 :

  • Generate new key pair named "merchantKeyName" and return a new public key

If keypair named with the "merchantKeyName" filled in exists and dateKeyPair < 60 :

  • Return current public key


This service returns the key details:

  • RSA public key details (alogorithm, size, exponent, ...);
  • Key expiration date;
  • Key ID.
  • merchantKeyName;

These data must be stored by the merchant in order to encrypt further messages.


Step 2 : Encrypt the card data with the public key 

  



Step 3 : Calls the Payline web services with the encrypted data.



Example encryption function 

 



List of Key/Value accepted
The following keys are accepted in the encrypted data:
CardNumbercard.number497010000000006
ExpDatecard.expirationDate0220
CVXcard.cvx123
OwnerBirthDatecard.ownerBirthdayDate31121980
Passwordcard.passwordPayline01$
Cardholdercard.cardholderJeremy Mattio

Key renewal
A key is valid for 90 days. A new key will be issued 30 days before the previous key expiration. During this period both keys are valid and usable.
A merchant has 30 days to change the key in its systems before the old key become unusable.
A good practice is to call the getEncryptionKey everyday, and to start the renew process as soon as a new key ID is received by the merchant

In order to prevent misuse and not to saturate the database, the system refuses a generation of a new key, if there are more than 100 active keys simultaneously.
So, at each key draw, the system looks for the number of active key pairs (whose life date is <= 90 days) by taking the unique name of the key (disctinct merchantKeyName) .

If a merchant has more than 100 active keys at the same time, the system rejects a new key issue with code 02203 - ERROR.
Security
The key is unique per merchant.
The current key specification are :
  • Algorithm : RSA 
  • Key size : 2048
  • Cipher : RSA/ECB/OAEPWithSHA-256AndMGF1Padding





























































Code example
Encryption function code example used by merchant to encrypt the message.

 

  Example encryption function
 

 

  
public void getRSAEncodedMessage() throws Exception{
    String message = "CardNumber=497010000000006,ExpDate=0220,CVX=123,OwnerBirthDate=,Password=Payline1,Cardholder=Alain Durand";
    String cipherName = "RSA/ECB/OAEPWithSHA-256AndMGF1Padding";
    Cipher cipher = Cipher.getInstance(cipherName);
    String algo = "RSA";
    String modulus = "AOLndIya3+ViAuP07V1Ky+YRuZK6zsMUsVIPP3xhFCS1CSJb9oBLmmzkMMASAn0TQ7BrELuNbY1+9VT30ah1N0mX0BzIBqE5sojV+CkafF+LtIntpF1wUhguXlcFOXcBLCECiMA4gBqHJMrVxnF626M1S6Wi2++WUwFgPTtHdn4B7e0RMvWqFr6uKBDq1qhdP8iziiAn/YPPp5ObgxuabWvPAZvRMDmgflNLYCOZB05LjZXMDvkLaYy244iY0tmVWwa7WYi2lJ7N0wK6gpDXD1WQh42AQuyVQX9i/m3oOjH8iqdRZG8FuaoHkBtON9zhz+ZyuBAwb+zNZWBDvnp6V0E=";
    String publicExponent = "AQAB";
 
    final KeyFactory fact = KeyFactory.getInstance(algo);
    PublicKey publicKey =  fact.generatePublic(new RSAPublicKeySpec(new BigInteger(Base64.decodeBase64(modulus.getBytes())), new BigInteger(Base64.decodeBase64(publicExponent.getBytes()))));
    System.out.println("Message encoded : " + Base64.encodeBase64String(encrypt(cipher, publicKey, message)));
}
 
 
public static byte[] encrypt(Cipher cipher, Key key, String message) throws Exception {
    cipher.init(Cipher.ENCRYPT_MODE, key);
    return cipher.doFinal(message.getBytes());
}