Technical update 2024-09

This update was sent in September 2024.

Improved documentation search

The documentation search is now much better:

• More relevant results.
• Hierarchical results: Better overview
• Search as you type: Fast!
• Shortcut: Command-K (Mac) or Control-K (Windows)

Recurring API: future app changes

Based on the feedback from users in Norway, we are making it possible for Vipps users to stop their payment agreement in the app. Key takeaways from the survey:

• 20000 Vipps users took part in the survey
• 87 % answered they would like to manage their agreement in Vipps
• 85 % answered they are more likely take the subscription again if it was easy to manage

You can see what it looks like in the app.

⚒️ Important information for the merchants

1. Ensure that you listen to the recurring.agreement-stopped.v1 webhook event and update the subscription status on your systems accordingly. The actor field in the payload will indicate if it was stopped by the merchant or the user.
2. When a user stops an agreement:
   • Already RESERVED charges will not be cancelled. Merchants can cancel or capture based on their needs.
   • All PENDING/DUE charges are cancelled.
3. Attempts at creating new future charges for a stopped agreement will result in an error.

Merchants will have the option to disable the feature that lets users cancel payment agreements within the app. While we advise merchants against blocking users from canceling their agreements, they can opt out if they have a compelling reason and meet the specified requirements. However, it's important to note that opting out will exclude merchants from future functionalities related to managing agreements. For more information, see Recurring API FAQ: Can we opt out of showing Stop payment agreement in the app?

Partners: Save 90 % of the time by using "prefill" in the Management API

Partners can use the Management API to prefill the product order form and make it much easier for merchants to provide the correct information, product configuration, etc.

Our data shows that prefilled order forms saves 90 % of the time filling out the form, as the merchant only needs to check and submit. Processing the product orders is also faster, since the product orders are correct.

In short: Use prefill to make sure merchants go live faster.

Management API: Prefill available for management partners too

Partners that use management keys (see Partners: Types of API keys) can now use prefill product orders get information about product orders, and all other features of the Management API.

Management API: Improved sales unit details

The GET:/management/v1/sales-units/{msn} endpoint now returns more data about the sales unit:

{
   "msn":123456,
   "name":"ACME Fantastic Fitness",
   "businessIdentifier":{
      "scheme":"business:NO:ORG",
      "id":"9876543221"
   },
   "configuration":{
      "paymentAllowed":false,
      "captureType":"ReserveCapture",
      "skipLandingPageAllowed":false,
      "recurringAllowed":false,
      "partialCaptureAllowed":true,
      "lateCaptureAllowed":false,
      "landingPagePhoneNumberLocked":false,
      "longLivingPaymentAllowed":false,
      "creditCardPaymentAllowed":true
   }
}

See: Get information about a sales unit.

QR API: IN_STORE and VENDING categories for merchant callback QR codes

The merchant callbacks QR codes now offer two types of categories.

These will determine which waiting screen the user will see in the app after the QR code has been scanned, so the user gets a better user experience.

IN_STORE	VENDING

Allowing decimal values for tax rate

The ePayment API and Order Management API now accept decimal values for tax/VAT input on the receipts. The taxPercentage field is now deprecated, and replaced with taxRate to allow decimal values for the tax lines.

Get ready for MobilePay facade migration

For the merchants and partners using the existing MobilePay Subscriptions and App payments the time is approaching where you need to start migrating to the Recurring and ePayment API. We have improved and are expanding the migration guides to assist you in the migrations:

• MobilePay Subscriptions migration guide
• MobilePay App Payments migration guide

Prefill phone number on landing page for MobilePay Online

You can now add a field to the Initiate Payment request allowing the phone number to be prefilled on the landing page for MobilePay Online. For more information, see Prefill phone number on landing page.

Support for Danish and Finnish users in Vipps Login

Following the merger of Vipps and MobilePay, Vipps Login now supports Danish and Finnish MobilePay users.

Questions or comments?

We're always happy to help with code or other questions you might have! Please contact us.