BackOffice


A merchant can perform following BackOffice operations using our REST API.

   In the ID field you will receive the referencedPaymentId as value.

How to Capture an Authorization?

If you want to clear previously authorized funds you have to use capture against a preauthorization payment. You can choose between full and partial capture.

The paymentID will be referred and a POST request will be send over HTTPS to the /transactionServices/REST/v1/payments/{id} endpoint.

To Capture the transaction, you have to send the paymentType as CP.


How to Refund a Payment?

To Refund the transaction, you have to send the paymentType as RF.

The paymentID has to be send with a POST request over HTTPS to the /transactionServices/REST/v1/payments/{id} endpoint.

You can refund previous payments and a refund is allowed against debits or captured payment types.


How to Reverse/Cancel a Payment?

To Reverse/ Cancel the transaction you have to send the paymentType as RV.

The paymentID has to be send with a POST request over HTTPS to the /transactionServices/REST/v1/payments/{id} endpoint.

You can cancel previous payments and a cancelation is allowed against preauthorized payment types.

   Partial reversal is not possible.

How to Inquire about a Payment?

To Inquire a transaction you have to send the paymentType as IN.

The paymentID has to be send with a POST request over HTTPS to the /transactionServices/REST/v1/payments/{id} endpoint.

The merchant can retrieve detailed information of previously placed transactions through the Inquiry/ Status request.


   Merchant needs to set authentication token in header for each request. To generate authentication token, please refer Auth token API.

Sample Request


Sample Response


How to Get All Transactions List?

Transaction List request has to be sent to our REST endpoint i.e. transactionServices/REST/v1/getTransactionList using POST method.


   To get transaction list merchant first needs to generate authentication token and set it in header. To generate auth token please refer Auth token API.

Sample Request


Sample Response


Hashing Rule

is supporting MD5 Cryptographic Hash for the authenticity of payment request send to the server.


Below are the description of fields used for generating checksum:
  • memberId <Merchant ID as shared by >
  • secureKey <Secure Key that can be generated through 's dashboard>
  • paymentId <Id of previous transaction>

How to generate Checksum?

Checksum has to be calculated with following combination & needs to be send along with the authentication parameters in each server-to-server request:

Capture And Refund Payment:
<memberId>|<secureKey>|<paymentId>|<amount>

Inquire & Cancel Payment:
<memberId>|<secureKey>|<paymentId>

Get all transactions list:
<memberId>|<secureKey>


Sample Code