Problem/Motivation
Klarna changes API endpoints to Kustom
Proposed resolution
Update https://github.com/centarro/kco_rest_php to use new API endpoints.
Update composer requirement to use new centarro/kco_rest release.
API changes
New endpoints:
Production: api.kustom.co
Playground: api.playground.kustom.co
How to update your credentials
- Log in to portal.kustom.co (or portal.playground.kustom.co)
- Go to Integrations in the left sidebar
- Select your store from the menu
- Click Generate new to create credentials
- Save your username and password
How to update your API configuration
- Add your new Kustom credentials to your backend set-up/configuration
- Update all references from klarna.com to kustom.co in your codebase
- Verify your checkout is working by doing a test purchase
Important: The URL is kustom.co (not .com)
Applicable services
- Kustom Checkout (API)
- Kustom Order Management (API)
- Kustom Settlement (API)
- Kustom Hosted Payment Page (API)
Read more: Kustom API endpoint switch - FAQ
Comments
Comment #2
oleksandr yushchenko commentedComment #3
jsacksick commentedThe url is passed by the payment gateway plugin. I'm still using this module with Kustom, plus some minor overrides (for the url for example) .
The reason why I haven't backported those changes is I'm unsure whether you could still use Klarna separately or not? And I was also unsure about making changes to this contrib module, or create a new module, with a different name.... Like commerce_kustom_checkout or something...
Comment #4
oleksandr yushchenko commented@jsacksick I can not find anything in payment gateway plugin that passes url. Klarna API URLs used by connector in KlarnaManager service and they are passed from kco_rest_php ConnectorInterface, therefore in my opinion it should be changed in centarro/kco_rest_php in a new major branch v5.x and then we can release a new major 3.x version of this module that will be based on centarro/kco_rest_php 5.x
Introducing new major versions will be safe for existing projects to not update automatically and break payments. In this case any project that uses this module will require to upgrade to a new major version and obtain new Kustom credentials.
Comment #6
jsacksick commentedI'm wondering if we should introduce a new major branch here as well.
Comment #8
jsacksick commented