- Posts: 7
- Thank you received: 0
Stripe Checkout plugin issue
2 weeks 6 days ago #100000452
by Dasa
Stripe Checkout plugin issue was created by Dasa
-- HikaShop version -- : 6.7.1
-- Joomla version -- : 6.2.0
-- PHP version -- : 8.5
-- Browser(s) name and version -- : Chrome 156.0
Hello, I am using the latest Stripe Checkout plugin. When a payment is successfully completed, the Stripe webhook reaches the site, the payment status changes to 'paid', and the order status updates correctly. However, no order confirmation or serial/ticket email is generated or sent. Looking at the order history, I see 'A payment notification was received with the state paid', but HikaShop does not trigger the notification sequence for automated payments (unlike manual status changes in the backend, which trigger emails successfully). Why does the automated webhook execution bypass the email trigger?
Best regards
Dagmar
-- Joomla version -- : 6.2.0
-- PHP version -- : 8.5
-- Browser(s) name and version -- : Chrome 156.0
Hello, I am using the latest Stripe Checkout plugin. When a payment is successfully completed, the Stripe webhook reaches the site, the payment status changes to 'paid', and the order status updates correctly. However, no order confirmation or serial/ticket email is generated or sent. Looking at the order history, I see 'A payment notification was received with the state paid', but HikaShop does not trigger the notification sequence for automated payments (unlike manual status changes in the backend, which trigger emails successfully). Why does the automated webhook execution bypass the email trigger?
Best regards
Dagmar
Please Log in or Create an account to join the conversation.
2 weeks 6 days ago #100000453
by nicolas
Replied by nicolas on topic Stripe Checkout plugin issue
Hi,
The webhook does trigger the email: on a Joomla 6.2 / HikaShop 6.7.1 test shop with Stripe Checkout 1.5.9 and HikaSerial, a paid Stripe notification confirms the order and sends the customer the "Your order is now confirmed" email, with the serial key in it.
What stops it is a setting of the email itself. In System > Emails, each order email has a "Payment methods" field: when payment methods are selected there, the email is only sent for orders paid with one of them. Stripe Checkout is a new payment method on your shop, so if that field lists your other methods (bank transfer for example) but not Stripe Checkout, the automatic email is skipped for Stripe orders. A status change from the order listing in the backend sends the email you see in its popup without that check, which is why your manual changes still work. I reproduced exactly this: with the email limited to bank transfer, the Stripe notification confirmed the order and assigned the serial, but no email went to the customer, while a manual status change sent it.
To fix it:
1. Go to System > Emails and open "Order status notification".
2. In "Payment methods", either add Stripe Checkout or remove every method (with none selected, the email is sent for all orders). Also check that "Published" is on Yes: an unpublished email is skipped in the same way for automatic notifications. Save.
3. Do the same check for the other order emails you rely on, such as "Order creation notification".
The setting is explained here: www.hikashop.com/support/documentation/2...shop-email-form.html
The serial keys of HikaSerial are added to that same "Order status notification" email, so they will reach your customers again once it is sent. Your next Stripe orders will get the email automatically; for the orders already paid, you can resend it by changing their status from the orders listing with the notification enabled.
If it still does not send after that, open System > Configuration, Main tab, Files, and click "See the report" next to the payment log file: HikaShop writes there the reason when it skips an email (the line starts with "Sending of email order_status_notification skipped because..."). Send us that line and we will look further.
The webhook does trigger the email: on a Joomla 6.2 / HikaShop 6.7.1 test shop with Stripe Checkout 1.5.9 and HikaSerial, a paid Stripe notification confirms the order and sends the customer the "Your order is now confirmed" email, with the serial key in it.
What stops it is a setting of the email itself. In System > Emails, each order email has a "Payment methods" field: when payment methods are selected there, the email is only sent for orders paid with one of them. Stripe Checkout is a new payment method on your shop, so if that field lists your other methods (bank transfer for example) but not Stripe Checkout, the automatic email is skipped for Stripe orders. A status change from the order listing in the backend sends the email you see in its popup without that check, which is why your manual changes still work. I reproduced exactly this: with the email limited to bank transfer, the Stripe notification confirmed the order and assigned the serial, but no email went to the customer, while a manual status change sent it.
To fix it:
1. Go to System > Emails and open "Order status notification".
2. In "Payment methods", either add Stripe Checkout or remove every method (with none selected, the email is sent for all orders). Also check that "Published" is on Yes: an unpublished email is skipped in the same way for automatic notifications. Save.
3. Do the same check for the other order emails you rely on, such as "Order creation notification".
The setting is explained here: www.hikashop.com/support/documentation/2...shop-email-form.html
The serial keys of HikaSerial are added to that same "Order status notification" email, so they will reach your customers again once it is sent. Your next Stripe orders will get the email automatically; for the orders already paid, you can resend it by changing their status from the orders listing with the notification enabled.
If it still does not send after that, open System > Configuration, Main tab, Files, and click "See the report" next to the payment log file: HikaShop writes there the reason when it skips an email (the line starts with "Sending of email order_status_notification skipped because..."). Send us that line and we will look further.
Please Log in or Create an account to join the conversation.
2 weeks 5 days ago #100000454
by Dasa
Replied by Dasa on topic Stripe Checkout plugin issue
Hi, thank you for your reply, unfortunately none of your suggestions were effective.
- The payment methods field in the (published) email template was already empty before. I tried adding all payment methods, and even Stripe Checkout explicitly by name, with no result.
- The log file (with debug mode enabled) only contains the payment session (Payment log file: 11.01.26 10:47:57 - stripecheckout Stripe Checkout session created. Session ID: cs_live_a1Cj6dM5z6ECoTfq5CQQJvJpM8q3K1qh5UcOnUD9GIyRIE1DVCuiBvAyUl).
- The order history only displays the states: created - payment - confirmed.
- The email history shows that no
email was created at all (see the attached screenshot).Code:order_status_notification
- I performed a test order WITHOUT HikaSerial involved (I know there was a bug in a previous version, but it should be fixed in version 6.1.1) – no change.
- I have added Stripe's webhook IP addresses to the whitelist on the server.
Please Log in or Create an account to join the conversation.
2 weeks 5 days ago #100000461
by nicolas
Replied by nicolas on topic Stripe Checkout plugin issue
Hi,
Thank you, these details narrow it down. The order status is saved and the payment line is added to the history, but the email is never created: there is no entry for it in the email log, and no line in HikaShop's log saying that it was skipped. That is what happens when the processing of Stripe's notification stops on a PHP error while the email is being prepared. We reproduced exactly this situation (status confirmed, payment line in the history, no email, nothing in the email log or in HikaShop's log) with an error in the "Order status notification" email.
Since the same email is sent when you change the status in the backend, the code that fails only fails in that situation: Stripe's notification is processed on the frontend, with no logged-in user, at the very start of Joomla's loading, before the page and its template are prepared. The cause is usually a customization of that email (its HTML or preload code in System > Emails) or another plugin that runs when an order is updated or when an email is prepared.
To find out which, we need the error message. The PHP error log of your server will most likely be empty: Joomla catches the error itself and only shows it on its error page, which is returned to Stripe. You can read it in either of these two ways:
1. In your Stripe Dashboard, open Developers > Webhooks (Workbench > Webhooks in the newer dashboard), click your site's endpoint, then the checkout.session.completed event of one of these orders. Stripe shows the response of your site: a 500 error with Joomla's error page, which contains the error message (for example "Call to a member function ... on null"). Copy that response to us.
2. Or, in System > Global Configuration, Logging tab, set "Log Almost Everything" to Yes and make a new test order with Stripe Checkout. Joomla then writes the error with its full stack trace to the file administrator/logs/everything.php, in a line starting with "Uncaught Throwable of type". Send us that entry, then set the option back to No.
The stack trace shows which file and which extension fails, and we can then tell you how to correct it.
Thank you, these details narrow it down. The order status is saved and the payment line is added to the history, but the email is never created: there is no entry for it in the email log, and no line in HikaShop's log saying that it was skipped. That is what happens when the processing of Stripe's notification stops on a PHP error while the email is being prepared. We reproduced exactly this situation (status confirmed, payment line in the history, no email, nothing in the email log or in HikaShop's log) with an error in the "Order status notification" email.
Since the same email is sent when you change the status in the backend, the code that fails only fails in that situation: Stripe's notification is processed on the frontend, with no logged-in user, at the very start of Joomla's loading, before the page and its template are prepared. The cause is usually a customization of that email (its HTML or preload code in System > Emails) or another plugin that runs when an order is updated or when an email is prepared.
To find out which, we need the error message. The PHP error log of your server will most likely be empty: Joomla catches the error itself and only shows it on its error page, which is returned to Stripe. You can read it in either of these two ways:
1. In your Stripe Dashboard, open Developers > Webhooks (Workbench > Webhooks in the newer dashboard), click your site's endpoint, then the checkout.session.completed event of one of these orders. Stripe shows the response of your site: a 500 error with Joomla's error page, which contains the error message (for example "Call to a member function ... on null"). Copy that response to us.
2. Or, in System > Global Configuration, Logging tab, set "Log Almost Everything" to Yes and make a new test order with Stripe Checkout. Joomla then writes the error with its full stack trace to the file administrator/logs/everything.php, in a line starting with "Uncaught Throwable of type". Send us that entry, then set the option back to No.
The stack trace shows which file and which extension fails, and we can then tell you how to correct it.
Please Log in or Create an account to join the conversation.
2 weeks 4 days ago #100000466
by Dasa
Replied by Dasa on topic Stripe Checkout plugin issue
Hi,
First of all, I'm happy to announce that the notifications are now working properly!
Here is the explanation of what was actually happening. The logs revealed a critical error:2026-11-02T10:30:15+00:00 CRITICAL 52.15.183.38 error Uncaught Throwable of type Error thrown with message "Undefined constant "T4\Helper\T4PATH_TPL"". Stack trace: #0 [ROOT]/plugins/system/t4/t4.php(315): T4\Helper\Path::addIncludePath()
After digging through the codebase, I traced the following execution flow:
The Stripe webhook arrives correctly.
HikaShop changes the order status to confirmed.
modifyOrder() passes control to orderClass->modifyOrder().
save() initiates the generation of order_status_notification.
loadOrderNotification() loads the email template and its preload.
The preload triggers onAfterOrderProductsListingDisplay.
HikaSerial responds to the event and creates a view via hikaserial::getLayout().
While creating the view, T4's onHtmlViewAddPath() is executed.
T4 hits the undefined constant T4PATH_TPL.
The fatal error interrupts the email generation before it can be sent.
I checked the JoomlArt forums and found that this issue was already described back in the summer here: www.joomlart.com/forums/d/52705-undefine...4helpert4path-tpl/36 and can be resolved using a DIY patch for the T4 plugin. However, this patch was not included even in the latest plugin update from October 26, 2026, so it's likely to keep causing issues in combination with JoomlArt templates.
It might be worth considering whether errors in external system plugins could be isolated or handled more gracefully so they don't break the entire email notification process.
Anyway, thank you so much for your help and guidance in tracking down this bug!
Best regards
Dagmar
First of all, I'm happy to announce that the notifications are now working properly!
Here is the explanation of what was actually happening. The logs revealed a critical error:2026-11-02T10:30:15+00:00 CRITICAL 52.15.183.38 error Uncaught Throwable of type Error thrown with message "Undefined constant "T4\Helper\T4PATH_TPL"". Stack trace: #0 [ROOT]/plugins/system/t4/t4.php(315): T4\Helper\Path::addIncludePath()
After digging through the codebase, I traced the following execution flow:
The Stripe webhook arrives correctly.
HikaShop changes the order status to confirmed.
modifyOrder() passes control to orderClass->modifyOrder().
save() initiates the generation of order_status_notification.
loadOrderNotification() loads the email template and its preload.
The preload triggers onAfterOrderProductsListingDisplay.
HikaSerial responds to the event and creates a view via hikaserial::getLayout().
While creating the view, T4's onHtmlViewAddPath() is executed.
T4 hits the undefined constant T4PATH_TPL.
The fatal error interrupts the email generation before it can be sent.
I checked the JoomlArt forums and found that this issue was already described back in the summer here: www.joomlart.com/forums/d/52705-undefine...4helpert4path-tpl/36 and can be resolved using a DIY patch for the T4 plugin. However, this patch was not included even in the latest plugin update from October 26, 2026, so it's likely to keep causing issues in combination with JoomlArt templates.
It might be worth considering whether errors in external system plugins could be isolated or handled more gracefully so they don't break the entire email notification process.
Anyway, thank you so much for your help and guidance in tracking down this bug!
Best regards
Dagmar
Please Log in or Create an account to join the conversation.
2 weeks 4 days ago #100000468
by nicolas
Replied by nicolas on topic Stripe Checkout plugin issue
Hi,
Thank you for the follow-up and for the detailed analysis, it is very useful to us.
Your trace matches what we saw: Stripe's notification is processed at the very start of Joomla's loading, before the template is set up, so the T4 system plugin runs its view code before the constant it relies on exists. In the backend, or on a normal page, the template is already loaded, which is why the same email worked when you changed the status manually.
Since the fix is a patch of the T4 plugin, keep in mind that it will be overwritten the next time you update the T4 Framework. After each T4 update, make one test order with Stripe Checkout and check that the confirmation email with the serial arrives; if it does not, apply the patch again until JoomlArt includes the fix. It would also help to tell JoomlArt on their forum topic that the error still happens with their October update, in requests that are processed without a page (payment notifications, cron).
About handling such errors more gracefully: thank you for the suggestion, we followed it. From the next version of HikaShop, an error thrown by another extension while an email is generated no longer stops it: the customer still receives the email with everything that could be generated, and the shop receives a separate email with the error, the order number, the file and line at fault and how it was reached, also written in HikaShop's log. Such a problem then shows at once and points to the extension that must be corrected.
Thank you for the follow-up and for the detailed analysis, it is very useful to us.
Your trace matches what we saw: Stripe's notification is processed at the very start of Joomla's loading, before the template is set up, so the T4 system plugin runs its view code before the constant it relies on exists. In the backend, or on a normal page, the template is already loaded, which is why the same email worked when you changed the status manually.
Since the fix is a patch of the T4 plugin, keep in mind that it will be overwritten the next time you update the T4 Framework. After each T4 update, make one test order with Stripe Checkout and check that the confirmation email with the serial arrives; if it does not, apply the patch again until JoomlArt includes the fix. It would also help to tell JoomlArt on their forum topic that the error still happens with their October update, in requests that are processed without a page (payment notifications, cron).
About handling such errors more gracefully: thank you for the suggestion, we followed it. From the next version of HikaShop, an error thrown by another extension while an email is generated no longer stops it: the customer still receives the email with everything that could be generated, and the shop receives a separate email with the error, the order number, the file and line at fault and how it was reached, also written in HikaShop's log. Such a problem then shows at once and points to the extension that must be corrected.
The following user(s) said Thank You: Dasa
Please Log in or Create an account to join the conversation.
Time to create page: 0.065 seconds