Issues on Subscription and Recurring API
Incident
Report for Vipps MobilePay
Resolved
Between 10:56 - 11:47 CET we had slowness in:
• agreement activation, Agreements which were accepted by the user in the app were stuck in PENDING state.
• processing on unscheduled (oneoff) payments. Payments were stuck in PENDING or DUE state
• This could have caused the landing page and app switch to not take the user back to the merchant domain.
• No Agreement activation webhooks sent to the merchant
• No unscheduled charge webhooks sent to the merchant
• On polling by the merchant, the agreement would have been in PENDING state
After 11:47 CET, our systems are back to normal and all the agreements and payments that were stuck are processed. Agreements would have transitioned to either ACTIVATED (on successful charge processing) or EXPIRED (on failed charge processing). Agreement activation webhooks for all the stuck agreements were also sent.
Unscheduled payments would have transitioned to either CHARGED or FAILED. Unscheduled charges webhooks for all the stuck charges were also sent.
• agreement activation, Agreements which were accepted by the user in the app were stuck in PENDING state.
• processing on unscheduled (oneoff) payments. Payments were stuck in PENDING or DUE state
• This could have caused the landing page and app switch to not take the user back to the merchant domain.
• No Agreement activation webhooks sent to the merchant
• No unscheduled charge webhooks sent to the merchant
• On polling by the merchant, the agreement would have been in PENDING state
After 11:47 CET, our systems are back to normal and all the agreements and payments that were stuck are processed. Agreements would have transitioned to either ACTIVATED (on successful charge processing) or EXPIRED (on failed charge processing). Agreement activation webhooks for all the stuck agreements were also sent.
Unscheduled payments would have transitioned to either CHARGED or FAILED. Unscheduled charges webhooks for all the stuck charges were also sent.