> For the complete documentation index, see [llms.txt](https://hinkal-team.gitbook.io/hinkal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hinkal-team.gitbook.io/hinkal/hinkal-waas/faq.md).

# FAQ

<details>

<summary>What is Hinkal WaaS?</summary>

Hinkal Wallet-as-a-Service (WaaS) is a managed wallet infrastructure that allows organizations to create wallets, manage users, define permissions, and execute private blockchain transactions through a REST API.

</details>

<details>

<summary>Who should use Hinkal WaaS?</summary>

Organizations building payroll systems, exchanges, treasury platforms, payment applications, embedded finance products, and enterprise blockchain solutions.

</details>

<details>

<summary>How is WaaS different from the Hinkal API?</summary>

With the API, users keep and control their own wallets. With WaaS, wallets are generated and managed inside Hinkal's secure enclave.

</details>

<details>

<summary>How is WaaS different from the SDK?</summary>

The SDK is designed for self-custody integrations. WaaS is designed for managed wallet environments.

</details>

<details>

<summary>Which chains does WaaS support?</summary>

Ethereum, Solana, Tron, and supported EVM-compatible chains.

</details>

<details>

<summary>Does WaaS support multiple chains?</summary>

Yes.

</details>

<details>

<summary>What wallet types can WaaS create?</summary>

EVM, Solana, and Tron wallets.

</details>

<details>

<summary>Does every wallet include all supported chains?</summary>

Yes.

</details>

<details>

<summary>What is an Organization?</summary>

The top-level entity used to manage users, wallets, and permissions.

</details>

<details>

<summary>Why do I need an Organization?</summary>

Organizations provide access control and management capabilities.

</details>

<details>

<summary>Can I create multiple Organizations?</summary>

Yes.

</details>

<details>

<summary>What is a User?</summary>

An identity within an Organization.

</details>

<details>

<summary>Can an Organization have multiple Users?</summary>

Yes.

</details>

<details>

<summary>Can Users have different permissions?</summary>

Yes.

</details>

<details>

<summary>What is a Policy?</summary>

A permission rule that controls what actions a user can perform.

</details>

<details>

<summary>Why are Policies required?</summary>

To prevent unauthorized operations.

</details>

<details>

<summary>Can Policies be updated?</summary>

Yes.

</details>

<details>

<summary>Can Policies be removed?</summary>

Yes.

</details>

<details>

<summary>What actions can Policies control?</summary>

Wallet creation, transaction signing, administration, and other supported actions.

</details>

<details>

<summary>What is the minimum setup flow?</summary>

Create Organization, Create User, Grant Policies, Create Wallet.

</details>

<details>

<summary>Can Organization creation be automated?</summary>

Yes.

</details>

<details>

<summary>Can User creation be automated?</summary>

Yes.

</details>

<details>

<summary>Can Wallet creation be automated?</summary>

Yes.

</details>

<details>

<summary>Does WaaS require manual user interaction?</summary>

Not necessarily.

</details>

<details>

<summary>Can wallets be created programmatically?</summary>

Yes.

</details>

<details>

<summary>How are users identified?</summary>

By Ed25519 public keys.

</details>

<details>

<summary>Does WaaS use passwords?</summary>

No.

</details>

<details>

<summary>Does WaaS use email authentication?</summary>

No.

</details>

<details>

<summary>Does WaaS use API keys?</summary>

No.

</details>

<details>

<summary>What authentication method does WaaS use?</summary>

X-Stamp authentication.

</details>

<details>

<summary>What is X-Stamp?</summary>

An Ed25519-based request signing mechanism.

</details>

<details>

<summary>Why does WaaS use X-Stamp?</summary>

To provide cryptographic authentication without passwords.

</details>

<details>

<summary>What is required for every request?</summary>

A valid X-Stamp signature and unique nonce.

</details>

<details>

<summary>What is a nonce?</summary>

A unique value included in every signed request.

</details>

<details>

<summary>Why is a nonce required?</summary>

To prevent replay attacks.

</details>

<details>

<summary>What happens if a nonce is reused?</summary>

The request is rejected.

</details>

<details>

<summary>Can I generate my own Ed25519 keypair?</summary>

Yes.

</details>

<details>

<summary>Should keypairs be generated locally?</summary>

Yes.

</details>

<details>

<summary>Does Hinkal generate authentication keys?</summary>

No.

</details>

<details>

<summary>Does Hinkal store authentication private keys?</summary>

No.

</details>

<details>

<summary>How should I store my private key?</summary>

Securely using your infrastructure or key management system.

</details>

<details>

<summary>Can authentication keys be rotated?</summary>

Yes.

</details>

<details>

<summary>Can users have different keypairs?</summary>

Yes.

</details>

<details>

<summary>What happens if I lose my private key?</summary>

You must generate and register a new keypair.

</details>

<details>

<summary>What is a root user?</summary>

The first administrative user created within an Organization.

</details>

<details>

<summary>How do I create my first Organization?</summary>

Generate a keypair and call the organization creation endpoint.

</details>

<details>

<summary>Can the root user manage all users?</summary>

Yes.

</details>

<details>

<summary>Can the root user create policies?</summary>

Yes.

</details>

<details>

<summary>Can the root user create wallets?</summary>

Yes.

</details>

<details>

<summary>Can the root user sign transactions?</summary>

Yes, if policies permit.

</details>

<details>

<summary>What permissions are required to create wallets?</summary>

CREATE\_WALLET.

</details>

<details>

<summary>What permissions are required to sign transactions?</summary>

SIGN\_TRANSACTION.

</details>

<details>

<summary>Why am I getting a policy error?</summary>

The user lacks permission for the requested action.

</details>

<details>

<summary>Can policies grant administrative access?</summary>

Yes.

</details>

<details>

<summary>Can policies be assigned to multiple users?</summary>

Yes.

</details>

<details>

<summary>Can policies be revoked?</summary>

Yes.

</details>

<details>

<summary>Where are wallet private keys generated?</summary>

Inside the secure enclave.

</details>

<details>

<summary>Can database administrators access wallet private keys?</summary>

No.

</details>

<details>

<summary>Can cloud providers access wallet private keys?</summary>

No.

</details>

<details>

<summary>Are wallet private keys encrypted?</summary>

Yes.

</details>

<details>

<summary>How are wallet keys protected?</summary>

They are generated, stored, decrypted, and used only inside the enclave.

</details>

<details>

<summary>What is a secure enclave?</summary>

A hardware-isolated environment for sensitive operations.

</details>

<details>

<summary>Does transaction signing happen inside the enclave?</summary>

Yes.

</details>

<details>

<summary>Can developers export wallet private keys?</summary>

No.

</details>

<details>

<summary>Can organizations export wallet private keys?</summary>

No.

</details>

<details>

<summary>Can organizations import existing wallets?</summary>

No.

</details>

<details>

<summary>Does the enclave store decrypted keys?</summary>

No.

</details>

<details>

<summary>What happens if the API server is compromised?</summary>

Wallet keys remain protected by the enclave.

</details>

<details>

<summary>Can administrators view wallet private keys?</summary>

No.

</details>

<details>

<summary>Can administrators export wallet private keys?</summary>

No.

</details>

<details>

<summary>Can administrators create users?</summary>

Yes.

</details>

<details>

<summary>Can administrators create wallets?</summary>

Yes.

</details>

<details>

<summary>Can administrators execute transactions?</summary>

Yes, if policies allow.

</details>

<details>

<summary>Does WaaS support role-based access control?</summary>

Yes.

</details>

<details>

<summary>Can I retrieve wallet addresses?</summary>

Yes.

</details>

<details>

<summary>Can I retrieve organization information?</summary>

Yes.

</details>

<details>

<summary>Can I retrieve user information?</summary>

Yes.

</details>

<details>

<summary>Can I retrieve wallet information?</summary>

Yes.

</details>

<details>

<summary>Can I retrieve balances?</summary>

Yes.

</details>

<details>

<summary>Does WaaS support deposits?</summary>

Yes.

</details>

<details>

<summary>Does WaaS support withdrawals?</summary>

Yes.

</details>

<details>

<summary>Does WaaS support transfers?</summary>

Yes.

</details>

<details>

<summary>Does WaaS support swaps?</summary>

Yes.

</details>

<details>

<summary>Does WaaS support Public→Public transactions?</summary>

Yes.

</details>

<details>

<summary>Does WaaS support Public→Private transactions?</summary>

Yes.

</details>

<details>

<summary>Does WaaS support Private→Private transactions?</summary>

Yes.

</details>

<details>

<summary>Does WaaS support Private→Public transactions?</summary>

Yes.

</details>

<details>

<summary>Can WaaS perform batch payouts?</summary>

Yes.

</details>

<details>

<summary>Can WaaS be used for payroll?</summary>

Yes.

</details>

<details>

<summary>Can WaaS be used for treasury management?</summary>

Yes.

</details>

<details>

<summary>Can WaaS be used for payment processing?</summary>

Yes.

</details>

<details>

<summary>Can I estimate transaction fees?</summary>

Yes.

</details>

<details>

<summary>What fees apply to WaaS transactions?</summary>

Network fees and applicable Hinkal service fees.

</details>

<details>

<summary>Does WaaS support compliance workflows?</summary>

Yes.

</details>

<details>

<summary>Does WaaS support selective disclosure?</summary>

Yes.

</details>

<details>

<summary>Does WaaS share the same security model as the Hinkal API?</summary>

Yes.

</details>

<details>

<summary>Does WaaS use the same enclave infrastructure as the Hinkal API?</summary>

Yes.

</details>

<details>

<summary>What information should I provide when reporting a WaaS issue?</summary>

Provide Organization ID, User ID, wallet address, chain ID, endpoint used, request payload, error message, transaction hash (if applicable), and timestamp.

</details>