Incoming transactions workflow

When counterpart VASPs send Travel Rule messages through CryptoSwift, your analysts receive the data in near real time. This page explains how notifications arrive, how Personally Identifiable Information (PII) becomes visible, and which operational steps keep investigations on track when information is incomplete.

1. Travel Rule message ingested – As soon as an originator VASP submits data that matches one of your confirmed wallets, we create an INCOMING transaction.
2. Delivery channel – You can consume updates through the CryptoSwift Client Dashboard, via webhooks, or by polling the Transactions API. Use webhook signatures to verify authenticity.
3. PII visibility – Sensitive fields unlock only after the destination wallet is confirmed in your tenant. Review the disclosure logic in PII data handling to align with your privacy policies.

Keep your CryptoSwift wallet list aligned with the addresses you operate. Confirm ownership whenever a new custodial wallet appears so inbound Travel Rule messages map cleanly to your customer accounts and expose PII without delays.

Configure a central webhook endpoint (or monitoring queue) that forwards Travel Rule updates to the teams responsible for transaction monitoring. Make sure payloads reach both compliance analysts and any downstream case-management systems so follow-up actions are logged.

Define risk-based criteria—amount thresholds, risk scores, customer tiering—that determine whether funds move immediately after blockchain settlement or remain on hold pending additional checks. Document the playbook so analysts know when to pause payouts, request more data, or escalate to manual review.

When the originator VASP fails to provide Travel Rule data, you have two options:

• Submit a claim – Use the Claim Transaction endpoint (or the dashboard) to alert CryptoSwift about the blockchain transfer. We search for existing data, contact the originator VASP when necessary, and forward any recovered payloads back to you.
• Backfill internally – Collect details from your customer or external sources and store them with the incoming transaction record so your audit trail stays complete.

Track whether analysts confirm, decline, or keep transactions pending. Update statuses in CryptoSwift so the originator VASP receives clear feedback and your own ledgers stay reconciled.

• Keep webhook delivery logs so you can prove when data arrived and who handled it.
• Reconcile blockchain transactions against Travel Rule payloads regularly to detect any missing messages.
• Share this workflow with AML and customer-support teams so everyone understands what happens when additional information is requested from customers.

• PII data handling
• Improving data quality
• Webhooks
• Travel Rule recipes