Skip to main content

Vipps PSP API checklist

View as Markdown (opens in a new tab)
Install AI tools

Give your assistant up-to-date guidance for our APIs, with our plugin or without it.

The plugin is still under development. See the AI tools page for details.

Run both commands, in order.

claude plugin marketplace add vippsas/agent-toolkit
claude plugin install vipps-developer@agent-toolkit

For troubleshooting, see the full instructions.

End of life

This API doesn't have any set end of life yet, but is receiving critical maintenance only. Long-term support for PSPs will be served by the ePayment API. No new integrations to this API will be approved.

This API is only available in the Norwegian market.

To ensure that your system is ready for production, we must verify your solution in test and production. Once we have verified that the steps have been completed successfully, you are ready to go live.

Before moving to production, you must have performed the following actions. All actions are mandatory unless explicitly stated otherwise.

Send your filled out Vipps PSP checklist to us at developer@vippsmobilepay.com. Use this editable PDF to fill out and submit. Request examples in the checklist must be no more than 1 month old when you submit the checklist.

Download the editable Vipps PSP checklist

Download the PDF — an editable PDF you can fill out and track your progress.

Vipps PSP checklist​

Endpoints to integrate​

PurposeEndpoint
Initiate a PSP paymentPOST:/psp/v3/psppayments/init
Update the status of the PSP transaction
RESERVED CAPTURED CANCELLED REFUNDED		POST:/psp/v3/psppayments/updatestatus
Get the details of the PSP paymentGET:/psp/v3/psppayments/{pspTransactionId}/details
Receive makePaymentRequestPOST:makePaymentUrl
Respond with correct error information
See error codes list for possible responses.		POST:makePaymentUrl.

Mandatory implementations​

Support soft decline step-ups​

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.

App Switch​

If you offer your merchants the option to use apps, you must test a switch between the Vipps app and a merchant app.

Payment status​

All payments must be updated with capture or cancel status, as well as refund if this is performed.

Follow design guidelines​

Proper use of our logo and buttons will ensure a better user experience and conversion rate. Please visit our Design guidelines for more information and resources.

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.

Live flow​

  1. The PSP completes all checklist items.
  2. The PSP contacts us with test IDs (pspTransactionId, merchantOrderId) in the test environment, showing that all checklist items have been fulfilled.
  3. The PSP contacts us to verify the integration in the production environment:
    • At least one ID 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
Tip

Operational Status Page

We recommend that you subscribe to the Vipps MobilePay Operational Status Page for real-time updates on service availability, incidents, and maintenance.

Last updated on