Integrate from a mobile app
App integrations are currently based on using browsers.
You can enable automatic switch of users back to the merchant app, from the Vipps or MobilePay app.
This flow is designed to be used with apps. It requires that the app initiate Login in an external browser that is opened within the app, as described in Using Login in native applications.
You should not use web views.
The merchant must specify the app URI, where the user will be returned after completing the confirmation in the Vipps or MobilePay app.
Merchant app -> Merchant app controlled browser -> Vipps or MobilePay app -> Merchant app controlled browser -> Merchant app
This flow can be enabled per login request by adding the
app_callback_uri parameters to the Authorize request.
This flow requires both the
app_callback_uri should be a URI that makes the device switch back to the merchant's
app again after the Vipps or MobilePay app portion of the flow is done (example: "merchant-app://callback").
redirect_uri is opened in the browser once the login flow is completed there.
This URL can either redirect the user to a page in the browser, or be handled/intercepted by the merchant app.
In either case it is important to avoid using static client secrets in the app for completing the login.
(For more information, see AppAuth for Android Utilizing client secrets (DANGEROUS)
and OAuth 2.0 for Native Apps: Client Authentication).
Both URIs must be added in the portal.vippsmobilepay.com, you find more information on how to do this Developer resources: Portal: How to set up login on your sales unit?.
Please note: URIs specified on portal.vippsmobilepay.com
must be exactly the same as used in the API calls. Be extra careful with
/ and URL-encoded entities. If the URIs are not identical, you will get
The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client
The Vipps or MobilePay app will return some data with the return to the
It contains two query parameters
State is the OIDC
state parameter passed at the start of a login which can be used to identify the specific login if needed.
resume_uri parameter that we generate
can optionally be used to resume the login when the user returns from the Vipps or MobilePay app.
If the merchant app manages to keep the initial browser window open it is not required to use the
To use the
resume_uri, it must be opened in the same browser used in the initial phase
ASWebAuthenticationSession or Chrome Custom Tabs). It is required that the browser contains the cookies
from the interaction that happens before the user is sent to the Vipps or MobilePay app.
A typical flow/implementation might look like this
The dotted lines in this diagram are handled by us (or the user), while the filled lines need to be implemented by the merchant.
- Merchant backend generates an OpenID authentication flow authorization URI. The URI is communicated to the merchant app.
- Merchant app uses the URI to initiate Login in an external browser that is opened within the app, see the specification for details.
- Login will open the Vipps or MobilePay app, if required. (If the user is remembered in the browser, they will be authenticated directly, and they will then be on step 6 below).
- Vipps or MobilePay app opens the deep link
app_callback_uriparameter after the user has approved the login.
- Merchant app handles the link in one of two ways:
- Display the same browser instance that was created in 1.
- Open a browser again using the
resume_uri-query parameter that is returned with the request to the
- Login finalizes the authentication of the user and obtains consent to share information if needed.
When this is finished the user will be redirected to the
redirect_uri. The Login process has now finished, and the merchant controls the remaining process.
- Merchant app sends the
stateparameters received in the callback to the merchant backend.
- Merchant backend fetches the access tokens and user information.
Example authorize request URL:
state and possibly
error will be passed as query parameters to the
state parameter has the same value as the
state parameter passed to the Authorize request.
Example success callback from app (step 4):
Example error callback from app (step 4):
Example success callback from browser (step 6):