Update TXID

Version: 3.0.0

Method

POST

Url

https://platform.globaltravelrule.com/api/verify/v2/notify_tx_id

Authentication

No authentication

Path Parameters

No path parameters

Query Parameters

No query parameters

Request Body (Optional)

Schema

	Property	Type	Required	Description
	requestId	String	Yes	requestId is the unique id for all transaction, the same travelrule-request invoke process flow should be using same requestId, the recommend format is: "[YOUR_VASP_NAME]-[UUIDv4]"
	txId	String	Yes	*if the travel rule is after on chain, then the txId is required. the tx id format type can check the table.

Example

{
  "requestId": "testexchange-189e9948-64c7-4a6c-bb4f-859c173321c5",
  "txId": "d1029841dacb031098288b257b628a967eb963bbaccf954506ad0694219497a4"
}

Responses

Status 200

OK

JSON Content

Schema

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

Example

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

Status HTTP Status: 200, VerifyStatus: 100000

Success

JSON Content

Schema

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

Example

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

In a Travel Rule request, you should call this API to notify the txId to your counterparty after you send crypto asset to the blockchain.

If you decide to cancel this outbound transaction (asset withdrawal) after PII verification passed, please use /end to explicitly terminate the Travel Rule process.

Request Example 1: Update Transaction ID to GTR

{
  "requestId": "[requestId]",
  "txId": "[txId]"
}

Response Example: Success

HTTP Status: 200, VerifyStatus: 100000

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