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

# Technical update Sep 2021

## The QR API

An early version of the
[QR API](https://developer.vippsmobilepay.com/docs/APIs/qr-api/README.md)
is available.

The QR API lets merchants generate Vipps QR codes that can be used to pay
over the counter, without requiring the Vipps user to provide their telephone
number to the merchant.

The QR code, when scanned and opened, will redirect the user to the Vipps
landing page, which on the phone will automatically trigger a switch to the
Vipps app where they can pay the merchant.

## The Order Management API

An early version of the
[Order Management API](https://developer.vippsmobilepay.com/docs/APIs/order-management-api/README.md)
is available.

The Order Management API allows merchants to send rich order information to their
existing Vipps transactions. This information is shown to the customer in the
app in their order history. This functionality is available for both recurring
and direct payments, but not for pass-through payments.

## The Partner API

An early version of the Partner API is available.

The Partner API will let partners, banks and large corporations
manage their merchants and sales units. See the GitHub repository for
background and priorities.

## Vipps Login support for authentication/registration outside of browser/app (CIBA)

The Vipps Login service has been extended with Client Initiated Backchannel Authentication
(CIBA) flows to support use cases where authentication/registration does not start in a browser or an app.

This could typically be physical contexts like point of sales (POS) solutions, on the
phone in call center solutions, or devices/terminals like TV boxes. We currently support initiating logins based on the
user's phone number. We are also working on supporting the same flows with the user scanning the merchant's QR-code as a
starting point.

More information can be found in the
[Login API Guide](https://developer.vippsmobilepay.com/docs/APIs/login-api/README.md).

## The Recurring API now supports variable amounts

Recurring agreements with variable amount lets merchants charge users a different amount each interval,
based on the user's specified max amount.

More information can be found in the
[Recurring API Guide](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/recurring-api-guide.md#variable-amount-pricing).

## API Dashboard for the test environment

*UPDATE from 2024-01-12: The API Dashboard is deprecated.*

The API Dashboard is now available for both the production and test environments.
See it on the portal in the *Utvikler* section.
Here's an example:

## Removed HTTP 402 errors

The eCom API previously sent `HTTP 402 Payment Required` for some errors.
That HTTP status is "reserved for future use", and our use was a bit *creative*.

We now send `HTTP 400 Bad Request` instead, with more details in the message body.

Since this is *still* an error that can and must be fixed by the merchant,
we have concluded that the change does not require a new version of the API.

## Technical updates archive

All the previous technical updates are in the
[Technical updates archive](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).