API version: 2.0
Document version 1.1.1
For examples of requests and responses, see the Postman collection in tools
- Integrate all the API endpoints:
- The merchant correctly handles callbacks, both for successful and unsuccessful payments
- Callback
POST:[callbackPrefix]/v2/payments/{orderId}
- For express checkout only: Shipping details
POST:[shippingDetailsPrefix]/v2/payments/{orderId}/shippingDetails
- For express checkout only: Remove consent
DELETE:[consetRemovalPrefix]/v2/consents/{userId}
- Callback
- Avoid Integration pitfalls
- The Merchant must not rely on
fallback
alone - The Vipps branding must be according to the Vipps design guidelines
- The Merchant must not rely on
- The merchant orders Vipps på Nett.
- Vipps completes customer control (KYC, PEP, AML, etc).
- The merchant receives an email from Vipps saying that they can log in with bankID on portal.vipps.no and retrieve API keys.
- The merchant completes all checklist items.
- The merchant contacts Vipps with test IDs (
orderId
) in the Vipps test environment, showing that all checklist items have been fulfilled.- A complete order ending in
Refund
. - A complete order ending in
Cancel
.
- A complete order ending in
- The merchant receives an email from Vipps saying that the orders are OK.
- The Merchant contacts Vipps to verify the integration in the production environment:
- A complete order ending in
Refund
. - A complete order ending in
Cancel
.
- A complete order ending in
- The Merchant goes live 🎉