CookieBot + Easy Digital Downloads + Stripe -> Stripe not defined

  • Resolved Marco van Wieren

    (@wpo365)


    3 weeks ago

    Hi

    I ended up – after testing several others – with Cookiebot, because it was the easiest to configure and connect with GTM. I was pretty happy, until a customer wrote me that they couldn’t complete a credit card transaction. They received the message (JavaScript alert) “Stripe not defined”. I tested this and was able to reproduce this behavior. Only if I would allow all cookies or a selection of all but the marketing cookies, I was able to progress. I checked the dashboard and both stripe cookies appeared to be marked as “Necessary”.

    Now I am not sure how to continue and disabled the plugin for the moment.

    Thanks!

    PS The website is basically build around Easy Digital Downloads (see https://www.ads-software.com/plugins/easy-digital-downloads/) and sells digital downloads (plugins for WordPress).

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support hannausercentrics

    (@hannausercentrics)

    Hi @wpo365 ,
    Thank you for reaching out and we’re glad to know you found Cookiebot easy to configure and connect with Google Tag Manager!

    From your description, it sounds like the Stripe integration is being unintentionally blocked due to the way the Stripe cookie is categorized. Although you’ve marked Stripe-related cookies as “Necessary,” one of the Stripe cookies – named “1” – has been automatically categorized under “Preferences” by Cookiebot. 

    To resolve this, you’ll need to reassign this cookie under the “Necessary” category to ensure that essential payment functionality isn’t blocked. Once you’ve made this change, please run a fresh scan to update Cookiebot’s settings. This should help ensure that Stripe functions correctly without requiring users to allow all cookies.

    Alternatively, if you continue to encounter issues, you may consider disabling automatic cookie blocking and using manual markup for elements that involve non-essential tracking. This approach allows more control over what is blocked or allowed on your site. 

    You can find guidance on how to manually mark up these elements here: Manual Cookie Blocking Guide.

    If the payment container still doesn’t work after the scan, please open a support case for further troubleshooting. This will provide a better platform to address the issue.

    Thread Starter Marco van Wieren

    (@wpo365)

    Hi

    Thank you for your reply! I was able to find the cookie, but not how I can order a rescan. Can you please guide me?

    Thanks!

    -Marco

    Plugin Support hannausercentrics

    (@hannausercentrics)

    Hello,
    Thank you for reaching out!
    We’ve initiated a new scan, which has completed successfully. Upon review, it appears that Stripe cookies have been reclassified as necessary.

    If you continue to experience any issues with the payment gateway, please consider opening a support ticket in our system. This will give us a more convenient platform to resolve the issue effectively. Thank you!

    Thread Starter Marco van Wieren

    (@wpo365)

    Hi @hannausercentrics

    Thank you for your help. I can confirm that customers can now purchase items on the website, even when they deny all (non-necessary) cookies.

    You can close this ticket.

    Plugin Support hannausercentrics

    (@hannausercentrics)

    Hi @wpo365 ,
    Thank you so much for the update! I’m glad to know that the solution worked for you.

    Should you need any further assistance or have any other questions, please don’t hesitate to reach out.
    We’re always here to help!

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.