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
Sample Request & Response
The following fields ought to be included in the request body:
ReferenceId
String
15-digit reference id received in the validate requet response
MerchantId
String
Merchant code
ECardData
String
The encrypted card data encrypted using AES encryption with a 32-bit key. Explained below
ECardKey
String
ACS_CallbackURL
String
Explanation of the ECardData
Encryption Object
ECardData
Encryption ObjectThe 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:
Sample code to encrypt ECardData// Some code
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.
Last updated