> **Description:** Find answers to common questions about implementing profile sharing with the Userinfo API, including

# Profile Sharing and Userinfo API FAQ

Common questions about implementing profile sharing with the Userinfo API. For general questions about profile
sharing features in specific payment APIs, please refer to their respective documentation.

## How can I get updated profile information from users?

You can request profile sharing as part of a payment flow, asking users to share their Vipps MobilePay
information (e.g., address, email, phone number) through a payment request.
See the [API guide](https://developer.vippsmobilepay.com/docs/APIs/userinfo-api/userinfo-api-guide.md) for details.

**Looking for Login-based profile sharing?**

If you want to implement profile sharing through the Login flow (without payments), please refer to the
[Login API guide: user info](https://developer.vippsmobilepay.com/docs/APIs/login-api/api-guide/user-info.md) documentation instead.

## I can still get the profile information after the user has revoked consent

For the payment session only, there may be some delay in consent revocation.

To better support merchants that do not handle online fetching and processing
of the user info as part of a **payment session**, we keep this information accessible
for the merchant for the next **168 hours**. The data will be available even if the user revokes the
consent in this period. Revoking consents will immediately affect future payment sessions.

## Can we fetch the user data after the time-limit

Once the time limit has expired, it is no longer possible to retrieve user data through the API.
For privacy reasons, Vipps MobilePay cannot provide user data manually after the expiration of the time limit,
as user consent does not cover such actions.

> **Full site overview:** For every page in this documentation, read [https://developer.vippsmobilepay.com/llms.txt](https://developer.vippsmobilepay.com/llms.txt).