TRON Address Compliance Checks

Last updated: 2026-10-05

An instant yes/no compliance verdict for a TRON address, before you send USDT to it or after you receive USDT from it. Each check looks the address up against a deny-list built from:

• Sanctions lists — OFAC SDN, EU, UK and other official designations.
• Commercial AML intelligence — scams, ransomware, stolen funds, fraud.
• Tether's USDT freeze list — addresses whose USDT the issuer has frozen.
• Smart-contract addresses and confirmed mass-spam senders.

This is a fast blocklist lookup, not a risk score. For an Elliptic risk score, exposure breakdown and the reasons behind it, use AML Address Checks.

Price

1.00 per check, in-kind (1.00 USDT or 1.00 USDC) from one of your balances, debited when the verdict is returned. If no verdict can be produced — the service is unavailable, you hit the rate limit, or the address is invalid — nothing is charged. The fee appears in your fee ledger as Compliance Check Fee.

Which balance pays: send feeCurrency and feeNetwork together to choose. Without them the fee comes from USDT on TRX, then your largest balance.

Network

TRON (TRX) only.

When to check

Before you send (payouts)

Screen the destination address before calling POST /api/withdrawals:

{ "address": "TLa2f6VPqDgRE67v1736s7bJ8Ray5wYjU7" }

Don't send if verdict.blocked is true:

After you receive (deposits)

When USDT arrives, the party to screen is whoever sent it, not your deposit address. Pass the deposit's id and the check runs on that deposit's on-chain sender — the same sender reported as fromAddress in your deposit.confirmed webhook:

{ "depositId": "cmg9…" }

• Run it once the deposit is confirmed and before you credit the customer or release goods. A blockchain transfer cannot be refused: the funds have already arrived. The check tells you whether to hold them for review instead of crediting.
• On blocked: true with aml_risk, freeze the customer's credit and follow your compliance procedure. Don't send the funds back yourself without that review: returning funds to a sanctioned address is itself a transfer to it.
• usdt_frozen is rare for senders, because a frozen address cannot send USDT. Seeing it means the address was frozen after the payment.
• smart_contract is normal for payments from some exchanges and payment processors. Treat it as information, not a block.
• You can also screen a customer's declared wallet before they pay, with address, if you whitelist customer wallets during onboarding.

Run a check

POST /api/compliance-checks
Authorization: <API key>
Content-Type: application/json

{
  "address": "TTVUvAWUZafeHqQP82sYnfk4jNFPEHCRpL",
  "referenceId": "payout-88412"
}

Only write-capable merchant API keys can run checks.

Response

{
  "success": true,
  "check": {
    "id": "cmgb1x0c90004",
    "referenceId": "payout-88412",
    "address": "TTVUvAWUZafeHqQP82sYnfk4jNFPEHCRpL",
    "network": "TRX",
    "depositId": null,
    "verdict": {
      "blocked": true,
      "category": "aml_risk",
      "severity": "BLOCK",
      "reasonCode": "SANCTIONS_SCREENING",
      "label": "DPRK Bitget Exploit - September 2026",
      "checkedAt": "2026-10-05T08:00:00+00:00"
    },
    "fee": { "amount": "1", "currency": "USDT", "network": "TRX", "status": "CHARGED" },
    "createdAt": "2026-10-05T08:00:00.120Z"
  }
}

A clean address returns "blocked": false, "category": "clean"; severity, reasonCode and label are null.

Get and list checks

GET /api/compliance-checks/{checkId}
GET /api/compliance-checks?blocked=true&page=1&limit=20

Re-reading a stored verdict is free and never re-checks. Run a new check when you need a current verdict — lists change daily.

List filters (all optional): page, limit (max 100), blocked, category, address, depositId, referenceId. The response also carries service.feePerCheck and service.supportedNetworks.

Errors

Nothing is charged for any error.