Introduction
Introduction
The Paysafe Wallet SDK is provided for all popular front end technologies, like web and mobile (Android, iOS).
The Paysafe Wallet SDK is directly connected to Consumer APIs and does not require partners to host the wallet functionalities provided by the SDK in their backend systems.
Paysafe Wallet SDK is available only for regular customers and cannot be used to perform actions on wallets owned by legal entities and merchants.
To leverage the Paysafe Wallet SDK in your applications you need to properly configure and authenticate it, so it can access the customer wallet.
The configuration & authentication is a two-step process implemented with the support of your backend and it ensures secure access to the customer data.
SDK Configuration
The SDK configuration acts as a prerequisite that precedes onboarding and authenticating the user within the Wallet, accomplished by obtaining a Configuration Token. It is used to configure the SDK, enhance the overall fraud detection capabilities, and utilize the provided settings throughout the lifecycle of the partner's application.
During the SDK configuration, a digital identity for the device, called digital fingerprint, is created and stored, which must be provided during the user onboarding and authentication process. The digital fingerprint enhances the ability of systems to identify device and network irregularities, thereby improving overall fraud detection capabilities.
The SDK Configuration process takes advantage of the Configuration Authentication and uses it in order to configure the SDK and obtain the digital fingerprint.
SDK User Authentication
To ensure secure access to customer data by the SDK, it is necessary to provide a Customer Token. This token enables access to customer-specific information and the execution of sensitive actions (mostly related to funds movement). The Customer Token exclusively permits access to resources linked to the specific customer for whom the token was generated.
The SDK User Authentication process takes advantage of the Customer Authentication and uses it in order to authenticate the user for whom the wallet operations will be performed.