Sygna Travel Rule Compliance Integration

We design and develop full-cycle blockchain solutions: from smart contract architecture to launching DeFi protocols, NFT marketplaces and crypto exchanges. Security audits, tokenomics, integration with existing infrastructure.
Showing 1 of 1 servicesAll 1306 services
Sygna Travel Rule Compliance Integration
Medium
~3-5 business days
FAQ
Blockchain Development Services
Blockchain Development Stages
Latest works
  • image_website-b2b-advance_0.png
    B2B ADVANCE company website development
    1214
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1161
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    852
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1041
  • image_logo-advance_0.png
    B2B Advance company logo design
    561
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    823

Sygna Integration (Travel Rule Compliance)

Sygna Bridge is a Travel Rule messaging platform from CoolBitX, popular in Asia (Taiwan, Japan, Korea) and among major exchanges (OKX, BitoPro, MaiCoin). If your audience or partners are Asian exchanges, Sygna provides better VASP coverage for that region.

API Integration

Sygna uses IVMS101 standard for formatting Travel Rule data — this is InterVASP Messaging Standard, adopted by most providers.

import { SygnaClient } from "@sygna/bridge-sdk";

const client = new SygnaClient({
  apiKey: process.env.SYGNA_API_KEY,
  baseUrl: "https://api.sygna.io/v2",
  privateKeyHex: process.env.SYGNA_PRIVATE_KEY, // for message signing
});

// Send Travel Rule data on withdrawal
async function sendTravelRuleData(withdrawal: Withdrawal): Promise<void> {
  const beneficiaryVASP = await client.getCurrencyId(withdrawal.destinationAddress);
  
  if (!beneficiaryVASP) return; // unhosted wallet
  
  const originatorData = {
    originator: {
      originatorPersons: [{
        naturalPerson: {
          name: [{
            nameIdentifier: [{
              primaryIdentifier: withdrawal.user.lastName,
              secondaryIdentifier: withdrawal.user.firstName,
              nameIdentifierType: "LEGL",
            }]
          }]
        },
        accountNumber: [withdrawal.fromAddress],
      }]
    },
    beneficiary: {
      beneficiaryPersons: [{ accountNumber: [withdrawal.destinationAddress] }]
    },
  };
  
  const callbackUrl = `${process.env.API_URL}/webhooks/sygna/callback`;
  
  await client.postPermissionRequest({
    data: client.encryptData(JSON.stringify(originatorData), beneficiaryVASP.encryptionKey),
    signature: client.signData(originatorData),
    expire_date: Math.floor(Date.now() / 1000) + 3600,
    callback_url: callbackUrl,
    transaction: {
      currency_id: withdrawal.asset,
      amount: withdrawal.amount.toString(),
      sender_address: withdrawal.fromAddress,
      recipient_address: withdrawal.destinationAddress,
    },
  });
}

Sygna vs Notabene

Parameter Sygna Notabene
Main market Asia Global
Encryption RSA-OAEP (keys in their system) SSI/DID
VASP coverage 400+ in Asia 500+ globally
Standard IVMS101 IVMS101
Pricing Negotiable Subscription

Choice between Sygna and Notabene depends on geography of VASP partners. For global coverage — integrate both through unified Travel Rule service. Sygna integration: 1-2 weeks.