The root cause for this incident was due to old api endpoints that were not properly updated.
This was resolved on 2019-01-17 by updating the api endpoints and publishing a hotfix to the service.
All users who tried to subscribe during the incident have gotten their subscriptions updated so they can use the service as intended.