• Resolved glean47

    (@glean47)


    I’ve tried many things posted online. My donors keep getting this error. I believe I’ll need to look for a new solution if I can’t resolve this.

    stripe.confirmPayment(): the confirmParams.return_url argument is required when using automatic payment methods

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Ginger Coolidge

    (@gscoolidge)

    Hello @glean47,

    Glad you reached out, happy to help.

    Those errors are usually associated with other form log errors, can you send us a few of those please?The error logs are accessed by going to GiveWP > Tools > Logs. When you find one, click on the “eyeball” icon on the right of the log to expand it to view the contents.  After that, copy/paste the complete log into your next reply as well as the top of the form log where it shows the donation information. (Note: a screenshot will not show us enough information. Here’s a screencast on how to get the error log content for us: https://screencast-o-matic.com/watch/c3eD0AVFgVG.

    Thread Starter glean47

    (@glean47)

    I can’t seem to post a screenshot, but this is what I’m seeing repeatedly in the logs:

    Description:
    Invalid Secure Route
    Category:
    Payment Gateway
    Source:
    Payment Gateway
    Date & Time:
    2025-09-29 13:48:24
    Error details:

    {
    "routeSignature": "7a93f90f3fd04c8d727976f4c353578c",
    "signature": {
    "Object Class": "Give\\DonationForms\\Routes\\DonateRouteSignature",
    "\u0000Give\\DonationForms\\Routes\\DonateRouteSignature\u0000signature": "givewp-donate|1758979629",
    "expiration": "1758979629"
    },
    "signatureString": "givewp-donate|1758979629",
    "signatureHash": "7a93f90f3fd04c8d727976f4c353578c",
    "signatureExpiration": "1758979629"
    }

    Plugin Support Ginger Coolidge

    (@gscoolidge)

    Hello,

    Thank you for sending that form log, it’s exactly what we needed!

    The form log error and the error you’re getting at the bottom of the donation form are from caching. The short version is, once you exclude the GiveWP slugs/paths/cookies, etc that should resolve that error and allow donations to process successfully.

    The Longer Version and How To Fix It

    That “Invalid Secure Route” error message is basically saying there isn’t a secure route (like a secure payment token) to assure that the payment will be processed securely. This is 100% caused by caching as the “route” hasn’t been refreshed. How you can verify this is comparing the date/time of the donation to the “expiration” or “signatureExpiration” in your form logs.

    The expiration date/time is in format computers can read called epoch/unix time (1758979629) and translates to September 27, 2025, so it expired 2 days before the donation was attempted and did not refresh itself.

    You can use this website to convert those expiration date numbers to an actual human-readable date: https://www.epochconverter.com/

    Caching is handled differently on various sites and web hosts, and most of them allow for excluding specific URLs or parts of URLs from caching. At the very least, you should exclude the following slugs from caching:

    • /donations/
    • /donation-confirmation/
    • /donor-dashboard/

    Furthermore, the following query strings:

    • give-embed=donor-dashboard
    • giveDonationFormInIframe=1
    • give-route

    Your host or the caching plugin/solution you are using can help with that. Some of them may require what’s called a “wildcard” like /donations/* to capture all subdirectories under the /donations/ folder.

    Note that clearing the cache will not resolve this as it will build up again, and those errors will resume.

    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 provide any tips, and review those we have documented our guide on this topic here in our documentation: https://givewp.com/documentation/resources/caching/

    Let us know how this go after you’ve implemented and tested the above! 🙂

    Thread Starter glean47

    (@glean47)

    Thanks, I have removed all caching for now. Knowing there are logs will help me catch issues in the future.

    Are logs exposed anywhere so I can trigger an automated alert in the event this recurs?

    Plugin Support Ginger Coolidge

    (@gscoolidge)

    Good to hear things are working!

    Currently there isn’t a way to get an automated alert for form logs with a status of “Error”, however, this has been a popular feature request, and the status shows it is In Review in the bug report here:

    https://givewp.featureos.app/p/admin-email-for-failed-payments

    While I do not have an ETA on when it will be included, I’ve added this support ticket link to the internal comments so that you’ll be notified when there’s an update.

    I hope this helps to clarify! I’ll go ahead and close this support ticket now.

    Have a great rest of your day/evening 🙂

    Thread Starter glean47

    (@glean47)

    For technically minded this is exposed in WP database tables.

    select date, JSON_EXTRACT(data,"$.message") as message from wpsp_give_log  
    order by date desc

    The cache blocking issue worked for me! After months trying to work it out with both GiveWP and my host!

Viewing 7 replies - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.