Provider Extensions

Provider Extensions is an extra layer on top of the core SDK, it bundles a set of useful backend interactions that could save you some time and effort. In addition to Venly's services, these functions also interact with your backend services (such as an identity system or inventory system).

FunctionDescription
HasWalletChecks whether a wallet has been linked to the logged-in User
CreateWalletForUserCreates, links (Backend Identity Service), and returns a new wallet for a (new) logged-in User (If none is linked already)
GetWalletForUserRetrieves the wallet for an (existing) logged-in User
HasMarketUserChecks whether a MarketApi SubUser has been linked to the logged-in User
CreateMarketUserForUserCreates, links (Backend Identity Service), and returns a new MarketApi SubUser for a (new) logged-in User (If none is linked already)
GetMarketUserForUserRetrieves the MarketApi SubUser for an (existing) logged-in User

Developer Mode

Provider extensions are not supported when using Developer Mode.

Beamable

These extensions will automatically streamline essential interactions with Beamable's services from inside your Beamable Microservice. Tasks such as retrieving a walletId from the active user or linking a walletId to an active user are handled automatically. This Default Behavior offers a built-in, straightforward, and user-friendly approach for executing common interactions with the Beamable Backend.

📘

The Default behavior is part of the VenlyAPI.Companion.Beamable assembly (C#). The default behavior can be altered if necessary.

For Beamable, the Default Extension Behaviour stores the data, such as walletId/subUserId, as a private Stat of the corresponding user. Feel free to override this Default Behaviour by Overriding the Provider Extensions for Beamable.

PlayFab

These extensions will automatically streamline essential interactions with PlayFab's services from inside your Azure Cloud Function. Tasks such as retrieving a walletId from the active user or linking a walletId to an active user are handled automatically. This Default Behavior offers a built-in, straightforward, and user-friendly approach for executing common interactions with the Playfab Backend.

📘

The Default behavior is part of the VenlyAPI.Companion.PlayFab-Azure assembly (C#). The default behavior can be altered if necessary.

For PlayFab, the Default Extension Behaviour stores the data (like 'walletId') inside the Internal Player Data of the corresponding user. Feel free to override this Default Behaviour by Overriding the Provider Extensions for PlayFab.