Transaction Layer

TravelRule-AI

Coming soon

FATF Travel Rule compliance for crypto and cross-border wire transfers. Validates originator and beneficiary information, screens counterparties, and determines jurisdiction-specific disclosure obligations. Supports VASP-to-VASP and bank-to-VASP flows.

This plugin is in development. The API schema below is planned and subject to change. You can design your integration now using this reference.

Endpoint

POST/api/travelrule/check

Request parameters

Parameter	Type	Required	Description
`transaction_id`	string	Yes	Your unique transaction reference.
`jurisdiction`	string	Yes	One of: CA, AE, SA, GB.
`amount`	number	Yes	Transaction amount.
`currency`	string	Yes	ISO 4217 or crypto ticker.
`originator_name`	string	Yes	Full name of the originator.
`originator_account`	string	Yes	Originator account or wallet address.
`beneficiary_name`	string	Yes	Full name of the beneficiary.
`beneficiary_account`	string	Yes	Beneficiary account or wallet address.
`beneficiary_vasp`	string	No	Beneficiary VASP name or LEI, if known.

Response fields

Parameter	Type	Required	Description
`data.travel_rule_applies`	boolean	Yes	Whether Travel Rule disclosure obligations apply to this transaction.
`data.threshold_exceeded`	boolean	Yes	Whether the transaction exceeds the jurisdiction threshold.
`data.disclosure_required`	array	Yes	List of required disclosure fields for this jurisdiction.
`data.originator_screened`	boolean	Yes	Whether originator was screened against sanctions lists.
`data.beneficiary_screened`	boolean	Yes	Whether beneficiary was screened against sanctions lists.
`data.status`	string	Yes	approved, rejected, or review_required.
`data.ai_recommendation`	string	Yes	Compliance recommendation and required next steps.

cURL

# Coming soon
curl -X POST \
  https://shield.kodexa.systems/api/travelrule/check \
  -H "Content-Type: application/json" \
  -d '{...}'

Code examples available when plugin launches