Skip to main content

iOS Components v3.1.0

· One min read

The method for exchanging tokens in the biometrics login flow has been updated to make implementation simpler.

Key changes​

On biometric login, a token is returned to the SDK; this token is used for two purposes:

  1. For your backend to swap for an access token, which can then be used by your backend for all Weavr API endpoints
  2. To be set automatically in the SDK, so that UI components (for example card components) can de-tokenizeTokenize Replace a card's primary account number (PAN) with a unique digital token that stands in for the real card during a transaction. When a cardholder adds a card to Apple Pay or Google Pay via push provisioning, the wallet provider stores a device-specific token rather than the underlying PAN, so the real card number isn't exposed on the device or shared with merchants. values retrieved by your backend and display the information in plain text to the user. It is no longer required to call "Set user token" (setUserToken) for UI components.

See biometrics overview for a swimlane of a sample implementation, and the iOS documentation for specific instructions.