PLATFORM

  • Tails

    Create websites with TailwindCSS

  • Blocks

    Design blocks for your website

  • Wave

    Start building the next great SAAS

  • Pines

    Alpine & Tailwind UI Library

  • Auth

    Plug'n Play Authentication for Laravel

  • Designer comingsoon

    Create website designs with AI

  • DevBlog comingsoon

    Blog platform for developers

  • Static

    Build a simple static website

  • SaaS Adventure

    21-day program to build a SAAS

COMMUNITY
MORE
Question By

SailorEudes

Unsolved
Back to All Questions

Wave Paddle problem

sailoreudes ・

Apr 25th, 2022 05:27 AM

Hello,

I had asked the same question the other time, and I double-checked all the documentation regarding paddle payments.

I have also configured everything as shown on the documentation, but I am encountering this error:

Sans titre 1.png

I also checked my smtp info well...

Report
DigitalOcean Laravel News Genesis
thinkverse ・

Apr 25th, 2022 05:52 AM

Make sure your plan IDs match and your Paddle keys are correct.

Highlighting which IDs should match.

Report
sailoreudes ・

Apr 25th, 2022 06:23 AM

Are correct...

Report
thinkverse ・

Apr 25th, 2022 06:39 AM

Could the Plan ID possibly start with a 0 or anything that could be removed when using parseInt? Wave uses parseInt in the checkout function, so something could've been parsed out. I recommend checking the data-plan attribute on each Get Started button on your register page, and running the ID through parseInt to see if something gets removed.

Report
sailoreudes ・

Apr 25th, 2022 06:42 AM

Sans titre 1.png Above, my plan ids

The data plan of the buttons are well equivalent to the data plans of Paddle...

I don't see how to do it...

Report
bobbyiliev ・

Apr 25th, 2022 06:51 AM

Hi there,

Did you also specify the PADDLE_VENDOR_ID in your .env file as described here:

Also if you've done so, try clearing your config cache using php artisan config:clear.

Report
thinkverse ・

Apr 25th, 2022 07:14 AM

On that, did you set your PADDLE_ENV to the correct one? sandbox when using your sandbox keys and IDs, and live when using the live keys and IDs.

Report
sailoreudes ・

Apr 26th, 2022 05:58 AM

Hello,

I have already tried all your solutions

Report
bobbyiliev ・

Apr 27th, 2022 04:30 AM

The error that you are getting is from Paddle itself and to build up on what @thinkverse mentioned, this discussion here also suggests that this is a problem with sandbox vs live keys and IDs.

Can you verify that you are indeed using the correct keys with the correct PADDLE_ENV?

Report
sailoreudes ・

Apr 27th, 2022 01:07 PM

Everything is good on the api side, so I decided to put the system in public and in "production" version with these parameters:

PADDLE_VENDOR_ID="144*******"

PADDLE_VENDOR_AUTH_CODE="45a**************"

PADDLE_ENV="live"

But nothing works.

Look on your side: https://foxpress.fr

Thanks !

Report
thinkverse ・

Apr 27th, 2022 03:25 PM

Has your domain been whitelisted and approved by Paddle? That is one of the steps you need to do when moving to production.

They have a section about domain approval under the account verification help section.

Report
bobbyiliev ・

May 12th, 2022 03:03 AM

Hey @SailorEudes,

Did you manage to get this to work? I've not been able to replicate this on my side just yet.

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 http://vendors.paddle.com/ and not http://vendors-sandbox.paddle.com/.

Report