> **Description:** Details about API and product updates, including Management API enhancements, Recurring API improvements, Donations API webhooks, and Login API custom flows.

# Technical update February 2026

## Management API

Product orders now include `productType` in responses, making it easier to identify the type of product being ordered.
We've also added a `REJECTED` status to help you track when orders have been rejected.

The `hasRecurring` parameter simplifies prefilling product orders for recurring payments.

See: [Management API guide: Product orders](https://developer.vippsmobilepay.com/docs/APIs/management-api/management-api-guide.md#product-orders)

## Phone number support

### Greenlandic phone numbers (upcoming)

In Q1 2026, we will add support for Greenlandic phone numbers for private customers.

Previously, customers in Greenland could onboard MobilePay using Danish numbers. With this update, they can now use their Greenlandic phone numbers directly.

This means that you, as a merchant or partner, may see 6-digit phone numbers with country code +299 appear in API responses once this feature launches. No updates to your API integration are needed in order to receive Greenlandic phone numbers.

## 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).

### Transaction ID in charge webhooks

Charge webhook payloads now include a `transactionId` field. This helps you distinguish between multiple equivalent payment operations performed on the same charge, such as multiple captures.

See: [Recurring API guide: Charge webhook event payloads](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/recurring-api-guide.md#charge-webhook-event-payloads).

### Age verification enforcement

Starting December 9, 2025, the Recurring API enforces the age requirement by rejecting any attempt to sign a new payment agreement for users below 18 years of age.

See: [Under-18 users](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/how-it-works/payment-agreement/recurring-api-under-18-users-howitworks.md).

## Donations

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

### Webhook support for donation agreements

We've added webhook support for donation agreements, allowing you to receive real-time notifications when agreements are started or stopped.

See: [Donations API guide: Webhooks integration](https://developer.vippsmobilepay.com/docs/APIs/donations-api/api-guide.md#webhooks-integration).

### New agreement details endpoint

You can now retrieve comprehensive details about a specific donation agreement using the new
[`GET:/donations/v1/agreements/{agreementId}`](https://developer.vippsmobilepay.com/redocusaurus/donations-swagger-id.yaml) endpoint.

### Authentication changes for new integrations

The Donations product now uses merchant-level API clients for authentication.
You'll receive a client ID and client secret in the portal, and use
[Specialized Authentication](https://developer.vippsmobilepay.com/docs/APIs/access-token-api/specialized-authentication.md) to get your bearer token.

If you already integrated based on a Recurring Donations API client, it will still work, but we recommend moving to the merchant-level client once you have been approved for the Donations product.

See: [Donations API guide: Integration steps](https://developer.vippsmobilepay.com/docs/APIs/donations-api/api-guide.md#integration-steps).

## Login

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

### Custom consent collection flows

The new `customFlow` scope enables merchants to fully customize their consent collection experience using the flow builder in the business portal.
This is the recommended approach for new integrations requiring custom consent flows.

See: [Login API: Collecting consents](https://developer.vippsmobilepay.com/docs/APIs/login-api/api-guide/collecting-consents.md).

### Partner portal support

Partners can now manage Login product settings for their merchants directly from the partner portal.

See: [Partner portal guide: Managing Login](https://developer.vippsmobilepay.com/docs/partner/partner-portal.md#login-integration-details).

## ePayment API

### Profile sharing in GET response and webhooks

When you request profile information in a payment using `profile.scope`, the `userDetails` object is now returned directly in the GET payment response and in the `epayments.payment.authorized.v1` webhook payload -- no separate Userinfo API call required for the fields you requested.

See: [ePayment API: Profile sharing](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/profile-sharing.md).

## Webhooks API

**Coming soon:** We will be introducing automatic removal of webhook registrations that have consistently failed to receive deliveries for 2 weeks. This is not yet active, but we recommend reviewing your endpoint health in advance.

See: [Webhooks API guide: Faulty webhook servers](https://developer.vippsmobilepay.com/docs/APIs/webhooks-api/api-guide.md#faulty-webhook-servers).

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