Messages

Hello,

It looks like the manual upgrade may not have been completed correctly. Did you see any errors when running the SQL upgrade? Also, please confirm that the database table prefix was changed correctly.

In the admin panel, you should see the same forms and fields for each form under Design > Form Manager. Please compare your setup with the demo here: https://www.abantecart.com/shopping-cart-demo

Hello.
The error simply means your mail server (SMTP) is rejecting the credentials and/or the host/port combination, so authentication is failing.

The fact that you still receive the test email does not mean SMTP authentication is working. On shared hosting, this is most likely caused by the hosting mail server falling back to local delivery, especially when the message is sent to an email address on the same domain as the store.

To resolve this, you need to contact your hosting/email provider and ask them for the correct, fully working SMTP settings

 For AbanteCart 1.3.2, the correct default Stripe extension version is 1.1.1. Please also note that there are third-party Stripe extensions in the marketplace, and their compatibility may vary.

Also, AbanteCart 1.3.2 is very outdated. The latest in the 1.3 branch is 1.3.4, and the current stable release is 1.4.3, which includes a new template, support for newer PHP versions, and improved security.

I'm not sure what you mean by 'any settings and programming that will add sting in.' Could you please clarify what you are referring to?

Hello.
What is your Mail Protocol in setting? https://abantecart.atlassian.net/wiki/spaces/AD/pages/7372837/Mail+Settings

Hello.

At the moment, there is no quick fix available. The developers are currently very busy with an ongoing project and will get back to this issue later on.

Thank you for your patience.

Hello.
It looks like an upgrade was started but the database was not fully upgraded. The error clearly shows missing core tables (*_field_groups and related tables), which are required for customer forms, login, and checkout to work.

This usually happens when an upgrade process is interrupted or only partially completed, leaving the database schema incomplete.

The safest solution is to restore a full database backup from before the upgrade attempt, then run the upgrade again manually and make sure it completes without errors. Please follow the manual upgrade instructions here https://abantecart.atlassian.net/wiki/spaces/AD/pages/5275676/Upgrade+manually

Hello.
The most important point in your case is actually the current workflow. Collecting card details at checkout and then manually entering them into Stripe later is not safe and not PCI-DSS compliant, even if the data is handled carefully.

From that perspective alone, moving to the official Stripe Payment extension is the correct and safer choice.The Stripe Payment extension ensures that Card data is handled by Stripe, not your server

Hello.
Try disabling ModSecurity and check AbanteCart + webserver logs for the blocked request

Apparently after spending a great deal of more time with Stripe support it is your ABANTECART CONNECT settings that is causing this result.

Hello. Thank you for the update. It would be helpful if Stripe support could indicate which setting is involved, as we do not see where it can be controlled.

I wonder if it has something to do with Link?

Disable it temporarily to check whether it's the cause.

Hello.
Regarding the question about her previous Stripe account before using Stripe Connect, we can't confirm whether anything old remains on that account. That would need to be checked directly with Stripe Support.

For the other points, when the merchant connects their account through the extension, nothing additional is normally required. The only exception is for certain payment methods such as mobile payments, which do require one webhook to be created manually by the merchant.

To complete the webhook setup for mobile payments (to send a success confirmation), here are the steps:
1. Open the Stripe Dashboard and go to Developers.
2. Select Add Endpoint.
3. Enter the HTTPS URL of your webhook endpoint in the Endpoint URL field.
4. Choose Select event to listen to: payment_intent.succeeded.
5. Click Add endpoint.
6. After the endpoint is created, click Reveal Signing Secret, then copy that value and save it in the Stripe Extension Additional Settings section.

Hello.
The payment methods are configured by the merchant through the extension settings. On our side, we can see that all bank-related payment options are currently disabled.

Could you please confirm whether your Stripe extension code is unmodified, and that you have cleared the AbanteCart cache manually after making the settings changes?

Which account ID are you asking for?

Stripe account id

Hello.
Please send the account ID. As payment-connected accounts are not restricted, they should be configurable through the API (configuration from extension).

Thanks for sharing your solution.