Cubewire LogoDeveloper
Support
Onboarding
Cubewire Developer Hub Logo
SOC 2 Compliant

Developer documentation and tools for Cubewire's digital wallet infrastructure. Built for developers, by developers.

developers@cubewire.com
TwitterGitHubDiscord

Developer Tools

  • API Documentation
  • API Reference

Resources

  • Documentation

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
© 2026 Cubewire. All rights reserved.
Developer Documentation Portal•Built with ♥ for developers
  1. Cubewire Wallet
  2. Manage Transactions
  3. Validate transaction for travel rule

Validate transaction for travel rule

Validate a transaction against Travel Rule requirements. Automatically authenticates with the configured Travel Rule provider and returns compliance results including transaction type classification, beneficiary address classification, and VASP information.

The Financial Action Task Force (FATF) Travel Rule requires Virtual Asset Service Providers (VASPs) to share originator and beneficiary information for crypto transactions above a regulatory threshold. This endpoint determines whether a given transaction triggers Travel Rule obligations.

Request Body

FieldTypeRequiredDescription
transactionAssetstringYesAsset symbol (e.g., ETH, BTC, USDC)
transactionAmountstringYesAmount in the asset's base unit (e.g., wei for ETH, satoshi for BTC)
transactionBlockchainInfoobjectYesOn-chain transaction details (origin and destination addresses)
transactionAssetDecimalsnumberNoAsset decimals for amount conversion (e.g., 18 for ETH)
originatorDidstringNoOriginator's decentralized identifier
beneficiaryDidstringNoBeneficiary's decentralized identifier
originatorVaspIdstringNoOriginator VASP identifier
beneficiaryVaspIdstringNoBeneficiary VASP identifier
beneficiaryVaspNamestringNoBeneficiary VASP name

transactionBlockchainInfo Object

FieldTypeDescription
originstringOriginator blockchain address (0x...)
destinationstringBeneficiary blockchain address (0x...)

Response Fields

FieldTypeDescription
isValidbooleanWhether the transaction passes Travel Rule requirements
transactionTypestringOne of BELOW_THRESHOLD, TRAVELRULE, NON_CUSTODIAL, UNKNOWN
beneficiaryAddressTypestringOne of HOSTED (VASP-controlled), UNHOSTED (self-custodied), UNKNOWN
addressSourcestringProvider that classified the address (CHAINALYSIS, ELLIPTIC, COINFIRM, UNKNOWN)
beneficiaryVaspIdstringIdentified beneficiary VASP (if resolvable)
beneficiaryVaspNamestringBeneficiary VASP display name
errorsstring[]Compliance errors (present when isValid=false)
warningsstring[]Non-blocking compliance warnings

Use Cases

  • Pre-screen transactions before submission to check Travel Rule obligations
  • Determine if VASP-to-VASP information sharing is required
  • Classify beneficiary addresses as hosted or unhosted wallets
  • Integrate compliance checks into transaction submission workflows

Required Permission

transactions:create

On this page

  • Request Body
  • transactionBlockchainInfo Object
  • Response Fields
  • Use Cases
  • Required Permission
  1. Cubewire Wallet
  2. Manage Transactions
  3. Validate transaction for travel rule

Validate transaction for travel rule

Validate a transaction against Travel Rule requirements. Automatically authenticates with the configured Travel Rule provider and returns compliance results including transaction type classification, beneficiary address classification, and VASP information.

The Financial Action Task Force (FATF) Travel Rule requires Virtual Asset Service Providers (VASPs) to share originator and beneficiary information for crypto transactions above a regulatory threshold. This endpoint determines whether a given transaction triggers Travel Rule obligations.

Request Body

FieldTypeRequiredDescription
transactionAssetstringYesAsset symbol (e.g., ETH, BTC, USDC)
transactionAmountstringYesAmount in the asset's base unit (e.g., wei for ETH, satoshi for BTC)
transactionBlockchainInfoobjectYesOn-chain transaction details (origin and destination addresses)
transactionAssetDecimalsnumberNoAsset decimals for amount conversion (e.g., 18 for ETH)
originatorDidstringNoOriginator's decentralized identifier
beneficiaryDidstringNoBeneficiary's decentralized identifier
originatorVaspIdstringNoOriginator VASP identifier
beneficiaryVaspIdstringNoBeneficiary VASP identifier
beneficiaryVaspNamestringNoBeneficiary VASP name

transactionBlockchainInfo Object

FieldTypeDescription
originstringOriginator blockchain address (0x...)
destinationstringBeneficiary blockchain address (0x...)

Response Fields

FieldTypeDescription
isValidbooleanWhether the transaction passes Travel Rule requirements
transactionTypestringOne of BELOW_THRESHOLD, TRAVELRULE, NON_CUSTODIAL, UNKNOWN
beneficiaryAddressTypestringOne of HOSTED (VASP-controlled), UNHOSTED (self-custodied), UNKNOWN
addressSourcestringProvider that classified the address (CHAINALYSIS, ELLIPTIC, COINFIRM, UNKNOWN)
beneficiaryVaspIdstringIdentified beneficiary VASP (if resolvable)
beneficiaryVaspNamestringBeneficiary VASP display name
errorsstring[]Compliance errors (present when isValid=false)
warningsstring[]Non-blocking compliance warnings

Use Cases

  • Pre-screen transactions before submission to check Travel Rule obligations
  • Determine if VASP-to-VASP information sharing is required
  • Classify beneficiary addresses as hosted or unhosted wallets
  • Integrate compliance checks into transaction submission workflows

Required Permission

transactions:create

On this page

  • Request Body
  • transactionBlockchainInfo Object
  • Response Fields
  • Use Cases
  • Required Permission