Platform · Travel Rule
Counterparty VASP discovery, originator and beneficiary data exchange, unhosted-wallet ownership proof, and a message record for every qualifying transfer, evaluated in the same call that screens the wallet.
Inside the handshake
Threshold test, counterparty resolution, payload exchange, and the sunrise-case fallback when the other side cannot receive.
Every transfer is tested against the applicable threshold and transfer type before any data leaves your tenant, the AED 3,500 threshold.
The destination address is attributed to an institution where attribution exists, and matched to a reachable counterparty, counterparties are reached over Notabene and TRP.
Required originator and beneficiary fields are assembled from the verified customer record rather than re-typed, so the message matches the KYC evidence on file.
Self-custody destinations trigger ownership proof, declaration, signed message, or in-session verification, self-hosted wallets are evidenced with signed-message or micro-transfer proof.
When a counterparty cannot receive a message or refuses to respond, the transfer is routed to a documented decision, proceed, hold, or reject, with the reason recorded.
Incoming originator data is validated against the beneficiary you hold, and mismatches open a case instead of silently crediting the account.
Sanctions screening of the counterparty parties and wallet exposure scoring run alongside the message, so one decision covers both obligations.
What was sent, what came back, when, and under which protocol version, retained on the customer's case file.
Submission to settlement
The originating side and the beneficiary side of the same exchange, in order.
Send the transfer against a customer ID that already carries verified identity data, before you broadcast or release funds.
VerifiX decides whether the transfer is in scope, attributes the destination, and resolves whether it is an institution or an unhosted wallet.
Originator and beneficiary data is exchanged with the counterparty institution, or ownership proof is collected for a self-custody destination.
Hold, proceed, or reject based on the response, the screening result, and your own rules, with the outcome attached to the case.
The message, the response, the proof, and the decision are written to the append-only audit trail with the operator who approved it.
Exposure
Indirect
Hops
3
Action
Alert raised
curl -X POST https://api.verifix.ae/v1/travel-rule/transfers \
-H "Authorization: Bearer $VERIFIX_KEY" \
-d '{
"direction": "outbound",
"asset": "USDT",
"amount": "12500.00",
"originator": { "customer_id": "cus_2LX..." },
"beneficiary": { "name": "A. Rahimi", "wallet": "0x9f2...c41" },
"jurisdiction": "AE"
}'
{
"id": "tr_7QF...",
"in_scope": true,
"counterparty": {
"type": "vasp",
"resolved": "exchange_partner_id",
"protocol": "supported_protocol",
"status": "message_sent"
},
"beneficiary_response": "pending",
"hold": true,
"evidence_id": "ev_31A..."
}Chain of custody
Illustrative sample data for an outbound transfer at or above the AED 3,500 threshold.
Named modules
Wallet and transaction monitoring modules live on the KYT page.
Scope the transfer, resolve the counterparty, exchange the payload, and record what was sent, received, or refused.
travel_ruleExchanges originator and beneficiary information with counterparty institutions on qualifying transfers, and records what was sent, received, or refused.
counterparty_vasp_discoveryAttributes a destination address to an institution and resolves whether a Travel Rule message can be delivered to it, or whether the destination is an unhosted wallet.
travel_rule_scopeDecides whether a transfer is in scope before any personal data leaves your tenant, using the threshold and transfer rules of the applicable regime.
unhosted_wallet_proofCollects proof that a self-custody destination belongs to your customer: signed message, declaration, or in-session verification, retained as an artefact.
See the full module catalog , every KYC, KYB, AML, KYT, and platform module with its inputs and outputs.
Inside the console
Counterparty discovery, data exchange, and wallet evidence stay connected to the transfer’s case file.
| Stage | What your team sees |
|---|---|
| Resolve | Identify the counterparty Virtual Asset Service Provider (VASP) before exchanging the payload. |
| Exchange | Send originator and beneficiary information through Notabene or TRP. |
| Check | Collect proof of control for an unhosted wallet where the journey requires it. |
| Retain | Record what was sent, the reply, timestamps, and the protocol version on the case file. |
Evidence retained
Questions
Continue
Most regulated journeys combine several of these. Each page covers one in the same detail.
A 30-minute walkthrough with a compliance engineer, or a request for sandbox access.