Payment Statuses

TX type	Event	Status
Received	Immediate	PENDING
Approved	Temporary	SUCCESS
Failed	Temporary	FAIL
Failed	Final	REJECTED, REVERSED

Status Flow

Immediate Response	Callback	Potential Callback
REJECTED
PENDING	SUCCESS	REVERSED

Each postback is a general HTTP POST request. The final amount in the postback may differ from the initial payment amount; therefore, the merchant must verify and update the amount value when receiving the postback. Multiple payment requests with the same orderId are allowed. Each payment gets its own unique id.

Payment Postback Table

Title	Format	Explanation
id	String	System Transaction ID
orderId	String	Merchant Order ID
status	String	Transaction status
amount	double	Transaction amount
currency	String	Alphabetic currency code, e.g. INR
hash	String	Data signature for encryption

Postback Payload

header name ‘apikey’, header value <merchant-apikey>

{

  "id": "912z-1zs4-acvb-1bre3",

  "orderId": "merchtx12345",

  "status": "SUCCESS",

  "amount": 100.00,

  "currency": "PKR",

  "hash": "<system-generated-hash>"

}

Callback- & Return URLs

Value	Description	Format	Provided by
callbackUrl	Callback/postbacks are sent here	string	Merchant
returnUrl	Customer is returned here after payment	string	Merchant
paymentUrl	The payment page to serve the customer	string	PSP

Data Signature of Payload

Encryption Variables	Values and explanations
apikey	<confidential>
Secret key	<confidential>
Encryption format	Concatenated and signed by using SHA-256 algorithm
Parameter order	The order must be in exact order as per below sample
Parameter example	secretKey=xxx&amount=xx.xx&currency=xx&id=xx&orderId=xx&status=xx
Amount format	2 digits after comma Ex: 100.999 -> 100.99, 100 -> 100.00
Result string	Will be signed using SHA-256