Recurring API - Agreements with Initial charge affected
Incident
Report for Vipps MobilePay
Resolved
On 14th Jan 2025, we identified a bug in Recurring API that affected the agreement sign up flow from 11:54 to 16:01. During this period, agreements with INITIAL charge would have failed. These agreements were never activated, so the customer would have thought no payment happened. Instead, the initial charges were processed, i.e either reservation was made or the amount captured. The bug was resolved at 16:01. We have identified that around 900 transactions to be cleaned up.
On 15th Jan 2025, we cancelled the reservations of 572 transactions. We are working on refunding the 328 transactions that were captured.
For the merchants, if there are users who reach out to your customer support stating they were charged incorrectly, and if the transaction happened during the incident time frame 14th Jan 2025, 11:54 to 16:01, please let them know that Vipps Mobilepay are working on fixing this.
As on 16th January 10.32 CET, all affected transactions are corrected.
On 15th Jan 2025, we cancelled the reservations of 572 transactions. We are working on refunding the 328 transactions that were captured.
For the merchants, if there are users who reach out to your customer support stating they were charged incorrectly, and if the transaction happened during the incident time frame 14th Jan 2025, 11:54 to 16:01, please let them know that Vipps Mobilepay are working on fixing this.
As on 16th January 10.32 CET, all affected transactions are corrected.