Technical update October 2025
💥 DRAFT! This is still being updated, and will be sent by email and on Slack when complete. 💥
Recurring Payments
This section shows new features in the Recurring Payments product and the Recurring API.
New designs in the app
To be provided.
Age verification for recurring agreements
Norway only: Users must be 18 years old to enter legally binding recurring payment agreements.
The Recurring API now enforces this age requirement by automatically rejecting agreement creation for users younger than 18. This provides an additional safety layer while age verification remains the merchant's responsibility.
Portal
This section shows new features in the portal.vippsmobilepay.com, business portal and partner portal.
Payment Insights
A new feature, Payment Insights, is now available in the portal.vippsmobilepay.com for both partners and merchants. Payment Insights gives access to key business metrics, such as transaction volume, success rate, and conversion rates.
With Payment Insights, it's easy to assess the quality of your Vipps MobilePay integration. You can quickly identify whether your setup meets best practice standards, spot sales units that are performing exceptionally well or underperforming, and detect any shifts in performance that may require attention.
For more details, see:
Single Sign-On (SSO) for business portal
The business portal, portal.vippsmobilepay.com, now supports single sign-on (SSO), making it easier for businesses to manage portal access using their existing authentication systems.
Supported identity providers:
- Microsoft Entra ID (formerly Azure AD) with OIDC
- Okta with OIDC
For more details, see: SSO documentation.
Webhooks & error monitoring
Merchants and partners can now view their registered webhooks in portal.vippsmobilepay.com, as well as any errors encountered during webhook delivery attempts.
Merchants can:
Partners can:
See: Webhooks API.
When webhooks fail, it often leads to failed payment processes, causing users to perceive that "Vipps MobilePay doesn't work".
Tip: If you don't receive the expected webhook, always poll the API to ensure accurate payment status. See Polling guidelines.