Who Sygna is
Sygna launched in 2019, when CoolBitX introduced Sygna Bridge so that virtual asset service providers could meet FATF Recommendation 16, the Travel Rule. Next to Bridge, Sygna Hub adds blockchain analytics and sanctions screening through one API.
Exchanges and other crypto businesses use Sygna Bridge to exchange sender and recipient data in the IVMS 101 format, encrypted so that only the counterparty can read it. In April 2026 Sygna was acquired by VerifyVASP, a Singapore-based Travel Rule network, and existing Sygna members are being brought onto VerifyVASP's Verified Network. It is one of the Travel Rule providers our compliance reporting module connects to.
What it does in your platform
Compliance reporting
Exchanges Travel Rule data for your customers' crypto transfers through Sygna Bridge, where the receiving provider confirms a transfer with a signed permission before it is broadcast. Incoming requests are checked against your rules before funds are credited, and each permission is kept with its transfer.
How the connection works
One connector in the compliance reporting module talks to the Sygna Bridge API. Requests are relayed by Sygna's central server, and your platform's Sygna keys stay in its secrets.
A customer withdraws crypto
To an address at another exchange. The module finds the receiving provider in Sygna's directory, where each member is listed with its code and public key.
A permission is requested
The module posts a permission request with the sender and recipient data, encrypted for the receiving provider, and Sygna Bridge relays it.
The other side validates
The receiving provider checks the recipient against its own customers and answers with a permission, accepted or rejected, signed with its key.
The answer comes back
Sygna relays the permission to the module's callback, and the module records it next to the withdrawal.
The transaction ID closes it
Once the transfer is on-chain, the module submits its transaction ID to Sygna Bridge, linking the permission to the blockchain record.
Deposits work the other way
Requests for your customers' incoming transfers reach the module through Sygna and are checked against your rules before the funds are credited.
Next to other providers
Sygna Bridge connects you to the providers on its network, and the move onto VerifyVASP's Verified Network widens the set of counterparties Sygna members can reach.
The Travel Rule checks, the review in the backoffice and the records belong to the module, not to Sygna, so your apps stay the same whatever the acquisition changes.
When Sygna fits best
A strong fit when
- Your counterparties already exchange Travel Rule data on Sygna Bridge or on VerifyVASP's network.
- You want a signed permission from the receiving provider before a transfer goes on-chain.
- You want standardised, encrypted messages: IVMS 101 data that only the receiving provider can read.
Also worth a look
- A provider that bridges several Travel Rule protocols, such as Notabene, when your counterparties are spread across networks.
- The open Travel Rule Protocol, for counterparties that support it directly.
How we get you live
The contract
We help you get your account and contract in place with Sygna, now part of VerifyVASP, set up for your markets and your licence.
Your profile and rules
We register your details in the directory with you, and set the rules your side applies when another provider sends you a request.
The keys
Your API key and your signing keys stay in your platform's secrets, so every request you send is signed and every permission you receive can be verified.
A full test run
Transfers run against Sygna's Robot VASP, a test counterparty that answers automatically, before your first real customer transfer.
