How Recurring works with variable amount
In this scenario, the user can choose the max amount that they will allow the merchant to charge each payment. The suggested amount from the merchant is preselected in the list. This step is applied only for agreements with a variable amount.
For technical documentation go to: Recurring API guide.
Recurring variable amount pricing​
1. Buy a subscription​
A user chooses Vipps MobilePay as payment method for a subscription on a merchant's website or app.
Flow diagram: Step 1 — A user on a merchant's website or app selects Vipps MobilePay as the payment method to start a recurring 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.
Screenshot: Two-panel Vipps landing page: the left panel shows a "Recurring payment" screen with a phone number entry field and a "Next" button; the right panel shows an "Open Vipps" prompt with a phone graphic and the instruction to open the app to complete the payment.
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.
In this step the user can choose the max amount that they will allow the merchant to charge each interval. The suggested amount from the merchant is preselected in the list.
Screenshot: Three-screen flow in the app (Vipps or MobilePay): the first screen shows the recurring agreement with a "Max amount" row and a "Confirm and start" button; the middle screen shows a "Change max amount" list of selectable amounts with the suggested value pre-checked; the third screen shows the agreement updated with the user's chosen max amount.
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.
Flow diagram: Step 4 — The user is redirected back to the merchant's website or app, where the subscription is confirmed.
5. Due charges​
Upcoming charges are displayed in Vipps MobilePay for the user to see. If a charge fails for any reason and there are retry days left, a failure text is visible for the user on the charge. This text will explain to the user what went wrong and how they can fix it.
Extra notification if users max amount is too low​
If the user has a lower max amount than the charge that is created, the user will get a push notification. An explanation text is also shown on the charge in Vipps MobilePay.
This notification and failure text is triggered and shown when the charge is set as due.
Screenshot: Three screens showing the max-amount notification flow in the Vipps app: a lock-screen push notification (in Norwegian) alerting the user that the upcoming charge exceeds their agreed max amount; the payments list with an affected charge highlighted in red prompting the user to update the max amount; and the charge detail screen showing a red error banner instructing the user to increase the max amount or the payment will fail.
6. Overview and manage agreement​
The user can see their active subscriptions, as well as stopped subscriptions, and get an overview of previous charges in Vipps MobilePay.
If the user clicks on max amount, they can choose a new max amount for the agreement.
Screenshot: Three-screen flow in the app (Vipps or MobilePay): the first screen shows the active subscription overview with the price listed as "Variable", frequency "Paid every month", and "Payments" and "Manage agreement" menu items; the second screen shows a "Manage agreement" bottom sheet with options to change the payment card, adjust the max amount, toggle payment notifications, visit the merchant, or stop the agreement; the third screen shows a "Change max amount" list of selectable amounts.
For technical documentation go to: Recurring API.