Assistance Required with Forminator and Stripe Payment Field Issue

Hi @lspr

I hope you are doing well today.

Recently, we updated the Forminator and integrated the Stripe Restricted key and that was implemented to enhance the security.

Please follow our guide here to re-connect your Stripe:
https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#connect-to-stripe

Kind Regards,
Kris

Thank you for your response and for providing the link to reconnect Stripe. However, the issue we are experiencing is unrelated to the Stripe Restricted key integration. We implemented the Stripe Restricted key some time ago, and it has been functioning correctly without any issues since then.

Based on my investigation and communication with Stripe’s support team, it seems the issue may be related to a recent update involving deprecating a previous form field and introducing a new one. I am unsure if this is affecting Forminator’s functionality, but I believe it could be worth reviewing on your end.

The guide you provided has already been followed, and since the payment fields were working well until recently, I suspect the root cause may lie elsewhere. Could you please investigate further and confirm if the recent changes from Stripe are impacting the Forminator plugin?

I look forward to your feedback and any additional assistance you can provide.

Yet to get any response on this!

This issue is directly affecting our ability to process bookings, which is impacting our business operations.

As mentioned earlier, the problem does not appear to be related to the Stripe Restricted key but may be linked to a recent update Stripe made on old form fields being deprecated and introducing new ones. We urgently need your team to investigate this from your end and provide a resolution or guidance as soon as possible.

Your prompt assistance in resolving this matter is highly appreciated.

It’s been over 24 hours, and we still haven’t received a response or solution to the issue with our booking forms. This is very disappointing, as it’s costing us business.

After further troubleshooting on my end, I’ve noticed the problem started after the last plugin update on January 22nd. Before that, payments were being processed seamlessly through Stripe on the booking forms. This suggests the issue might be linked to changes introduced in that update.

We urgently need a resolution to restore functionality and avoid further business losses.

I am running into the same problem. Once I’ve migrated to the new stripe integration, the new field will no longer display properly on the users end.

It does display in test mode, but vanishes as soon as it’s moved to live mode.

It looks like it “tries” to load but as it completes, it vanishes.

Help with this would be appreciated, and if it can’t be found, the old integration field should be left available.

Also @lspr if in emergency, I would remove all “visibility” rules from this form.

If you’re having the same problem as me, this should make it display and start processing CC for you.

Kind of makes the form feel more amateur but atleast it will work while they fix this.

@joelo246 we are experiencing the same problem and it’s very concerning how unsupportive @wpmudevsupport13 has been these past few days.

They need to fix whatever bug it is ASAP

Hi @lspr,

I hope you are doing well today!

We had a bug which has been fixed with the new version of the Forminator and it will be released soon, as “Stripe?Field doesn’t load when Visibility Condition is set for?Stripe?Field with Live Mode”. Please try removing if any Visibility Condition is set for the Stripe Field and check again.

If this does not help, please share an export of the form with us, so that we can check further.

You can find more info on how to export the form here : https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#import-export

After exporting, please share the file contents with us using the free services such as Google Drive (public folder), https://pastebin.com or https://justpaste.it

Please always make sure to use such services to share the code and don’t post the code here directly as it will most likely be unusable.

Kind regards,
Zafer

Could you please let us know approximately when the new version will be released? This is quite urgent for us as we’re currently facing a difficult situation:

When we remove the visibility conditions as suggested, it creates a new problem – users who choose the invoice payment option can’t submit the form at all, even though they aren’t using the Stripe payment field. We need both payment options (invoice and credit card) to work properly for our clients.

Is there perhaps a temporary workaround we could use until the new version is released that would allow both payment methods to function?

find the link to the form export below:
https://justpaste.it/j5v44

Hi @lspr

Thank you for the form

I imported it on the current Free version and found the issue might be related to PayPal field

It has a conditional “Payment type” but there isn’t “PayPal” in the payment type field:

https://monosnap.com/file/xLQ4sPZI2xxFSHbGGCuyHWneAiCr6K

Can you try the following:

– Remove PayPal field
– Edit the “Payment type” add the PayPal option again
– Enter the PayPal field back and configure it.
– Test the form

With the above steps the submission worked well https://monosnap.com/file/rJEcvCf1SwQT1SvDCsSANpCss2w4SH

Let us know the result you got.
Best Regards
Patrick Freitas

Hi Patrick,

Thank you for your suggestion, but we’ve already tested this solution. The issue specifically occurs in live mode, not test mode – which is probably why it worked in your test. This was previously identified by your team as a known bug that will be fixed in the upcoming release.

Our main concern right now is timing – when will the new version with this fix be released? This is affecting our business operations as clients cannot make card payments on our forms.

Could you please give us an estimated release date for the version that contains this fix?

Hi @lspr

As mentioned above this was already fixed in version 1.39. Are you using an updated version of Forminator?

Kind Regards,
Kris

The forms are now functioning well, from my dashboard I can see the new version was released yesterday.

Hi again @lspr,

We are glad to hear that the issue has been resolved and marking this thread accordingly. Please let us know in case you need further help.

Kind regards,
Zafer