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

# Technical update Nov 2022

## Specify amounts in øre without decimals

Vipps MobilePay requires amounts to be specified in øre, without decimals:
"Amounts are specified in minor units.
For Norwegian kroner (NOK) that means 1 NOK = 100 øre. Example: 499 NOK = 49900 øre."

We still see some attempts at specifying payments with amounts that
end in `.0000001`.

API requests with incorrect amounts will fail: Both initiate, capture and refund.

Please check for rounding errors, and of course: Always monitor the responses
to your API requests:
[Please check your API calls for errors](#please-check-your-api-calls-for-errors).

## Get ready for "black week"

Let your customers pay with
[Vipps Hurtigkasse](https://developer.vippsmobilepay.com/docs/APIs/ecom-api/vipps-ecom-api.md#express)
with the new and improved user experience by specifying
`useExplicitCheckoutFlow": true`
to reduce drop-off and abandoned shopping carts.

Make sure your use of Vipps MobilePay is as good as it can be, without errors.
See: [Please check your API calls for errors](#please-check-your-api-calls-for-errors).

Monitor the Vipps Status Page:
`vipps.statuspage.io` (link updated to [https://status.vippsmobilepay.com](https://status.vippsmobilepay.com) on 15 January 2024)

## eCom API: Don't rely 100 % on callbacks

Callback offers a faster user experience than polling, but you
cannot rely on callbacks alone. You must also poll
[`GET:/ecomm/v2/payments/{orderId}/details`](https://developer.vippsmobilepay.com/redocusaurus/ecom-swagger-id.yaml)
as described in the
[Polling guidelines](https://developer.vippsmobilepay.com/docs/knowledge-base/polling-guidelines.md).

See:
[Callbacks](https://developer.vippsmobilepay.com/docs/APIs/ecom-api/vipps-ecom-api.md#callbacks)

## Report API

The
[Report API](https://developer.vippsmobilepay.com/docs/APIs/report-api/README.md)
gives you or a third-party acting on your behalf the ability to
fetch information about payment events that have been processed by Vipps.

## Documentation improvements

We are working hard to improve the
[Vipps Technical Documentation](https://developer.vippsmobilepay.com/):

* The documentation is now
  [searchable](https://developer.vippsmobilepay.com/search).
* We have a new
  [Recommended flows](https://developer.vippsmobilepay.com/docs/recommended-flows/README.md)
  section to highlight combinations of APIs, such as
  [In-store using merchant scan](https://developer.vippsmobilepay.com/docs/recommended-flows/loyalty-in-pos/README.md)
  and
  [Electric vehicle charging](https://developer.vippsmobilepay.com/docs/recommended-flows/ev-charging/README.md).
* All APIs now have a quick start
  with Postman collection. We also have a global Postman environment to make it
  easier to test all APIs without doing any development.

Please
[tell us what you think](https://forms.office.com/pages/responsepage.aspx?id=XcJbgGSO1k6NJDiDyQaMWuRWudsvYRxEorAi1xx_iqJUQzg4QzExTVhHM1UzMDIwM1lINkpaNTdWUC4u)
in this short, 3-minute survey - thanks!

## Check your phone number format

Far too many Vipps payments fail because of badly formatted phone numbers.
We try to silently correct them, but we can't fix all errors.

This is especially important when using
[Skip landing page](https://developer.vippsmobilepay.com/docs/knowledge-base/landing-page.md#skip-landing-page),
as it's impossible to send a push message to a user if the specified phone number is incorrect.

Please see the API specification:
[`POST:/ecomm/v2/payments`](https://developer.vippsmobilepay.com/redocusaurus/ecom-swagger-id.yaml)

## Reminders

### Please check your API calls for errors

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

We are working on eliminating incorrect API use. Please:

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

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