problem with Paddle


May 11th, 2022 01:04 PM


am facing this problem guys:


as I search here, I see that many users face this problem with Paddle.

1st my domain got approved by the Paddle team

& am sure that the .env details are correct like:


also plans id is 100% correct lastly SMTP is there and working.

I am waiting for your help guys.


May 11th, 2022 03:03 PM


Did you create a 'Subscription Plan' in Paddle rather than a single charge product?

Also make sure that the 'Subscription Plan' ID that you've created is correctly defined as described here:




May 12th, 2022 03:08 AM


I was only able to get this error when using the Sandbox details with PADDLE_ENV=live.

So I could suggest making sure that the vendor ID and the paddle auth code are the live ones from and not


May 12th, 2022 06:34 AM

not fixed yet , i tried :

PADDLE_ENV=live & PADDLE_ENV=true & PADDLE_ENV=sandbox

same problem in all cases


May 12th, 2022 07:08 AM

Have you updated your plan ids with ids from your account as well? When going live every aspect of billing should come from your account.

As long as PADDLE_ENV is not set to sandbox, your Paddle environment will be set to production. You can check verify this by opening your developer console in your browser and typing Paddle.Environment.get() and it should print out production.


May 12th, 2022 07:22 AM

hey @thinkverse , yes i worked directly with and I replace ids correctly.

yep the cmmd showing it's: production


May 12th, 2022 08:02 AM

I've just tested this out on a fresh new install and if I do the following it works as expected:

  • set the PADDLE_VENDOR_ID to the one from
  • set the PADDLE_VENDOR_AUTH_CODE matches the one from
  • the product id is correctly defined in the Voyager admin panel

Another thing you can try is to get in touch with Paddle and make sure that your account has been validated as described here:


May 12th, 2022 08:04 AM

If you can, I'd test with Paddles' basic checkout to see if the issue persists. Fill that in with your plan id, and make sure that Paddle.Setup has been called as well. Easiest thing to do is add that in your plans views.

<a href="#!" class="paddle_button" data-product="12345">Buy Now!</a>

Then if the issue persists then its something on Paddles' end and I recommend contacting their support and asking, since if the vendor id is correct and the plan id is correct there shouldn't be an issue. All Wave does is call Paddle.Setup() and which is described in their documentation on overlay checkouts.