COVALENT

Compliance infrastructure for crypto VASPs

[COVALENT @Covalent_One]

4/4 Each one is linked to the registered wallet and its customer, with the originator's data encrypted at rest and both sides' status visible at every step. Your team starts from a transfer that already knows who it is for.
👉 https://t.co/Ppyz8DRXpJ

[COVALENT @Covalent_One]

If you run a VASP, Travel Rule data never arrives with your customer's name on it. It comes addressed to a wallet, and before the funds can be released, someone has to work out which customer owns that wallet. 👁️🧵

[COVALENT @Covalent_One]

3/ Covalent makes that match the moment the data lands. Incoming attestations are checked against your wallet registry and claimed automatically, and Covalent creates the incoming transfer itself, with no API call from your side.

[COVALENT @Covalent_One]

4/4 Covalent sits across Travel Rule adapters, screening providers, and STR workflows so the operational record remains intact as supervision tightens.

[COVALENT @Covalent_One]

FATF is shifting from writing rules to testing whether they’re actually working.

After the late-October plenary, it opened a targeted review of jurisdictions with meaningful VASP activity. First findings are due mid-2027. 🧵

[COVALENT @Covalent_One]

3/ For operators, this changes the practical requirement. It’s no longer enough to have a single protocol connected. Travel Rule messaging, screening results, jurisdiction logic, and case handling need to stay consistent across the full transfer lifecycle.

[COVALENT @Covalent_One]

4/4 If the exchange does not complete, the transfer is held or failed, can be retried, and gets a case when an operator is needed -> https://t.co/Ppyz8DSvfh

[COVALENT @Covalent_One]

Before any Travel Rule data can move, a VASP has to know which VASP holds the destination address. Until then, the customer waits. 👁️🧵

[COVALENT @Covalent_One]

3/ Covalent's VASP search covers the counterparties in your own transfer history and resolved discovery records. Self-hosted wallets can require ownership proof, be blocked or go to analyst review.

[COVALENT @Covalent_One]

3/3 Case management, reporting and the audit trail sit on that same record. You keep your contracts. Your team gets one place to work. 👉 https://t.co/Ppyz8DSvfh

[COVALENT @Covalent_One]

Most VASPs already pay for a Travel Rule solution, a screening provider and a KYC tool. Each one returns its result in its own dashboard. When a transfer is held, the compliance team rebuilds the answer from three places.
👁️🧵

[COVALENT @Covalent_One]

2/ Covalent works with the providers you already have. They connect through provider adapters, and their results land on one record for each transfer, next to the jurisdiction rule that applied and the action taken.

[COVALENT @Covalent_One]

3/3 Case management, reporting and the audit trail sit on that same record. You keep your contracts. Your team gets one place to work. https://t.co/Ppyz8DRXpJ

[COVALENT @Covalent_One]

5/ Each draft is tracked against its filing deadline, with signed webhook events when it is generated and filed.
See it on your own cases -> https://t.co/dzHMFR2dZb

[COVALENT @Covalent_One]

When your analyst confirms suspicion on a transfer, Covalent drafts the STR or SAR from the case, ready for your team to review and file. 👁️🧵

[COVALENT @Covalent_One]

4/ Wallet addresses and transaction hashes are exact-match data. A report drafted from the record carries them exactly as captured.