MobilePay Subscriptions becomes Vipps MobilePay

Background

MobilePay deprecates their old system behind MobilePay Subscriptions. We have, in alignment with MobilePay migrated all existing subscriptions in a way that they will continue to work with their new API on their Vipps MobilePay patform.

In Quickpay we have made sure that all existing integrations continue to function as usual, so that you don’t have to make any changes on your end. It will still be shown as MobilePay in the payment window, and you can still send “mobilepaysubscriptions” as the payment method on the subscription. We will redirect the payments to Vipps MobilePay in a way that they will be processed on their new platform.

New Acquirer and payment method

Some of the biggest changes to migrate to Vipps MobilePay is that the name changes. Therefor your newly created recurrings and Subscriptions will be with the acquirer “vmpeepayment” and with the Payment method “Vipps MobilePay”. In case you have any logic that relies on these values, makes sure to update accordingly.

OneOffs

It is still possible to create OneOffs with Vipps MobilePay, and the logic remains that this feature allows you to create recurrings which will be captured immediately. One new feature, however, is that it is possible to set “auto_capture:false” for OneOffs and thereby create a recurring that you manually need to capture afterwards.

Captures

Until now it has been required to send “auto_capture_at” when a recurring with MobilePay Subscriptions was created. This is still possible, and the logic behind stays the same. We have introduced a new logic that makes this field optional towards our API, however, we will automatically set it the date to today + 2 as this is the minimum requirement for Vipps MobilePay.

One of the biggest changes when going from MobilePay subscriptions and to Vipps MobilePay, is that we have introduced “pending captures”. This means that when you create a recurring which will be automatically captured in the future, these will now appear with the status “pending”

This is made this way because there have previously been doubts about whether you needed to manually capture the recurring, since the capture operation did not appear on the transaction. This caused people to try to send a capture request, even though that was not possible. Now it’s clearer that there is an awaiting capture operation.

Due to unforeseen complications, we have deemed it necessarry to remove the pending capture again. Therefore going forward only the authorize will be there until the capture has been fully completed by Vipps MobilePay.

Custom branding

When switching to the new payment method for Vipps MobilePay Subscription, we also introduce a multi-branded payment method. What this means is that the payment method switches between MobilePay and Vipps depending on what currency the subscription is created with. Everyone who had MobilePay Subscription had either DKK and EUR currency, and therefore uses Mobilepay.

In the Payment Window window, we switches the logo based on this currency if you are using our standard-branding. If however, you are using a custom branding you should either use the logo “vmp-mobilepay.svg” to use a mobilepay logo for your subscriptions, or follow the logic in our standard branding, to take either vmp-mobilepay.svg or vmp-vipps.svg logo. Otherwise we have added a default vmp-epayment.svg which is a multibranded logo with both a vipps and mobilepay logo.

In addition to the logo files, make sure that if you have built a custom branding, that things like redirects etc, are still functioning as expected. Again you can follow the practice of the standard-branding.

Subscritions with amount 0

After the migration, it is no longer possible to create new subscriptions with the amount 0 toward MobilePay Subscriptions / Vipps MobilePay Recurrings. This is due to a new way of differentiating between different types of Subscriptions. A differentiation that Quickpay does not have. And therefore this has given some issue for those of you that used to create subscriptions with amount 0, which will be declined.

We are sorry for the inconvenience and lost business that this has caused. ALthough it has never been best practise to create subscriptions with amoun 0 due to the fact that Quickpay has always seen the amount as the highest amount that you are going to charge on the subscriptions and the amount that the customer agrees to have charged. Quickpay does not automatically charge the subscription when created, so therefore, we encourage to set the correct amount.

We are working hard to fix the challenge so that again will be possible to create subscriptions with MobilePay subscriptions / Vipps MobilePay Recurrings with 0 as the amount.