Address Screening Result

This page explains the meaning of the screeningResult object returned by selected GTR APIs.

Address Screening is an additional compliance signal generated from blockchain address analysis.

It is designed to help your Compliance or Risk team better understand whether a target address may be associated with a VASP entity or a risk category.

✍️ Address Screening is an advisory result only. Your final Travel Rule decision should still be based on the full verification flow and your own compliance policy.

Response structure

{
  "screeningResult": {
    "screeningStatus": "COMPLETED",
    "message": "screening result present",
    "vaspEntityName": "Axchange UK",
    "vaspEntityId": "axchange-uk",
    "vaspCode": "axchangeukadjk",
    "riskTags": [
      "Exchange & Trading Platforms",
      "Centralized Exchange",
      "Unknown"
    ],
    "riskScore": 4.0
  }
}

Field definitions

Field	Description
screeningStatus	Current status of the address screening job
message	Human-readable screening message
vaspEntityName	VASP entity name identified from the screened address, if available
vaspEntityId	Internal entity identifier identified from the screened address, if available
vaspCode	GTR VASP code identified from the screened address, if available
riskTags	Risk category tags identified from the screened address
riskScore	Risk score from 0 to 10. Type: double

Risk score

riskScore ranges from 0 to 10.

Score Range	Meaning
0	Lowest risk
10	Highest risk

In simple terms, the lower the score, the lower the risk.

Interpretation

• 0 to 2: generally indicates very low risk
• 3 to 5: generally indicates low to medium risk
• 6 to 8: generally indicates elevated risk
• 9 to 10: generally indicates high risk

✍️ The exact internal action you take for a given riskScore should still depend on your own compliance rules and jurisdiction requirements.

Precision handling

Since riskScore is returned as a double (floating-point number), direct floating-point comparison or arithmetic may lead to precision issues.

Java example:

// ❌ Avoid
if (riskScore == 4.0) { ... }
double result = riskScore + 1.0;

// ✅ Recommended
BigDecimal score = new BigDecimal(String.valueOf(riskScore));
if (score.compareTo(new BigDecimal("4.0")) == 0) { ... }
BigDecimal result = score.add(new BigDecimal("1.0"));

For other languages, please use equivalent precision-safe utilities (e.g., Decimal in Python, decimal.js in JavaScript).

Risk tags

riskTags may or may not be present.

If screening cannot identify any meaningful tag, the result should be treated as:

{
  "riskTags": ["Unknown"]
}

This means the screening engine could not confidently classify the address into a known category.

Screening status

COMPLETED

COMPLETED means the address screening has finished.

In this case, the returned riskScore, riskTags, and any identified VASP information should be treated as the final screening output for API usage.

TIMEOUT

GTR provides a response-time guarantee for address screening.

If the screening process takes more than 1 second, the API will immediately return:

{
  "screeningStatus": "TIMEOUT"
}

In this case:

• The API response is returned immediately to avoid blocking your integration flow.
• GTR may continue processing the screening result asynchronously.
• You can later view the delayed result from API History in GTR UI.
• The delayed result is available for UI inspection only.

ERROR

ERROR means the screening process encountered an internal issue during execution.

In this case:

• GTR will retry the screening process internally.
• You can later check the eventual result in API History in GTR UI.
• The retried result is available for UI inspection only.

NONE

NONE means screening was not started or no screening result is available in the current API context.

This status may appear in flows where address screening is not executed, or when the main verification flow did not reach the stage required to trigger screening.

Operational notes

• TIMEOUT does not necessarily mean screening permanently failed.
• ERROR does not necessarily mean screening permanently failed.
• For both TIMEOUT and ERROR, GTR may still produce a delayed result in the background.
• Delayed screening results for these cases should be checked through API History in GTR UI.
• For API consumers, only the immediate API response should be used programmatically.

Recommended handling

screeningStatus	Recommended interpretation
COMPLETED	Use the returned screening result directly
TIMEOUT	Continue your flow based on immediate API response, and review delayed result in UI later if needed
ERROR	Continue your flow based on immediate API response, and review retried result in UI later if needed
NONE	Treat as no screening result available

Important reminder

Address Screening is intended to assist compliance decision-making, but it is not a standalone proof of wallet ownership, Travel Rule success, or counterparty identity.

You should always combine it with:

• Address Verification or TX ID Verification
• PII Verification
• Your own compliance policy
• Your own risk engine or manual review process