Invalid email address in payment field

[rdkhunt]

Describe the bug

We are experiencing an issue with one of our forms: "Couldn’t save submission due to errors. Invalid email address."
Please see the attached screenshot for reference.

I have upgraded Formie to the latest version, but the issue persists. The payment integration is set up with Stripe.

I also have another site running Craft CMS 4 with Formie, and that setup is working without any issues. This leads me to believe that the issue may be related to compatibility between the latest version of Formie and Craft CMS 5, or there could be a bug in the Formie plugin.

Can you please investigate this issue and let me know how we can resolve it?

Steps to reproduce

1.Create a payment form with fields for Name, Email Address, Amount, and Payment.
2.Integrate the Payment field with Stripe using the Stripe keys.
3.Now, test the form.

Form settings

• Multi-page form: No
• Submission Method: Ajax or Page Reload - We have tried with both
• Client-side Validation: Yes
• Custom Form Templates: Yes or No

Craft CMS version

5.5.8

Plugin version

3.0.19

Multi-site?

No

Additional context

[engram-design]

Can you check your logs at /storage/logs/formie.log? I don't think this is related to your Email field, it's likely your Billing Address Email field in the Payment field settings
.

[rdkhunt]

I can see this error in /storage/logs/formie.log. 2025-01-24 04:24:16 [ERROR] Couldn’t save submission due to errors - {"payment":["Invalid email address: "]}.

…

On Fri, Jan 24, 2025 at 5:11 PM Josh Crawford ***@***.***> wrote: Can you check your logs at /storage/logs/formie.log? I don't think this is related to your Email field, it's likely your Billing Address Email field in the Payment field settings . — Reply to this email directly, view it on GitHub <#2262 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJKTEGLHYB7CUJEXBFJ63IL2MIRGNAVCNFSM6AAAAABVZPA5BCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJSGMZDGMBQG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[engram-design]

What does your Billing details look like for the field? Is it mapped to the correct field?

[rdkhunt]

You can see that in the screenshot below.

…

On Fri, Jan 24, 2025 at 5:17 PM Josh Crawford ***@***.***> wrote: What does your Billing details look like for the field? Is it mapped to the correct field? — Reply to this email directly, view it on GitHub <#2262 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJKTEGON26TH2BLJZ3HE5AL2MIR3VAVCNFSM6AAAAABVZPA5BCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJSGMZTKMZRGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[rdkhunt]

Do you think this issue is related to the billing details, or could it be something else?

…

On Fri, Jan 24, 2025 at 5:21 PM Rajesh Khunt ***@***.***> wrote: You can see that in the screenshot below. On Fri, Jan 24, 2025 at 5:17 PM Josh Crawford ***@***.***> wrote: > What does your Billing details look like for the field? Is it mapped to > the correct field? > > — > Reply to this email directly, view it on GitHub > <#2262 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BJKTEGON26TH2BLJZ3HE5AL2MIR3VAVCNFSM6AAAAABVZPA5BCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJSGMZTKMZRGU> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[engram-design]

I don't believe the screenshot has attached, as you've replied via email. I do believe it's these values:

In particular, these should've been migrated to a slightly different format in Formie 3, from {field.email} to {field:email}

[engram-design]

I did get a similar email through support (not sure if you), but recommended to check the logged-in status of the user when testing the form, due to mapping "User Email" to the "Email Address" setting for Stripe receipts. This will required a logged-in user to Craft.

[rdkhunt]

I have fixed the email issue. Now, we are observing another issue: [ERROR] Couldn’t save submission due to errors - {"payment":[""]}.

[engram-design]

Indeed, it looks like the front-end JS is not creating the stripePaymentIntentId which is required to send to the server to initiate payment. That process is all done on the front-end with Stripe's hosted JS.

Can you see if there are any JS errors on your front-end when submitting the form?