Return parameter fault

Hello @chihi108 ,

Glad you reached out, happy to help. That error is 99% attributed to caching and scripting compress/deferment. I can see the scripting console errors in the browsing when viewing your donations page here: https://www.loom.com/i/104ff1315d1748b29068559c2daf4b9a

Below are two recommendations – JavaScript exclusions and Caching recommendations.

JAVASCRIPT:
GiveWP does not function well when its JavaScript is optimized further by a 3rd-party plugin or service. Here is a list of JavaScript files that should be excluded form optimization in LiteSpeed and/or any other plugin that might do the same:

Core files:
give.js
give-donation-summary.js
donor-dashboards-app.js

Next, here are the caching recommendations of slugs to exclude at a minimum in your LiteSpeed Cache settings. 
/donations/
/donation-confirmation/
/donor-dashboard/

Also, the following query strings:
give-embed=donor-dashboard
giveDonationFormInIframe=1
givewp-route=donation-form-view
givewp-route
give-listener=stripe

Your web host or the caching plugin/solution you are using can help with that. If there is server-side caching like varnish and some Cloudflare/CDN components, you web host can assist there as well as the same exclusions would need to be applied. 

Some of them may require what’s called a “wildcard” like /donations/* to capture all subdirectories under the /donations/ folder.

Cookies:

We also use two cookies:

• The give_nl cookie provides email access to donors to view their donation history on your site.

• The wp-give_session_* cookie is to maintain the donor session during the donation process.

While fine-tuning cache falls outside the scope of the support we’re able to provide, your success with online donations is our number one priority, and we’re happy to assist with recommendations whenever possible. We have more details regarding caching here in our docs section:
https://givewp.com/documentation/resources/caching/

Let us know how things go after implementing and testing the above! 👍