> **Description:** Details about API and platform updates for October 2020, including new features, documentation improvements, and key changes to Vipps services.

# Technical update Oct 2020

## Userinfo

Vipps now offers the possibility for merchants to ask for user profile details as part of the payment flow in the
[eCom API v2](https://developer.vippsmobilepay.com/docs/APIs/ecom-api/vipps-ecom-api.md#profile-sharing)
and
[Recurring API](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/recurring-api-guide.md#profile-sharing).

This is done by adding a `scope` parameter to the initiate calls:

* `address`
* `birthDate`
* `email`
* `name`
* `phoneNumber`
* `nin` (*fødselsnummer*)
* `accountNumbers`

The userinfo endpoint is shared with
[Vipps Login](https://developer.vippsmobilepay.com/docs/APIs/login-api/README.md)
and the merchant needs to have
[activated Vipps Login](https://developer.vippsmobilepay.com/docs/APIs/login-api/login-api-faq.md#how-can-i-activate-and-set-up-login)
on their account to use this feature.

Using the Vipps Login service itself is optional.

### Customer registration

Vipps Login can also be used if you need to register your customers because of
the Covid-19 pandemic.

## New plugins

There are now 12 Vipps plugins for various ecommerce platforms:
WooCommerce, WordPress, Magento, Episerver, Drupal, Shopify, Craft, and more.

All [plugins](https://developer.vippsmobilepay.com/docs/plugins/README.md) are open source. See the complete list.

## PSP v3

Vipps MobilePay is launching the
[PSP API v3](https://developer.vippsmobilepay.com/docs/APIs/psp-api/README.md)
to coincide with our migration of our users' cards from PAN to EMVco network
tokens. This technological migration is Vipps' strategy for achieving delegated
SCA once PSD2 comes into effect for card payments on 2021-01-01.

The PSP API v3 is functionally identical to PSP API v2 apart from the
additional payment source format. There are also minor changes to naming of
properties to bring the API in line with Vipps' API standards.

Encrypted cards will still be sent for our users' cards that have not yet been
migrated.

## Rate limiting

Vipps has implemented rate limiting on our external APIs in order to offer a
more robust and secure service. Most of these limits are only created to
counteract unexpected and erratic behavior, and it's nothing you should notice
under normal operation. More information about this is available in the
documentation for
[Recurring API](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/recurring-api-guide.md#rate-limiting)
and
[eCom API](https://developer.vippsmobilepay.com/docs/APIs/ecom-api/vipps-ecom-api.md#rate-limiting).

## Deprecation

### Deprecation of `/status`

The `/details` endpoint in the eCom API v2 offers more than the old
and long deprecated `/status` endpoint. We still see some customers using
the old endpoint and strongly recommend updating to the
[current one](https://developer.vippsmobilepay.com/docs/APIs/ecom-api/vipps-ecom-api.md#get-payment-details).

### Deprecation of Vipps for Magento 1

The
[Vipps Payment Module for Magento 1](https://github.com/vippsas/vipps-magento-v1/blob/master/README.mdx)
is deprecated because of the high security risk in continued use of Magento 1.

## Reminders

We have mentioned some things before, and take this opportunity to remind you:

### API lifecycle

Our API lifecycle policy is
[available on GitHub](https://developer.vippsmobilepay.com/docs/knowledge-base/api-lifecycle.md).

### Status pages for test and production environments

See [Status pages](https://developer.vippsmobilepay.com/docs/knowledge-base/status-pages.md).

### How to get help quickly

Please see
[this page](https://developer.vippsmobilepay.com/docs/contact.md).

### Technical updates archive

Please see: [technical updates](https://developer.vippsmobilepay.com/docs/technical-updates/README.md)

## Questions or comments?

We're always happy to help with code or other questions you might have!
Please create [GitHub issues or pull requests](https://github.com/vippsas)
for the relevant API,
or [contact us](https://developer.vippsmobilepay.com/docs/contact.md).

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