Provider scope

The connector reads account balances with normalized asset codes. It does not claim universal coverage of every Kraken product, wallet or subaccount.

Credential boundary

Your server sends API key and private key when connecting the user's account. ChainsFlow encrypts the credential, while your onboarding must require read-only permissions and keep trading and withdrawals disabled.

Normalized application contract

After connection, your application uses ChainsFlow account IDs and normalized portfolio responses. Provider DTOs, signing rules and asset quirks stay inside the integration adapter.

Provider-specific behavior

The Kraken adapter handles asset prefixes, staking suffixes and unknown-code observability. Synchronization errors are mapped to stable safe problem codes without exposing credentials or raw provider payloads.