Skip to content

Latest commit

 

History

History
66 lines (35 loc) · 2.61 KB

vipps-recurring-api-howitworks.md

File metadata and controls

66 lines (35 loc) · 2.61 KB

Vipps Recurring API: How It Works

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

For technical documentation go to: Vipps Recurring API.

The recurring payment process

recurring process

1. Buy a subscription with Vipps

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

Buy subscription with Vipps

2. The Vipps landing page

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

If the payment was started from a mobile device, the app wil automatically switch over to Vipps.

Vipps landing page

3. Accept agreement in Vipps

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

If there is an initial charge to be made, 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 web site or app, and the subscription is confirmed on the merchant’s page.

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.

Overview of agreements

6. Manage agreements

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

Manage agreements

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

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

Questions?

We're always happy to help with code or other questions you might have! Please create an issue, a pull request, or contact us.

Sign up for our Technical newsletter for developers.