Update Expire Transaction

This process is used if merchants want to force-fail their transaction. Merchant will send request to Espay system, and Espay will respond in json format as shown below

Flow

Merchant -> Espay

Method

HTTP Post

API URL

Development : https://sandbox-api.espay.id/rest/merchant/updateexpire
Production : https://api.espay.id/rest/merchant/updateexpire


Parameter Request:
Parameter Name Max Length Mandatory Description
uuid 64 Yes Request identifier. Unique id to identify these messages with other messages
rq_datetime 19 Yes Date and time in Espay application server when messages is sent
comm_code 32 Yes Merchant code listed in the Espay application
order_id 20 Yes Transaction Number / Invoice Id / unique id that identifies the order / billing / invoice.
tx_remark 50 Yes The reason for update transaction to fail/expire.
signature 64 Yes Signature required to validate by merchant, see page here for more detail

Parameter Response:
Parameter Name Max Length Mandatory Description
rq_uuid 4 Yes Request identifier. Unique id to identify these messages with other messages
rs_datetime 32 Yes Local date/time Espay server when messages are replied
error_code 4 Yes Error code of web service, 0000 means success
error_message 32 Yes Error description
tx_id 20 No Transaction ID generated by bank
  

Sample Request

POST /rest/merchant/updateexpire HTTP/1.1 Host: sandbox-api.espay.id Connection: keep-alive Content-Length: 250 Content-Type: application/x-www-form-urlencoded Accept: */* uuid=f105ad8c-528b-4ee2-b7c5-a974891bec27 &rq_datetime=2021-10-22 14:50:06 &comm_code=SGWADIRAKUSC &order_id=020121401334 &tx_remark=CANCELED &signature=c0ba7670c90dd6bc8ac94fb93d9afe402d836ce7f90f5d505fde5e6cfcc36634
  

Sample Response

{ { "rq_uuid": "baefa025e0ca44861a9076c8Z83fccxx", "rs_datetime": "2018-02-27 11:57:45", "error_code": "0000", "error_message": "", "tx_id": "SG31516158283435J" }