Avus finds the counterparty, sends originator and beneficiary data over whichever network they use, checks what comes back, and releases funds only when the transfer is complete.
of transfers checked for complete data before release
messaging networks reached from one integration
threshold where self-hosted ownership is proven
transfers released with a mismatch left open
The Transfer of Funds Regulation applies from the first euro. Avus makes that the default and not a manual step.
Counterparties use different messaging networks. Avus reaches them through the one they are on, and discovers unknown VASPs from the address.
When funds go to or come from a self-hosted wallet, the customer proves ownership in a few taps, and the proof stays with the transfer.
Above €1,000 to a self-hosted wallet, ownership is proven before funds move, and the proof is kept with the transfer.
Incoming transfers are matched against what arrived. Missing or mismatched data is asked for, held or returned, according to your policy.
Not every jurisdiction applies the rule yet. Avus handles each counterparty by where it stands, and records the reasoning each time.
Each transfer carries its own record of what was sent, what came back and who allowed it to move.
Completeness and name matching run the same way on every transfer, in and out.
Case AI drafts the request to the counterparty and follows up until the data arrives.
Holds and returns outside policy go to a person, who decides on the record.
Travel Rule networks and analytics Avus works with
Travel Rule checks sit next to screening, use the same provider connections and leave the same audit record.
We will run a transfer to a counterparty on another network and a self-hosted wallet, end to end.