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

# Technical update Oct 2023

## Report API

The [Report API](https://developer.vippsmobilepay.com/docs/APIs/report-api/README.md)
version 2 is now available.

The API gives you, or your accounting partner, the ability to
fetch information about payment events that have been processed.
It is a REST API providing data in JSON format.

**Please note:**

* Accounting partners must use their
  [accounting keys](https://developer.vippsmobilepay.com/docs/partner/partner-keys.md#accounting-keys).
  Merchants are not allowed to share API keys with partners that have not been approved by
  Vipps MobilePay to make payments, as we are strictly regulated and must know who can make payments using our APIs.
* Accounting companies can use the
  [form](https://vippsmobilepay.com/en-NO/partner)
  to become an accounting partner.
* Merchants select their accounting partner on portal.vippsmobilepay.com as described here:
  [Give access to an accounting partner](https://developer.vippsmobilepay.com/docs/APIs/report-api/api-guide/overview.md#give-access-to-an-accounting-partner).

## Management API

The
[Management API](https://developer.vippsmobilepay.com/docs/APIs/management-api/README.md)
replaces the Partner API, and is available for all merchants and *most* partners:

* Prefill product orders in order to simplify and speed up onboarding of merchants
* Retrieve information about merchants and sales units

Partners: See
[Types of partner keys](https://developer.vippsmobilepay.com/docs/partner/partner-keys.md).

## ePayment API

The
[Long-living payment requests](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/long-living-payments.md)
feature in ePayment API is now supported in the latest version of the app on both iOS and Android.

When a payment is created with order lines, users can now see them before making the payment in the
latest version of the app on both iOS and Android.

## Recurring API

The
[Recurring V3 API](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/README.md)
now allows updating the interval of an active agreement. See
[Update an agreement](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/recurring-api-guide.md#update-an-agreement)
for more details.

## Test users

You can now create new test users on the portal.
See
[Test users](https://developer.vippsmobilepay.com/docs/knowledge-base/test-environment.md#test-users)
for details.

## MobilePay migration guides

There are several migration guides for how to move from the
MobilePay APIs to the new APIs.

## Deprecation of the SFTP service

The SFTP service is now deprecated, and will be shut down on 2024-03-01,
with a four-month warning according to the
[API lifecycle](https://developer.vippsmobilepay.com/docs/knowledge-base/api-lifecycle.md).

The
[Report API](https://developer.vippsmobilepay.com/docs/APIs/report-api/README.md)
is the replacement.

## Deprecation of the Partner API

The
[Management API](https://developer.vippsmobilepay.com/docs/APIs/management-api/README.md)
has replaced the Partner API.

For those few that still use the Partner API, please update as soon as possible.
The Partner API will be unavailable *at the latest* on 2024-03-01.

## Deprecation of the Checkout API v2

The
Checkout API version 2
will be shut down on 2024-01-01, so please make sure you're using version 3.

Checkout V3 improves upon V2 through alignment of polling and callback responses,
improvement of field names, and expanding models related to logistics options to permit
more advanced features.

Our migration guide
will take you through all the details, if you haven't already switched.

## Reminders

### Deprecation of the Recurring API v2

As announced in
[December 2022 technical update](https://developer.vippsmobilepay.com/docs/technical-updates/2022-12.md#recurring-api-v3),
the
[Recurring API version 2](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/README.md)
will be shut down on 2023-11-01, so please make sure you're using version 3.

Our migration guide will take you through all the details, if you haven't already switched.

### Please check your API calls for errors

We still see too much incorrect use of our APIs, and some errors cause payments to
fail, as well as bad user experiences. The API checklists explicitly says:

>Make sure to log and handle all errors. All integrations should display errors in a way that the users
>(customers and merchant employees/administrators) can see and understand them.

We are working on eliminating incorrect API use to ensure the best possible user
experience for all users and merchants. Please:

* Monitor the responses you get when making API calls
* Log all errors
* Fix errors as quickly as possible
* Use the
  API Dashboard (*no longer available*)
  to find problems with your integration.

## Questions or comments?

We're always happy to help with code or other questions you might have!
Please
[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).