-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MobilePay Reporting API going out of support #407
Comments
I can't quite figure out how to get access to their test environment 🤔 |
I believe that we are using the "MobilePay MyShop" product, which isn't really intended to have any sort of integration. So, I unfortunately don't think there is a test environment for it. I also found this in their documentation:
And this:
So the in general what I'm hearing is: The integration breaks next week and you can't test until after it has broken. |
Yup, that's how I read it at first, I just figured that really wasn't the case, but it seems it is then... |
Docs are https://developer.vippsmobilepay.com/docs/APIs/report-api/ and then use the Norwegian test server at |
I've been in contact with MobilePay about getting new API-keys. I ended up having to send an email, so I'm waiting for reply now. |
We've gotten a confirmation from MobilePay, that they do not provide API-keys to regular sellers (What we are) anymore, only registered bookkeeping software can be accepted into their 'accounting partner'-programme, and receive API-keys. I've written an email to get the Stregsystem registered as a bookkeeping software and possibly become an accounting partner, but I don't expect them to actually do so. Even if they do, there's probably a stark fee/membership. We'd have to be our own accounting partner in that sense too. We are currently looking into different payment gateway services, to replace the direct MobilePay reporting access, with an actual payment gateway. This will be more costly than before, and will require a whole new implementation. Don't expect services to be restored soon, make use of the manual refill opportunities provided at the institute in the meantime |
It seems like, it will be possible to have our system registered as a bookkeeping software with Vipps/MobilePay! We're still waiting for confirmation, but hopefully it succeeds. As soon as the API-key has been acquired it will be possible to continue the implementation #416 |
We've got keys baby! Expect to see more updates in #416 |
I'm planning on deploying later today, then we should know by tomorrow whether it works or not in prod |
MobilePay is in the midst of doing a transition to their new Vipps MobilePay platform. This means that the current implementation for fetching transactions will stop working come ~mid-2024.
The migration should in theory be fairly straightforward, but since we are still on the already deprecated V1 of the original API it may be more substantial, as the migration guides assume that we are on V3.
https://developer.mobilepay.dk/docs/reporting/transition-to-one-platform
Migration information: https://developer.vippsmobilepay.com/docs/mp-migration-guide/reporting/
Documentation for the replacement API: https://developer.vippsmobilepay.com/docs/APIs/report-api/
The text was updated successfully, but these errors were encountered: