Providers
Covalent carries Travel Rule transfers through five providers. Your company saves each provider's credentials for each environment, and enables the providers it uses.
Providers
Section titled “Providers”| Provider | Protocol | Discovery | Transport |
|---|---|---|---|
| Notabene | notabene |
Automatic wallet ownership discovery in the Notabene network | OAuth REST API and signed webhooks |
| CodeVASP | codevasp |
Wallet discovery, or a known beneficiary VASP entity ID | Signed REST requests with end-to-end encrypted IVMS101 |
| Veriscope | veriscope |
Attestation-based, asynchronous | Shyft Network blockchain |
| Global Travel Rule | gtr |
Address verification against GTR allowlisted VASPs | Mutual TLS REST API with encrypted IVMS101 |
| Sygna Bridge | sygna |
Signed address validation against registered Sygna VASPs | HTTPS, secp256k1 signatures and ECIES encryption |
Sending transfers through Veriscope is not available yet on this platform: Veriscope receives transfers from peers, and when routing reaches it for an outgoing transfer, its attempt fails and the next enabled provider is tried. See Veriscope.
Provider Behavior
Section titled “Provider Behavior”POST /api/v2/transfers does not name a provider. Covalent routes each transfer to an enabled provider able to carry it; preferredProtocol names the protocol to try first: the create is refused unless it has an enabled provider able to carry the transfer, and another enabled provider may still carry it when that attempt fails before the provider has taken the transfer, or when the beneficiary VASP was last reached through another provider. The provider that carried a transfer, and every provider attempt, are on the transfer's detail under cascade.
Notabene, Global Travel Rule and Sygna Bridge send your customer's verified Travel Rule identity as the originator of an outgoing transfer. On an incoming transfer, Notabene and Global Travel Rule send it as the beneficiary; CodeVASP sends back the beneficiary persons the originator sent, after matching their names against it; Sygna Bridge's acceptance carries no beneficiary data.
For Veriscope's KYC template states, webhook states, and IVMS state codes, see Veriscope.
Configuration
Section titled “Configuration”Configure providers with /api/v2/providers (the providers:read and providers:write scopes) or in the dashboard, under Travel Rule, Providers:
PUT /api/v2/providers/:namesaves credentials for the key's environment. Credential values are never returned.PATCH /api/v2/providers/:nameenables or disables a provider, for both environments, and takes a live key.POST /api/v2/providers/:name/testtests the connection with the environment's credentials.
See Providers and Integrations.
Callback Paths
Section titled “Callback Paths”Providers call your company's host on paths that name the environment and the provider's ID, such as /api/system/trp/notabene/live/<providerId>. A provider's paths are listed in its callbackPaths once it has been saved; register them with the provider. See Callback Paths.