Home›Support›English Support›[Waiting for user feedback] Error activating Pay-as-you-go : "An error occurred when confirming the subscription : id should be...
[Waiting for user feedback] Error activating Pay-as-you-go : "An error occurred when confirming the subscription : id should be...
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I am trying to activate the Pay-as-you-go service in WPML.
I had previously activated it successfully, but after redeploying the production website and renewing the WPML key, I can no longer activate the feature.
Under "Translation Management > Translation Tools > Transfer credits to wpml.org" the following message apears : "Cannot withdraw credits to wpml.org, please contact support"
Our WordPress installation is based on Bedrock and managed via Composer, so plugin updates are not performed via the admin UI but through our dependency management workflow. The site runs inside a Docker container, deployed on a Kubernetes infrastructure. The site key for each environment is managed using the 'OTGS_INSTALLER_SITE_KEY_WPML' environment variable
Automatic Translation account id :
100a3d4c-57d4-4265-9aaa-e652055ad256#1JkYCrEQwl0t3klLx1QuPAtt
Symptoms:
I received an error message when trying to activate Pay-as-you-go: "An error occurred when confirming the subscription: id should be a string representing the ID of an API resource."
Questions:
Why am I receiving an error when trying to activate Pay-as-you-go?
- Visit your WPML account: https://wpml.org/account/sites/
- Delete the existing key for your site
- In your WordPress dashboard, go to Plugins → Add New → Commercial tab
- Click “Register WPML”
- Then click “Get a key for this site”
- Copy the newly generated site key
- Return to the Commercial tab and paste the key to register your site
If not, please try these steps and upgrade to the latest version of WPML (4.7.6) after taking a full site backup (mandatory).
After completing these steps, please check if the issue is resolved.