Address Exists Verify Callback

Version: 3.0.0

Method

POST

Url

https://{YOUR_SERVICE_URL}/(address exists verify: 6)

This callback API endpoint verifies beneficiary address ownership. When an initiator sends a verification request via GTR, your VASP, as the request receiver, must confirm whether the provided address (and optional tag) belongs to your service.

Authentication

No authentication

Path Parameters

No path parameters

Query Parameters

No query parameters

Request Body (Optional)

Schema

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

Example

{
  "initiatorVasp": "string",
  "ticker": "string",
  "address": "string",
  "addressType": 0,
  "requestId": "string",
  "travelruleId": "string",
  "originatorVaspName": "string",
  "tag": "string",
  "originatorVasp": "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"
}

Note: If tag is null, treat it as empty or exclude it from your search criteria.

Response Example 1: Success

HTTP Status: 200, VerifyStatus: 100000

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

This response indicates that the address do exist in your service.

Response Example 2：Address Not Found

HTTP Status: 200, VerifyStatus: 200001

{"verifyStatus": 200001,"verifyMessage": "Address Not Found."}