Chapters

19 Chapters | 1:49:02 |

01

Meet LemonSqueezy - Your Merchant of Record.

6:30
02

Checkout Products

5:55
03

Start the Course Project App

4:26
04

Checkout API Request

7:17
05

Dynamic Data

6:29
06

Multiple Products Purchase

4:13
07

Complete the Checkout

4:31
08

Centralize LemonSqueezy Business Logic

4:58
09

Listening to Webhooks

3:45
10

Ngrok Tunnels

4:19
11

Implementing the Webhook Request Parser

4:17
12

Implementing the Webhook Consumer

8:10
13

Writing an Integrational Test for Webhooks

7:16
14

Rendering LemonSqueezy Orders on the Account Page

7:29
15

Enhancing API Error Handling

4:45
16

LemonSqueezy Checkout Overlay

5:48
17

Embedding the LemonSqueezy Checkout Overlay

6:51
18

Listening to LemonSqueezy Javascript Events

7:29
19

Improving Javascript Event Security

4:35

> Symfony > Lemon Squeezy Payment Processor

Buy Access to Course Buy Access

14.

Rendering LemonSqueezy Orders on the Account Page

|

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Previous Challenge

Next Challenge

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Login or Register to check out the script

8 Comments

Sort By

Login or Register to join the conversation

Francois 15 days ago

I have a problem in the listOrders method in LemonSqueezyApi. The LsCustomerId of the user is not set. Where should it be set?

|

Victor SFCASTS Francois 15 days ago

Hey Francois,

We're setting that lsCustomerId in the LemonSqueezyWebhookConsumer, see this specific code block: https://symfonycasts.com/screencast/lemon-squeezy/webhook-consumer#codeblock-607e352f6a . Basically, we sync that via the webhook. First of all, make sure the webhook contains user_id so that on our side we could fetch the related User object for the received webhook. Make sure that the user ID didn't change in the DB (because maybe you reload the fixtures that in turn incremented IDs?). If we have user ID, and was able to find the related User in the DB - we will set LS customer ID from the webhook on it. But this requires also ngrok tunnel working, otherwise webhook can't just reach your localhost.

Cheers!

1 |

Victor SFCASTS Francois 15 days ago edited

Hey @Brontie, could you help to figure out where that lsCustomerId should be set, please?

|

Brontie Victor 15 days ago edited

Assuming you mean in this chapter’s flow, lsCustomerId gets set when you assign a Lemon Squeezy customer to your Symfony user after a successful checkout. That happens outside listOrders(): the site needs to store the Lemon Squeezy customer ID on your User entity when the customer is created or matched, so later listOrders() can use it to fetch the canonical Lemon Squeezy customer record.

The important part is that listOrders() only reads $user->getLsCustomerId(); it doesn’t create it. If that field is null, the method intentionally returns an empty array, which is why the orders section shows “No orders yet” for unlinked users.

$lsCustomerId = $user->getLsCustomerId();

if (!$lsCustomerId) {
    return [];
}

Tip: don’t try to use the user’s email as the source of truth here — the chapter hardens this specifically so the lookup depends on the Lemon Squeezy customer record, not an editable site email.

Sources:

| |

Victor SFCASTS Brontie 15 days ago

OK, but where before we set that lsCustomerId, it seems that it happened not in this chapter. How and where that lsCustomerId is set on the User object?

|

Brontie Victor 15 days ago edited

Assuming you mean in this codebase, lsCustomerId is not set inside listOrders() at all — it’s stored on the User when your app first links that user to a Lemon Squeezy customer. In the flow from this chapter, that linkage must already exist from an earlier step or another part of the app: once you have the Lemon Squeezy customer ID, you persist it on the User entity and save it to the database. listOrders() then relies on $user->getLsCustomerId() to decide whether it can safely look up orders. If that field is missing, the method correctly returns [], because there’s no secure way to know which Lemon Squeezy customer belongs to that user.

$lsCustomerId = $user->getLsCustomerId();
if (!$lsCustomerId) {
    return [];
}

Common gotcha: if you’re seeing null here, the issue is usually that the user was never linked to a Lemon Squeezy customer in your database, not that listOrders() is broken.

Sources:

| |

Francois Brontie 14 days ago

Ok, here's what Claude said about this topic in the finish project of this course.

LsCustomerId is set in two places:

