's Tutorials



80%

Card Registration


Card Registration makes your transaction easier. Once you register your card , you don't have to enter all the payment data every time. Because the data will be stored. This makes it possilble to use the data later . Card Registration is a Stand-alone feature which means that you directly receive an object with the registration id.

Card Registration request has to be sent to our endpoint i.e. /transaction/CardRegistration using POST method.


In our API Specifications you can find a full list of parameters that can be sent in the initial request.

Sample Request

Sample code for reading the response

Hashing Rule For Request

supports MD5 Cryptographic Hash for the authenticity of payment request sent to the server.


Below are the description of fields used for generating checksum.
  • memberId <Merchant ID as shared by >
  • totype <Name of PSP>
  • secureKey <Secure Key that can be generated through 's dashboard>

How to generate Checksum for request ?

Checksum can be calculated with the following combination and needs to be send along with the authentication parameters in each server-to-server request:
<memberId>|<toType>|<secureKey>

Sample Code

Hashing Rule For Response

supports MD5 Cryptographic Hash for the authenticity of payment response to be sent to the merchant.


Below are the description of fields used for generating checksum.
  • memberId <Merchant ID as shared by >
  • status <Response status>
  • secureKey <Secure Key that can be generated through 's dashboard>

How to generate Checksum for response ?

Checksum can be calculated with the following combination and needs to be send along with the authentication parameters in each server-to-server request:
<memberId>|<status>|<secureKey>