Best Practices

Follow this page to learn about best practices as a wallet service developer

Configure permissions

Wallets should support the ability to configure connections directly from the wallet service (e.g. Alby Hub allows you to define permissions such read account balance and make payments)

Manage access permissions example from Alby Hub

Set budgets

Users are going to link their wallet account to apps to send and receive payments natively in apps. Enabling your users to set budgets creates an efficient safety measure to not overspend.

Manage budgets example from Alby Hub

Unique Keys

Use unique wallet keys for each connection. This keeps your user's activity across different apps completely separate.

Sub-wallets

Sub-wallets allow your users to completely isolate their activity, so that apps can only see and access data and funds for that specific app.

Last updated