VerifyVASP
  • Welcome
  • Change Log
  • Getting Started
    • Getting Started with VerifyVASP
    • Product Overview
    • Alliance Registration & API Key Creation
    • VASP API Functionality
    • Database
    • Enclave Installation & Execution
    • Security Guide
    • Robot VASP Utilization
    • Enclave Server API Utilization
    • Enclave Server Health Monitoring & Troubleshooting
  • Reference
    • Enclave API Reference
      • v1
        • VASP ID
        • VASP List
        • Screening API
          • Risk Assessment with Chainalysis Sanction API
          • Risk Assessment with Chainalysis KYT API
          • Risk Assessment with Refinitiv WCO API
        • User Account Verification
        • User Verification
        • Verification Result List
        • Verification Result by UUID
        • Transaction Result Report
        • Error Report
        • Transaction Status Query
    • VASP API Reference
      • User Account Verification
      • User Verification
      • Transaction Status Query
      • Callback API
      • Decrypting Database Encryption Key
    • IVMS101 Guide
      • About IVMS101 Standard
      • IVMS101 Message Format Guide
      • IVMS101 Personal Data Fields
    • Supplement
      • Network Field
      • Wallet address and transaction ID standards
    • Glossary
Powered by GitBook
On this page
  • Architecture
  • Central Server
  • Enclave Server
  1. Getting Started

Product Overview

PreviousGetting Started with VerifyVASPNextAlliance Registration & API Key Creation

Last updated 1 year ago

Architecture

VerifyVASP's Decentralized Architecture

Central Server

VerifyVASP operates a central Server which serves as a message mediator server, operated by VerifyVASP. Please configure either the Production or Staging server endpoint's information below for the enclave environment variable VEGA_API_ENDPOINT.

  • Production: https://api.vega-protocol.com

  • Staging: https://api.vega-protocol.xyz

Enclave Environment Variable:

Enter the Central server URL above in VEGA_API_ENDPOINT variable.

Enclave Server

The enclave server, installed on member VASP's infrastructure communicates with a central server.

  • The enclave server is developed by VerifyVASP and distributed as a docker image.

  • The docker image for the enclave server is shared on the Private docker hub registry.

    • Send your Docker Hub ID to corporate@verifyvasp.com to get the download access.

  • An integrated database, along with several tables needs to be created for the enclave server.

  • VASP's own application servers communicates with the installed enclave server.