Merchant should use SALES (SALS) for most of the use cases and avoid Pre-Authorization & Capture model. This is because many merchant will miss the auto-release period before they can actually capture the funds. Merchant who uses preauth or authorize payment mode may capture the transaction at a later stage by using this API

Response

Variable / Parameter	Type Format / Max Length	Description / Example
TranID	integer, 20 digits	Unique transaction ID for tracking purposes
Domain	alphanumeric, 32 chars	Merchant ID in PG system.
VrfKey	32 chars hexadecimal string	This is the data integrity protection hash string
StatCode	string of 2-digit numeric	00 = Success, 11 = Failure, 12 = Invalid or unmatched security hash string, 13 = Not a credit card transaction, 15 = Requested day is on settlement day, 16 = Forbidden transaction, 17 = Transaction not found, 18 = Missing required parameter, 19 = Domain not found, 20 = Temporary out of service, 21 = Authorization expired, 23 = Not allowed to perform partial capture, 24 = Transaction has already been captured., 25 = Amount requested more than available capture amount, 99 = General Error(Please check with PG Support)
StatDate	date (YYYY-MM-DD)	Response date & time
PartialCaptureTranID	integer, 20 digits	Created upon successful partial capture request

Formula of skey & VrfKey

skey = md5( txnID + amount + domain + verify_key )
VrfKey = md5( secret_key + Domain + TranID + StatCode )

200