Tomasz Błachowicz

Using CredentialsContainer.get() instead of Payment Request API

12

The[ initial proposal](https://github.com/w3c/secure-payment-confirmation#authenticating-a-payment) assumed that Payment Request API (PR API) should be used to trigger the SPC flow. The client code would use PR API providing the payment method as...

Update requirements.md

1

Some new requirements, some questions to the existing ones, and few corrections.

Add Support for Cross-Device Authentication

2

I'm not entirely sure if the matter relates to the specification or it's purely related to the browser vendor implementations. However, I'd like to raise that with the WPWG for...

Where does the challenge value go in the Registration JWT?

1

In the [high-level overview](https://github.com/WICG/dbsc/blob/main/README.md#high-level-overview) diagram explains that the Server returns the random challange value in `Sec-Session-Registration` response header and then the Browser generates the signed Registration JWT that should contain...

In the [high-level overview](https://github.com/WICG/dbsc/blob/main/README.md#high-level-overview) diagram there is example of Sec-Session-Registration header returned by the server which contains both `session_identifier` and `challange` as named parameters. However, further in more detailed description...