Providers are apps that enable their users’ embedded wallets to be used in other apps. Becoming a provider enables your users to use their embedded wallets and assets from your app elsewhere, allowing them to transact from an existing balance, aggregate assets, and more.

Before sharing your uses’ wallets as a provider app, you must enable a base domain for your app.

Enabling a base domain helps secure your users’ wallets in a cross-app context. Read more about security for cross-app wallets and follow this guide to set up a base domain!

​
Configuring your app as a provider

To become a provider and share your users’ embedded wallets with other apps, simply visit the Privy Dashboard and navigate to the User management > Global Wallet section.

Under the My app tab of this page, enable the Make my wallet available for other apps to integrate toggle. You should also upload a square logo image with aspect ratio 1:1 to be shared with other apps. We recommend a JPEG or PNG with size 180px by 180px for best results.

Once enabled, your app will show up as an available wallet provider that other apps can integrate via the Integrations tab of this page.

You can also see apps that have actively integrated your wallets under the My ecosystem tab.

​
Transaction scanning

As an additional security feature, Privy is integrated with Blockaid transaction scanning to ensure that all transactions from your users’ global wallets are safe and secure.

Transaction scanning has two levels of security; validation and simulation. With transaction validation, users will be notified if the transaction has been flagged by Blockaid as suspicious or malicious. Blockaid will also simulate the transaction with the wallet, showing the token and USD value or exposure difference if the transaction is approved.

To enable transaction scanning for your global wallet users, navigate to the Global wallet > My app page of the Privy Dashboard and toggle the Blockaid transaction simulation setting on.

Privy has a default API key your app can use for testing but to prevent rate limiting your app should configure its own Blockaid API key in the dashboard.

​
Read-only mode

When sharing your users’ embedded wallets with other apps, your users are protected from any malicious developer. Usage of embedded wallets across apps are strictly domain-segregated and every user action requires explicit consent in a third-party app.

If you would like to limit the scope of your users’ wallets to only be read-only in other apps, click the Read-only mode checkbox within the My app tab. With this setting enabled, requester apps may see your user’s wallet addresses, but not request signatures or transactions from them.

This may be particularly useful for setups where users verifying ownership of assets from your app in other apps, but not necessarily transacting with them.