> **Description:** Details about API and product updates, including recurring payment enhancements and business portal SSO.

# Technical update November 2025

## Recurring Payments

This section shows new features in the
[Recurring Payments product](https://vippsmobilepay.com/en-NO/billing-recurring)
and the
[Recurring API](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/README.md).

### One day lead time for recurring charges

Merchants and partners can now create a new charge one day before the charge due date, instead of two days.
See: [Recurring API guide - Due date](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/recurring-api-guide.md#due-date).

### Deep links are not recommended

Deep links that use custom URL schemes (e.g., `vipps://`) for direct app-to-app switching are not recommended.
For a smoother and more reliable user experience in the payment agreement signup flow, always use universal links.

See: [App flow recommendations](https://developer.vippsmobilepay.com/docs/knowledge-base/app-flow.md).

### Age verification for payment agreements

In  Norway,  Denmark, and  Finland: Users must be at least 18 years old to enter into legally binding payment agreements.

Starting 2025-12-09, the Recurring API will enforce this age requirement by rejecting agreement creations for users under 18.
This adds an extra layer of protection, while age verification remains the responsibility of the merchant.

For more details, see our
[guidelines for under-18 user flows](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/how-it-works/payment-agreement/recurring-api-under-18-users-howitworks.md).

### Improved user experience for existing payment agreements

We're introducing an improved user experience in the app for how existing payment agreements are displayed.
The new design will be launched in early November.
For a preview, see the [Existing payment agreements](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/how-it-works/payment-agreement/manage-payment-agreement-howitworks.md) section in the documentation.

### Demo updated

The Recurring demo "store" is updated, and you can now try out campaigns, profile sharing and lots of other functionality,
and see exactly what it looks like on our app:
[`demo.vipps.no`: Recurring](https://demo.vipps.no/recurring).

## Portal

This section shows new features in the [portal.vippsmobilepay.com](https://portal.vippsmobilepay.com/),
business portal and partner portal.

### Payment Insights

A new feature, *Payment Insights*, is now available on [portal.vippsmobilepay.com](https://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,
and 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.

### Single Sign-On (SSO) for business portal

The business portal, [portal.vippsmobilepay.com](https://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: [About the business portal: SSO documentation](https://developer.vippsmobilepay.com/docs/knowledge-base/portal.md#single-sign-on).

### Webhooks and error monitoring

Merchants and partners can now view their registered webhooks in
[portal.vippsmobilepay.com](https://portal.vippsmobilepay.com/),
as well as any errors encountered during webhook delivery attempts.

**Merchants can:**

* [View registered webhooks](https://developer.vippsmobilepay.com/docs/knowledge-base/portal.md#view-registered-webhooks)
* [View webhook errors](https://developer.vippsmobilepay.com/docs/knowledge-base/portal.md#view-webhook-errors)

**Partners can:**

* [View registered webhooks](https://developer.vippsmobilepay.com/docs/partner/partner-portal.md#view-your-webhooks)
* [View webhooks errors](https://developer.vippsmobilepay.com/docs/partner/partner-portal.md#view-your-webhooks)

See: [Webhooks API](https://developer.vippsmobilepay.com/docs/APIs/webhooks-api/README.md).

**INFO**

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](https://developer.vippsmobilepay.com/docs/knowledge-base/polling-guidelines.md).

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