Elliptic
The Elliptic adapter is implemented with a real HTTP path.
Implementation
Section titled “Implementation”| Field | Value |
|---|---|
| Integration name | elliptic |
| Display name | Elliptic |
| Type | blockchain_analytics |
| Required credentials | apiKey, apiSecret |
| Base URL | https://aml-api.elliptic.co |
| Endpoint path | /v2/wallet/synchronous |
| Timeout | 10 seconds |
| Retries | 3 attempts |
Screening
Section titled “Screening”The adapter supports:
- Address screening
- Customer reference forwarding when provided
- HMAC-signed requests
- Network mapping before requests: a network Elliptic does not map fails the check with
UNSUPPORTED_NETWORK
Transaction hashes are not screened: a transaction check fails with UNSUPPORTED_OPERATION, since Elliptic's wallet screening takes an address.
Credential Behavior
Section titled “Credential Behavior”When credentials are saved for the transfer's environment, the adapter signs and sends requests to Elliptic.
When they are missing, the check fails before any request is sent. There is no sandbox fallback: save test credentials to screen test transfers.
Connection Test
Section titled “Connection Test”The connection test requires both API key and API secret. If either is missing, the test fails with a missing-credential error.
Response Mapping
Section titled “Response Mapping”A complete response for the screened address, with its risk score from 0 to 10, is a successful check; the vendor's raw response is stored with it. Any other response fails the check.