Skip to main content

How Recurring works

Recurring can be used for subscriptions, donations or other recurring payments.

For technical documentation go to: Recurring API.

The recurring payment process

recurring process

1. Buy a subscription

A user chooses Vipps MobilePay as payment method for a subscription on a merchant’s website or app.

Buy subscription

2. The landing page

If the agreement was started on a desktop device, the user will be sent to the Vipps MobilePay landing page. The user confirms their number and is prompted to log in to Vipps MobilePay.

If the agreement was started from a mobile device, the app will automatically switch over to Vipps MobilePay.

Landing page

3. Accept agreement

The user receives a push notification on their phone. They log in to Vipps MobilePay and accept the agreement.

If there is an initial charge to be paid, the user confirms the payment in this step as well.

Accept agreement

4. Confirmation of subscription

The user is redirected back to the merchant’s website or app, and the subscription is confirmed on the merchant’s page.

Please note: Activation of the agreement is not guaranteed to be finished by the time the user is redirected back to the merchantRedirectUrl. The agreement could still have the status PENDING, so it is important to continue to poll the status of the agreement until a final status is returned by the API.

Confirmation of subscription

5. Overview of agreements and charges

The user can see their active subscriptions, as well as stopped subscriptions, and get an overview of previous charges in Vipps MobilePay.

Overview of agreements

6. Manage agreements

If the user clicks on “Manage agreement” in the previous step, they will be sent to the merchant’s site where they can manage their subscriptions. We recommend using Login to make login to the merchant’s site go smoothly.

Manage agreements

Great! Now you know how the Recurring payment process works.

Take a look at the technical documentation in the Recurring API Guide.

Help us improve our documentation

Did you find what you were looking for?