Jump to Content
Sygna Developer HubGuidesAPI ReferenceChangelogAPI StatusSygna HubHome
HomeGuidesAPI ReferenceChangelogDiscussions
GuidesAPI ReferenceChangelogAPI StatusSygna HubHomeLog InSygna Developer Hub
Log In

Glossary

  • VASP
  • VAAI
  • VASP Code
  • Currency ID
  • IVMS101

VASP Registration

  • Beneficiary VASP API Endpoint URL
  • VASP Key Pair
  • Bridge Public Key

Integration Workflows

  • 1. Sygna to Sygna VASP
  • Originator VASP
    • Send Permission Request
    • Receive Permission
  • Beneficiary VASP
    • New User Onboarding
    • Reply Permission
  • 2. Protocols Interoperability
    • Sygna VASP to Other-TR VASP
    • Other-TR VASP to Sygna VASP
  • 3. Non-interoperable VASP
    • Sygna VASP to non-interoperable VASP
    • Non-interoperable VASP to Sygna VASP
  • 4. Private Wallet Transaction
    • Private Wallet to Sygna VASP
    • Sygna VASP to Private Wallet

Testing

  • Robot VASP
  • Test Example Code

Other

  • FAQ
  • Support Library

Sygna Hub

  • Withdrawal Workflow
  • Deposit Workflow
  • Technical Document

Originator VASP

Sygna to Sygna VASP

Suggest Edits

When a transaction executes, an originator VASP sends a Send Permission Request to a beneficiary VASP for approval. Once the execution is approved, the beneficiary VASP will respond with a Receive Permission that allows the originator VASP to complete the transaction.

Updated 8 months ago


What’s Next
  • Send Permission Request
  • Receive Permission
Did this page help you?