Merchant History List

This API is used to get merchant transaction history in list format within a selected date range.

Technical Specification

Environment	Method	URL
Development	POST	https://snapstag.finnet.co.id/topup/v1.0/transaction-history-list-merchant

Required Headers

No	Name	Type	Mandatory	Description
1	Content-Type	String	M	Fill with application/json
2	Authorization	String	M	Bearer <access_token>
3	X-TIMESTAMP	String	M	Timestamp in RFC3339 format: yyyy-MM-ddTHH:mm:ssTZD
4	X-PARTNERID	String (36)	M	Client ID provided by Finnet
5	X-SIGNATURE	String	C	BI SNAP symmetric signature. Use base64(HMAC_SHA512($ClientSecret, stringToSign)). See Signature for details.
6	X-EXTERNAL-ID	String (36)	M	Reference number that must be unique within the same day
7	X-CHANNEL-ID	String (5)	M	PJP’s channel id Device identification on which the API services is currently being accessed by the end user (customer)

Body Request

No	Name	Type	Mandatory	Description
1	fromDateTime	String	M	Starting time range. Default: NOW (DESC) or NOW - 3 months (ASC)
2	toDateTime	String	M	Ending time range. Default: NOW - 3 months (DESC) or NOW (ASC)
3	pageSize	Integer	O	Maximum number of transactions returned in one pagination. Default: 10
4	pageNumber	Integer	O	Current page number. Default: 0

Sample Request

curl --location ' https://snap.finnet.co.id/topup/v1.0/transaction-history-list-merchant' \ 
 --header 'Authorization: Basic ZGVtby51c2VyOg==' \ 
 --header 'Content-Type: application/json' \ 
 --header 'Accept: application/json' \ 
 --data ' 
{ 
  "fromDateTime": "2019-07-03T12:08:56+07:00", 
  "toDateTime": "2019-07-03T12:08:56+07:00", 
  "pageSize": 10, 
  "pageNumber": 2 
} 

Body Response

No	Name	Type	Mandatory	Description
1	responseCode	Enum	M	Response code
2	responseMessage	String	M	Response message
3	detailData	Object	O	Detail data

Sample Response

{
  "responseCode": "2001200",
  "responseMessage": "Request has been processed successfully",
  "detailData": [
    {
      "dateTime": "2022-12-02T08:18:13+00:00",
      "amount": {
        "value": "10000.00",
        "currency": "IDR"
      },
      "remark": "Pulsa Rp. 10000",
      "status": "SUCCESS",
      "type": "TEST",
      "additionalInfo": {
        "partnerReferenceNo": "78912343452347003",
        "referenceNo": "2212020005597959",
        "trxcode": "WS_TRX_TRANSFER",
        "id": "16109172",
        "sum_in": "0",
        "sum_out": "10000",
        "channel_id": "140",
        "source": "[phone]",
        "destination": "[phone]",
        "name": "Testing"
      }
    }
  ]
}

Response Code & Message

The table below lists response codes and messages for the Merchant History List API.

No	HTTP Code	Code	Message
1	200	2001200	Successful
2	400	4001100	Bad request
3	400	4001101	Invalid field format {field}
4	400	4001102	Invalid mandatory field {field}
5	401	4011101	Invalid token (B2B)
6	401	4011100	Unauthorised. [Reason]
7	403	4031101	Feature not allowed
8	403	4031104	Activity count limit exceeded
9	404	4041108	Invalid merchant
10	500	5001100	General error