# Stripe & Future Chrome Cross-Site Cookie Blocking

**URL:** <https://community.feathery.io/t/stripe-future-chrome-cross-site-cookie-blocking/234>\
**Category:** Support\
**Created:** [October 27, 2023, 4:50am UTC](https://community.feathery.io/t/stripe-future-chrome-cross-site-cookie-blocking/234 "2023-10-27T04:50:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![szollar](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.feathery.io/szollar/32/34_2.png) [@szollar](https://community.feathery.io/u/szollar)\
**Post date:** [October 27, 2023, 4:50am UTC](https://community.feathery.io/t/stripe-future-chrome-cross-site-cookie-blocking/234/1 "2023-10-27T04:50:45Z")

</div>

I was looking at website errors through chrome dev tools and I saw these flags for Stripe, it’s not an issue now, but will it become a problem in April 2024? Google offers this guidance, [Prepare for phasing out third-party cookies - Chrome for Developers](https://developer.chrome.com/docs/privacy-sandbox/third-party-cookie-phase-out/), to use Partitioned cookies with CHIPS for embeds/payment embeds, but I don’t think this is something I think I have control over via integrations or settings?

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/feathery/original/1X/03eab7ab0d38ba2c3d5edd498fdf58223f8916c1.png)

---

<div class="post-metadata">

**Author:** ![peter](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.feathery.io/peter/32/7_2.png) [@peter](https://community.feathery.io/u/peter)\
**Post date:** [October 27, 2023, 4:54am UTC](https://community.feathery.io/t/stripe-future-chrome-cross-site-cookie-blocking/234/2 "2023-10-27T04:54:31Z")

</div>

This is something that is handled on stripe’s side [Chrome 80 SameSite cookie change : Stripe: Help & Support](https://support.stripe.com/questions/chrome-80-samesite-cookie-change)