Hi! 😁
We are now implementing two new checkout integrations for a customer and have started the onboarding process using this scheme: https://vippsbedrift.no/signup/vippspanett/ & we are happy to see that the keys is now to be found at portal.vipps.no instead of the old interface which we found hard to work with.
So the request has been approved, but some API keys is still missing.
1st:
We can see the Vipps-eCommerce-Services product in the list which has:
- Merhcant ID
- Client ID
- Client Secret
- Primary key
- Secondary key
But, we do not have access to the auth token API and we can't find the Primary Key for the auth api anywhere. 😱 (Edit: I refer to the JWT access token, see image in the first comment below)
This is also the case for previous integrations where we already have the codes. All codes and products is displayed in the list except for the Primary Key for the auth / token service. Without this code it is not possible to use any endpoints, because you cant generate an access token without it.
For the companies we previously integrated with vipps we do at least find the eCommerce-Classic-Services in the list which is good.
In summary:
At the onboarding process you should not only give access to the API V2, but also the Auth API and API V1 by default / always.
Why Auth API?
API V2 can't be used without the Auth API. (Edit: Here I ment the JWT Access token. It looks like it is supposed to be available on the portal some where, but I cant find it.)
Why API V1 (classic)?
Checkout with V2 REQUIRES a BROWSER and that the customer leaves the shop / app.
This means that it will not work with certain software where a web browser is not intended (as in our use case). (Edit: I now see that this is deprecated, ref. screenshot in first comment. That is not good news for us, so I created a new issue on it. -> #78)
When using API V1 (classic) this is not a problem, but with V2 it is a problem.
For example - We use it for a "Self service POS". and don't want to add a web-browser to it (neither a popup / iframe).
I also send this by e-mail to [email protected]