For exchanges and VASPs
Connect Travel Rule exchange to verification and risk.
We can help you link Korala verification, your provider’s response and the risk review for each transfer. Start with the provider and counterparties you need to reach.
The workflow
From verification to transfer decision.
Keep the provider’s acknowledgement, the customer’s verified identity and your transfer decision as separate records. Review them together when you investigate a transfer.
- 01
Verify the customer
Run the Korala identity and document checks your onboarding process requires.
- 02
Exchange transfer information
Your Travel Rule provider discovers the counterparty and exchanges the required information.
- 03
Evaluate the evidence
Link each provider response to a customer and transfer, then apply your risk policy.
- 04
Make the transfer decision
Your team reviews missing or conflicting responses and decides whether the transfer can proceed.
What exists today
Korala verifies customers. Your provider handles the exchange.
Korala provides verification workflows and a risk framework that accepts evidence from authenticated integrations. To exchange Travel Rule data, your team needs a provider or direct VASP connection, credentials, callback authentication and reconciliation.
Korala has no VASP messaging connector or TRUST connection today, and it does not exchange personal data with counterparties. A wallet-control proof shows control of an address under a given method; the institutional exchange still needs a provider.
Plan the first connection
Tell us which provider you use and which VASPs you need to reach.
We’ll map your verification and risk inputs to the transfer flow and identify the provider work your team needs.
Discuss an integration