> **Description:** Details about API and platform updates for June 2025, including new features, improvements, and important changes to Vipps services. # Technical update June 2025 ## Webinar on June 11: Summer update On June 11 we invite all merchants and partners to a webinar where we will present our latest product updates. This is the invitation: --- ### Welcome to Vipps MobilePay's summer update webinar We're kicking off the summer by inviting all customers and partners-- old, new or just curious-- to join our Vipps MobilePay summer update webinar Whether you work in e-commerce, are looking for new ways to boost conversion, or just want to stay updated on everything new in the Vipps MobilePay world, this session is for you! * When: June 11th, 09:00-10:30 CEST / 10:00-11:30 EEST * Where: Online! Add the webinar to your calendar **[with this .ics file](https://developer.vippsmobilepay.com/downloads/webinars/2025-06-webinar-summer-update.ics)** or jump in using **[this link on June 11](https://vipps.webex.com/vipps/j.php?MTID=m1cdddca2a25118ba7ed0b7a7aa06f216)** (password: `vmpupdate`). Why join? Get all the latest launches, practical tips, and summer inspiration from Vipps MobilePay--perfect for everyone in e-commerce. Agenda: * 09:00 - Welcome * 09:05 - Brand and user experience: Take advantage of our strong brands to increase conversion * 09:15 - Automatic update of cards & the Partner Portal * 09:30 - ePayments: Our most flexible and powerful API - now with Express payments in the Nordics * 09:45 - Recurring: User experience improvements, improved campaigns, 5x faster than before * 10:00 - Checkout: Payment links, support for Posten * 10:15 - Login and Loyalty * 10:25 - Q&A * 10:29 - Thank you! Know someone who might like to join? Feel free to forward this invite to colleagues, customers, or anyone else you think would enjoy a summer update with us! We can't wait to see you for a summer morning of insights and inspiration! Best, The Vipps MobilePay Team ### Webinar presentation and recording The presentation recording is on [YouTube](https://www.youtube.com/watch?v=S_f5gEoTLT4). ### Webinar Q&A Below are the questions and answers from the Q&A section of the webinar: **Does the auto card update feature work for cards already added, or only for new cards added after launch?** Great question! Automatic card updates work for all cards that have ever been added to the Vipps or MobilePay app - no matter when they were registered. We also update cards "in the future", for instance if a replacement card is issued before the original card has reached its expiry date. In short: Users only have to add their cards once, we take care of everything. **Do you support recurring payments on standalone card payments?** Recurring payments are only available via our Recurring API and require use of the Vipps or MobilePay app -- not on standalone card details. The Recurring API offers more functionality (including advanced campaign functionality) and a higher success rate than "card on file". If a Recurring charge fails, we will notify the user and help him/her to fix the problem, and make sure the charge is paid. Users can update their payment source anytime during their subscription (in Denmark and Finland it is also possible to pay from a budget account), and we continually help users resolve payment issues, achieving a very high payment success rate. For more details on how we notify and assist users with payment problems, see: [Notifications for failed charges](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/recurring-api-guide.md#notifications-to-users-for-failed-charges). **Why restrict recurring payments to in-app, when recurring on standalone cards could enable setups without extra gateways?** We believe our app-based Recurring solution outperforms "card-on-file" approaches, as proven by our industry-leading success rates. Over 80% of users prefer using Vipps/MobilePay instead of "card on file". To offer recurring card payments as a fallback, an additional gateway/acquiring agreement is required on the merchant side. A few key numbers: 12+ million users, 400,000+ shops and online stores, 1.3+ billion annual payments, 600+ employees, and leading Nordic market shares (for users over 15 years old): * Norway: 93% * Denmark: 92% * Finland: 59% **Can you add Vipps recurring after the first purchase if it wasn't initially set up? Is there documentation for this?** Yes, you can! Simply log in on the [business portal](https://portal.vippsmobilepay.com), find your existing sales unit, and add Recurring. All developer documentation is available here: [https://developer.vippsmobilepay.com/](https://developer.vippsmobilepay.com/). For a step-by-step API guide (including "how to order"), see: [Recurring API: API Guide](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/recurring-api-guide.md). ## Recurring payments ### Recurring API: 5x speed Users can now enter new agreements (subscriptions) in less than three seconds, five times as fast as before. There is nothing you need to do to get the benefits from this. See: [How it works](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/how-it-works/README.md). ### Recurring API: UX improvements We have improved the user experience in our app by redesigning several of the screens: * Enter agreements * Campaigns * Agreement overview * Agreement details The improvements make it easier for users to enter new agreements, understand the details of campaigns, and understand the details of their existing agreements. There is nothing you *must* do to get the benefits from this, but we recommend that you review the agreement `productDescription` and the charge `description`. We have seen that some have been a bit "creative" with these, and that may need to be fixed for it to look good on the new screens. See our [Recommendations](https://developer.vippsmobilepay.com/docs/knowledge-base/orderid.md). The improved designs will be live *very, very* soon, this month. ## Improve conversion on phones by opening URLs correctly We see that some merchants and partners show the [landing page](https://developer.vippsmobilepay.com/docs/knowledge-base/landing-page.md) on phones, and this can cause lower completion rates for payments. Users on phones should always get the automatic app-switch to the Vipps or MobilePay app, and *never* see the landing page. When the landing page URL is opened normally, the phone's operating system uses universal linking to recognize it as owned by Vipps MobilePay. This triggers an app-switch, automatically opening the Vipps or MobilePay app for seamless payment confirmation -- without user input. If the landing page is opened in a browser (with `window.location.href = url;`), the user is *redirected* to the URL, or similar, this app switch is blocked. The user is then forced to manually enter their phone number, approve launching the app, and confirm the payment again -- a tedious and unnecessary process. This leads to a poor user experience and lower conversion rates. The same problem occurs if the Vipps MobilePay landing page is shown in an iframe, web view, or embedded browser. See: [Can I show the landing page in an iframe?](https://developer.vippsmobilepay.com/docs/knowledge-base/landing-page.md#can-i-show-the-landing-page-in-an-iframe) **INFO** For the best results, always open the landing page directly from the phone's operating system, not in an embedded view. ## One more thing We're working on something exciting: Express, a future feature of the ePayment API. This will make payments simpler and faster, while allowing users to easily select their shipping address and delivery method. Want a glimpse of what's coming? Check out [How it works](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/express.md). If you've already integrated with the [ePayment API](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/README.md), adding Express when it's ready will be straightforward. You can learn more by visiting the [API guide: Express](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/express.md). Express will work in Norway, Denmark and Finland. > **Full site overview:** For every page in this documentation, read [https://developer.vippsmobilepay.com/llms.txt](https://developer.vippsmobilepay.com/llms.txt).