Skip to main content

Best Practices

Data Validation​

  • Validate all required fields before submitting API requests.
  • Use ISO 3166-1 alpha-2 country codes (e.g., US, GB, DE).
  • Use DD-MM-YYYY format for all date fields (e.g., date_of_birth, and the start_date / end_date read filters).
  • Ensure address, date_of_birth, and place_of_birth are provided for NATURAL type persons.

Transaction Management​

  • Store the returned _id for all created transactions.
  • Monitor transaction status regularly using the Read endpoint.
  • Review any warnings returned in API responses.
  • Always provide detailed reasoning when declining transactions.
  • Use date ranges and status filters for efficient compliance reporting.

Pagination​

  • Use reasonable per_page values (25-100) for large datasets.
  • Apply status and direction filters to reduce response size.
  • Specify date ranges for better performance on historical queries.
  • Always check if the transactions array is empty in responses.

Security​

  • Never expose your API key in client-side code or public repositories.
  • All API requests must be sent over HTTPS.
  • Implement proper error handling for all API requests.
  • Maintain internal logs of all status updates for audit trails.

VASP Directory​

  • Screen counterparty VASPs before initiating Travel Rule transactions.
  • Check the in_network status for better message delivery rates.
  • Review risk_assessment scores and severity for due diligence.
  • Use standard blockchain names for improved delivery rates.

Wallet Verification​

  • Verify wallet ownership before processing high-value transactions.
  • Monitor verification token expiration (typically 24 hours).
  • Use appropriate verification flows based on your compliance requirements.
  • Track verification status transitions: pending -> verified / failed.