3. Initiate Pay

Once the merchant request has been verified, this API is used to safely handle payment requests by encrypting card data using AES and RSA encryption.

API Endpoints

Production Endpoint

https://kwpaypg.casheer.com/COFWAY/InitiatePay

Sandbox Endpoint

Sample Request & Response

The following fields ought to be included in the request body:

Sample Request

 "Initiate pay request{
     "ReferenceId" : "xxxxxxxxx"
     "MerchantId": xxxxxx, 
     "ECardData" = "encryptedCard", 
      32BIT AES Encryption 
     "ECardKey" = "encryptedKey", 
     "ACS_CallbackURL"= "call back url for 3DS"+ReferenceId   
     }
     
 };

Sample Response

Field Name	Type	Description
ReferenceId	String	15-digit reference id received in the validate requet response
MerchantId	String	Merchant code provided by PSP
ECardData	String	The card data encrypted using AES encryption with a 32-bit key. Explained below
ECardKey	String	The AES encryption key, encrypted using an RSA public key generated at here
ACS_CallbackURL	String	Explained here

Explanation of the ECardData Encryption Object

The ECardData field in the request is an encrypted representation of the sensitive card details. The following explains the object that is encrypted using AES encryption before being included in the API request:

{
    "CardNumber": "xxxxxxxxxxxxxxxx",//16-digit card number
    "CardName": "John Doe", //Name mentioned on card
    "CardExpiry": "mm/yy", //month/year format
    "CardCVV": "xxx" //3 digit number
    "CardBrand" :"001" // 001 for VISA and 002 for MASTER CARD
}

Sample code to encrypt ECardData

AES Encryption C#

 
string aesKeyText = "jcIkNa3ybrNVWxe1GSxycA1ru4GoEETO"; // Generate a 32bit random alphanumeric Key
byte[] aesKey = Encoding.UTF8.GetBytes(aesKeyText);
byte[] IV = new byte[16]; // 16-byte IV initialized to zeros

var cardData = new
{
    CardNumber = "XXXXXXXXXXXXXXXXX",
    CardName = "John Doe",
    CardExpiry = "MM/YY",
    CardCVV = "XXX",
    "CardBrand" :"001"
};

string serializedCardData = JsonConvert.SerializeObject(cardData);
string encryptedData = EncryptStringToBytes_Aes(serializedCardData, aesKey, IV);



public static string EncryptStringToBytes_Aes(string plainText, byte[] Key, byte[] IV)
{
    
    using (Aes aesAlg = Aes.Create())
    {
        aesAlg.Key = Key;
        aesAlg.IV = IV;
        aesAlg.Mode = CipherMode.CBC;
        aesAlg.Padding = PaddingMode.PKCS7;

        using (var encryptor = aesAlg.CreateEncryptor(aesAlg.Key, aesAlg.IV))
        using (var msEncrypt = new MemoryStream())
        {
            using (var csEncrypt = new CryptoStream(msEncrypt, encryptor, CryptoStreamMode.Write))
            using (var swEncrypt = new StreamWriter(csEncrypt))
            {
                swEncrypt.Write(plainText);
            }
            return Convert.ToBase64String(msEncrypt.ToArray());
        }
    }
}

RSA Encryption C#

ACS_CallbackURL

• The provider will handle the 3D Secure callback if it is empty, and the user will be sent to the callback URL that was supplied in step 1. For more info about redirection refer here.

• If provided, the 3D Secure callback will be sent to the merchant's specified URL, and the merchant must call the API at here for further processing.

Response Explaination

Upon receiving the response from the InitiatePay API, the merchant must verify the errorCode to determine the next steps. If the errorCode is 0, indicating a successful initiation, the merchant should parse the result object and render the HTML content provided in result.redirect.html to proceed with the 3DS authentication process.