Verifix

Inside the handshake

What happens before the transfer leaves

Threshold test, counterparty resolution, payload exchange, and the sunrise-case fallback when the other side cannot receive.

Scope determination

Every transfer is tested against the applicable threshold and transfer type before any data leaves your tenant, the AED 3,500 threshold.

Counterparty VASP discovery

The destination address is attributed to an institution where attribution exists, and matched to a reachable counterparty, counterparties are reached over Notabene and TRP.

Originator and beneficiary data

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.

Unhosted wallet handling

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.

Sunrise and refusal handling

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.

Inbound message review

Incoming originator data is validated against the beneficiary you hold, and mismatches open a case instead of silently crediting the account.

Screening in the same call

Sanctions screening of the counterparty parties and wallet exposure scoring run alongside the message, so one decision covers both obligations.

Message record

What was sent, what came back, when, and under which protocol version, retained on the customer's case file.

Submission to settlement

How a transfer clears the rule

The originating side and the beneficiary side of the same exchange, in order.

Submit the transfer

Send the transfer against a customer ID that already carries verified identity data, before you broadcast or release funds.

Determine scope and counterparty

VerifiX decides whether the transfer is in scope, attributes the destination, and resolves whether it is an institution or an unhosted wallet.

Exchange or prove

Originator and beneficiary data is exchanged with the counterparty institution, or ownership proof is collected for a self-custody destination.

Decide and release

Hold, proceed, or reject based on the response, the screening result, and your own rules, with the outcome attached to the case.

Retain the evidence

The message, the response, the proof, and the decision are written to the append-only audit trail with the operator who approved it.

Transaction trace · 0x9f…c204

Sample data

Customer wallet

Verified · low

Exchange deposit

Licensed VASP

Intermediary

2 hops · medium

Mixer-linked cluster

High risk

Exposure

Indirect

Hops

Action

Alert raised

POST /v1/travel-rule/transfers

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

One transfer, as the record shows it

Illustrative sample data for an outbound transfer at or above the AED 3,500 threshold.