DLT Transaction Validator API
Validate Distributed Ledger Technology (DLT) transaction structures against common standards and UAE regulatory requirements. Checks address and hash formats, value constraints, prohibited assets, VARA compliance thresholds, AML signals, and DLT network identity — purpose-built for UAE fintechs and digital asset platforms.
/api/v1/dlt/validateidentity:dltTry it out
/api/v1/dlt/validateParameters
Code
curl -X POST "https://khaleejiapi.dev/api/v1/dlt/validate?transaction.txHash=0xabc123...64hexchars&transaction.from=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045&transaction.to=0xAbCdEf0123456789AbCdEf0123456789AbCdEf01&transaction.value=100000&transaction.currency=AED" \ -H "Authorization: Bearer your_api_key"Request Body
Send a JSON body with a transaction object. Fields marked required must be present; optional fields are validated when provided.
| Field | Type | Required | Description |
|---|---|---|---|
| transaction.txHash | string | ✓ | Transaction hash (0x-prefixed 64-hex EVM, plain 64-hex SHA-256, or base58) |
| transaction.from | string | ✓ | Sender address (EVM 0x40-hex, bech32, or base58check) |
| transaction.to | string | ✓ | Recipient address (same formats as from) |
| transaction.value | string | ✓ | Amount in smallest denomination (e.g. fils for AED, wei for ETH) |
| transaction.currency | string | ✓ | Currency/token code (AED, ETH, USDT, BTC, etc.) |
| transaction.chainId | number | — | DLT network chain ID (e.g. 1 = Ethereum Mainnet, 137 = Polygon) |
| transaction.timestamp | string | — | ISO 8601 transaction timestamp |
| transaction.nonce | number | — | Transaction nonce (non-negative integer) |
| transaction.type | string | — | Transaction type: transfer, contract_call, swap, bridge, payment, etc. |
| transaction.data | string | — | Transaction payload data (0x-prefixed hex or base64) |
| transaction.signature | string | — | Cryptographic signature (0x + 130-hex ECDSA or base64) |
Verdict Values
No errors or warnings — transaction structure is fully compliant
Structure is valid but advisory checks (e.g. VARA threshold) were triggered
One or more error-severity issues found; transaction should be rejected
Issue Severities
error
Structural or format violation — makes the transaction invalid. Examples: malformed hash, prohibited currency (privacy coins), negative value, zero address.
warning
Compliance advisory or AML signal — transaction is structurally valid but requires attention. Examples: VARA EDD threshold exceeded, burn address, self-transfer, future timestamp.
info
Informational note — no action required. Examples: unlisted chain ID, round large value (structuring indicator).
Validation Checks
Transaction Hash
Validates EVM 0x+64-hex, plain 64-hex (SHA-256), and base58-encoded hashes. Rejects zero hashes.
Address Format
Validates EVM 20-byte addresses (with EIP-55 checksum advisory), bech32 (Bitcoin SegWit, UAE custom), and base58check. Flags zero address and burn address.
Value & Currency
Rejects negative or non-numeric values. Triggers VARA EDD warning above AED 55,000. Rejects VARA-prohibited privacy coins (XMR, DASH, ZEC, GRIN, BEAM). Warns on unregistered tokens.
Network Identity (Chain ID)
Verifies chain ID against UAE VARA-acknowledged networks: Ethereum Mainnet (1), Polygon (137), BNB Chain (56), Avalanche (43114). Flags unknown chain IDs as informational.
AML / Fraud Signals
Detects self-transfers (wash trading per VARA AML §8.1), high-risk address patterns, and suspiciously round large values (structuring per VARA AML §8.2).
Optional Fields
When provided: validates ISO 8601 timestamp (future/stale detection), ECDSA or base64 signature format, 0x-hex or base64 data encoding, non-negative integer nonce, and recognized transaction type.
UAE Regulatory References
VARA — Virtual Assets and Related Activities Regulations 2023
Governs virtual asset service providers in Dubai. Defines permitted asset classes (§3.5), prohibited privacy coins, and licensing requirements.
VARA AML/CFT Rulebook 2024
§7.3 — Enhanced Due Diligence for transactions ≥ AED 55,000. §8.1 — Wash trading prohibition. §8.2 — Transaction structuring detection.
CBUAE Digital Asset Guidelines 2022
Central Bank of the UAE guidelines for digital payments and virtual asset integration in regulated financial institutions.
Rate Limits
| Plan | Requests/Month | Rate Limit |
|---|---|---|
| Free | 500 | 5 req/min |
| Starter | 5,000 | 30 req/min |
| Professional | 50,000 | 120 req/min |
| Business | 250,000 | 500 req/min |
Debugging & Support
Include X-Request-ID when contacting support
Every response from KhaleejiAPI includes an X-Request-ID header — a unique identifier that lets our support team pull the exact log entry for your request within seconds. Always share it when reporting an unexpected error or unexpected result.
How to capture it
JavaScript / fetch
const res = await fetch("https://khaleejiapi.dev/api/v1/...", {
headers: { Authorization: "******" },
});
const requestId = res.headers.get("x-request-id");
console.log("Request ID:", requestId);
// → e.g. "req_01j9xkz4vp8..."cURL
curl -si "https://khaleejiapi.dev/api/v1/..." \ -H "Authorization: ******" | grep -i x-request-id # → x-request-id: req_01j9xkz4vp8...
Browser DevTools
Open DevTools (F12) → Network tab → click the failing request → scroll to the Response Headers section → copy the value next to x-request-id.
For a full list of error codes and guidance on common issues, see the Troubleshooting guide.