DBSC currently refuses to bind cookies with the Partitioned attribute because all the session data is unpartitioned. This makes it challenging to use for certain payments use cases. For example, https://www.w3.org/2024/Talks/TPAC/fime-dbsc-3ds.pdf describes using DBSC for payments. The goal is for card issuers to have a session scoped only to a when the top-level site is a particular merchant. That's good for privacy, and could make payment flows smoother.
DBSC currently refuses to bind cookies with the Partitioned attribute because all the session data is unpartitioned. This makes it challenging to use for certain payments use cases. For example, https://www.w3.org/2024/Talks/TPAC/fime-dbsc-3ds.pdf describes using DBSC for payments. The goal is for card issuers to have a session scoped only to a when the top-level site is a particular merchant. That's good for privacy, and could make payment flows smoother.