TXID Existence Verify Callback

Version: 3.0.0

Method

POST

Url

https://{YOUR_SERVICE_URL}/(TXID exists verify: 9)

This callback API endpoint is for verify the existence of txId. Initiator will send you request to verify the txId.

Authentication

No authentication

Path Parameters

No path parameters

Query Parameters

No query parameters

Request Body (Optional)

Schema

	Property	Type	Required	Description
	address	String	No
	addressType	Integer	No
	initiatorVasp	String	No
	network	String	No
	requestId	String	Yes
	tag	String	No
	ticker	String	Yes
	travelruleId	String	No
	txId	String	Yes

Example

{
  "initiatorVasp": "string",
  "ticker": "string",
  "address": "string",
  "addressType": 0,
  "requestId": "string",
  "travelruleId": "string",
  "txId": "string",
  "tag": "string",
  "network": "string"
}

Responses

Status 200

OK

JSON Content

Schema

	Property	Type	Description
	verifyMessage	String
	verifyStatus	Integer

Example

{
  "verifyStatus": 0,
  "verifyMessage": "string"
}

Status HTTP Status: 200, VerifyStatus: 100000

JSON Content

Schema

	Property	Type	Description
	data	Object
Property Type Description No properties
	verifyMessage	String
	verifyStatus	Integer

Example

{
  "data": {},
  "verifyStatus": 0,
  "verifyMessage": "string"
}

You have to use tx_id + beneficiary_address + tag + network to identify one tx_id exists in your system or not.

The reason using beneficiary_address in txId check is because originator mostly using hot-wallet to make transfer, so that you as originator should use include beneficiary_address in the txId check.

Response Example 1: Success

HTTP Status: 200, VerifyStatus: 100000

This response indicates that this tx_id do exist in your VASP.

{"verifyStatus": 100000,"verifyMessage": "Verify Success"}

Response Example 2: TX ID Not Found

HTTP Status: 200, VerifyStatus: 200007

{"verifyStatus": 200007,"verifyMessage": "TX ID Not Found"}