Webhook consumer: src/RemoteEvent/LemonSqueezyWebhookConsumer.php:45-46. When Lemon Squeezy sends an order_created webhook, handleOrderCreatedEvent() reads data.attributes.customer_id from the payload and calls $user->setLsCustomerId(). It finds the user through meta.custom_data.user_id, which is the custom data passed when the checkout URL is created. This is the main, trustworthy path, because the request comes from Lemon Squeezy.
Checkout handler: src/Controller/OrderController.php:92-93. The app_order_checkout_handle route (POST /checkout/handle) takes lsCustomerId from the request body and saves it on the current user. It first checks that the posted userId matches the logged-in user. The front end probably calls it from the Lemon Squeezy overlay's checkout-success event.

You probably missed them because User.php only has the plain getter and setter. The setting happens in the webhook consumer and the controller, not in the entity.

The second path has a weakness. lsCustomerId comes straight from the client, so a logged-in user could post any customer ID. listOrders would then fetch another customer's orders. The ls_customer_id column also has a unique index, so a duplicate would cause an error. If the webhook already covers this, I'd drop or harden the controller endpoint. For example, it could verify the ID through the API (retrieveCustomer) before saving it. Do you want me to make that change?

At this stage of the course, it seems that the checkout handler in the order controller does not set LsCustomerId. So, it must be set in the webhook consumer. BUT, in my tutorial code (currently being updated at this very course), I have ordered several items and the LsCustomerId entry in user is till not set.

|

Victor SFCASTS Francois 14 days ago

Hey Francois,

Have you seen my comment: https://symfonycasts.com/screencast/lemon-squeezy/list-orders#comment-34335

So yes, Claude is right, and that LS customer ID should be set in the LemonSqueezyWebhookConsumer. So, make sure you have the ngrok tunnel started (keep in mind that when you stop and start it again - the URL is most probably changed, so you have to change it in the LemonSqueezy dashboard as well otherwise it won't be able to reach your server, but you should see it in logs there). Then make sure that that webhook endpoint in your app returns 200 status code and not fatal errors during that process, otherwise the LS customer ID saving may actually never happen. Ideally, use ngrok HTTP inspector to see what exactly data you receive and what was your response, basically I would recommend to rewatch previous chapter: https://symfonycasts.com/screencast/lemon-squeezy/webhook-consumer .

So, in short, you need to debug that spot around the setLsCustomerId() call in webhook parser: if it was reached by LS webhook and what exactly data you have there to realize why it waas not set, maybe you're mossing user_id in custom webhook metadata, or it mismatch your local user ID, or are there any fatal error happened during that process.

I hope that helps!

Cheers!

|

Symfony 7.2

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=8.2",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "doctrine/dbal": "^3", // 3.9.4
        "doctrine/doctrine-bundle": "^2.13", // 2.13.2
        "doctrine/doctrine-migrations-bundle": "^3.4", // 3.4.1
        "doctrine/orm": "^3.3", // 3.3.2
        "symfony/asset": "7.2.*", // v7.2.0
        "symfony/asset-mapper": "7.2.*", // v7.2.3
        "symfony/console": "7.2.*", // v7.2.1
        "symfony/dotenv": "7.2.*", // v7.2.0
        "symfony/flex": "^2", // v2.5.0
        "symfony/form": "7.2.*", // v7.2.4
        "symfony/framework-bundle": "7.2.*", // v7.2.4
        "symfony/http-client": "7.2.*", // v7.2.4
        "symfony/runtime": "7.2.*", // v7.2.3
        "symfony/security-bundle": "7.2.*", // v7.2.3
        "symfony/stimulus-bundle": "^2.22", // v2.23.0
        "symfony/twig-bundle": "7.2.*", // v7.2.0
        "symfony/validator": "7.2.*", // v7.2.4
        "symfony/webhook": "7.2.*", // v7.2.0
        "symfony/yaml": "7.2.*", // v7.2.3
        "symfonycasts/tailwind-bundle": "^0.7.1", // v0.7.1
        "twig/extra-bundle": "^2.12|^3.0", // v3.20.0
        "twig/twig": "^2.12|^3.0" // v3.20.0
    },
    "require-dev": {
        "doctrine/doctrine-fixtures-bundle": "^4.0", // 4.0.0
        "phpunit/phpunit": "^9.5", // 9.6.22
        "symfony/browser-kit": "7.2.*", // v7.2.0
        "symfony/css-selector": "7.2.*", // v7.2.0
        "symfony/maker-bundle": "^1.62", // v1.62.1
        "symfony/phpunit-bridge": "^7.2", // v7.2.0
        "symfony/stopwatch": "7.2.*", // v7.2.4
        "symfony/web-profiler-bundle": "7.2.*", // v7.2.4
        "zenstruck/foundry": "*" // v2.3.8
    }
}

Previous Challenge

Next Challenge