Frequently asked questions

NOTICE

All new integrations should use the ePayment API. See the eCom to ePayment migration guide for help migrating older integrations.

Applicable to Vipps.

Here are the eCom API Frequently Asked Questions (FAQ). See the eCom API guide for all the details.

For more general information and questions, please check in the Knowledge base.

Users and payments

I have initiated an order but I can't find it

If you have multiple sales units: Make sure you use the correct API keys, and that you are not attempting to use one sales unit's API keys to retrieve an order made by a different sales unit.

Have you, or the ecommerce solution you are using, successfully implemented GET:/ecomm/v2/payments/{orderId}/details? This is a requirement, see the API checklist.

In case the callback fails, you will not automatically receive notification of order status. The solution is to check with GET:/ecomm/v2/payments/{orderId}/details.

See: API endpoints.

Other questions

What functionality is included in the eCom API, but not the PSP API?

The PSP API provides tokens that a PSP can use to charge a Vipps user's card. To put it simply, it is a "card token lookup service". The payment is completed by the PSP, who sends an update to Vipps about the success or failure.

The eCom API has some functionality that is not available in the PSP API:

1. Retry functionality: If the user attempts to pay with a card that is declined, the user can retry with a different card, while still in the same payment process. This results in a higher success rater for payments. The PSP API does not have this functionality, as it is the PSP, not Vipps, that make the charge.
2. Express Checkout (Vipps Hurtigkasse) is only available in the eCom API.
3. Profile sharing: The eCom API offers the possibility for merchants to ask for the user's profile information as part of the payment flow: name, address, email, phone number, birthdate, etc.
4. When using the eCom API, Vipps handles soft-declines, 3-D Secure, BankID, etc. There is nothing a merchant needs to do. This gives a consistent user experience and a very high completion rate.

What does the status suffix at the fallBack URL mean?

Please disregard it. The status suffix was phased out several years ago, and is no longer documented. But, since some merchants still depend on in, it still provided.