Vipps PSP API checklist

Only available for Vipps.

Endpoints to integrate

Integrate all the API endpoints.

Endpoint	Comment
Initiate a PSP payment	POST:/psp/v3/psppayments/init
Update the status of the PSP transaction	POST:/psp/v3/psppayments/updatestatus
Get the details of the PSP payment	GET:/psp/v3/psppayments/{pspTransactionId}/details
On the merchant side, be able to process EMVCo tokens	POST:makePaymentUrl
Respond with correct error information	POST:makePaymentUrl. See error codes list for possible responses.

When the checklist is completed, notify Vipps MobilePay Integration Service at developer@vippsmobilepay.com. Include examples from the test environment, pilot customer info, and a description of the implemented solution.

We will verify the integration and contact you. After the checklist is approved, we'll send you the information you need to get started.

Avoid integration pitfalls

Action	Comment
Support soft decline step-ups according to 3DS specifications.	In case of a soft decline (when the issuer requires 3DS), the PSP must host a 3DSecure session and must provide the URL to Vipps. See PSD2 Compliance and Strong Customer Authentication (SCA).
Do not rely on pspRedirectUrl	Some users may close Vipps immediately after seeing the payment confirmation, therefore not being "redirected" back to the merchant. Because of this, it is important for the merchant and the PSP to not base their transaction logic on the user reaching the pspRedirectUrl. See PSP Payment Sequence.
Provide reserve, capture, and refund information to Vipps	The PSP provides information of every capture and refund to Vipps (not just reserve)
Follow design guidelines	The Vipps branding must be according to the Design guidelines.

Live flow

1. The PSP completes all checklist items.
2. The PSP contact us with test IDs (pspTransactionId, merchantOrderId) in the test environment, showing that all checklist items have been fulfilled.
   • A complete order including Reserve, Capture and Refund, that has been updated with POST:/psp/v3/psppayments/updatestatus.
   • A complete order including Cancel, that has been updated with POST:/psp/v3/psppayments/updatestatus.
   • One ID for each of the error codes.
     • Some codes like 85 aren't applicable for all systems, please provide short description for why each code does not apply.
3. The PSP contact us to verify the integration in the production environment:
   • At least one IDs for orders with each of the following statuses: Capture, Refund, Cancel.
   • At least 3 IDs for orders with different error codes.
4. The PSP goes live 🎉