Ensure specification handles revenue sharing use case correctly

[lukewarlow]

For revenue sharing the wallet address on the website isn't consistent once requested (we follow redirects and that might end up with different wallet address URLs). We need to make sure that we always use the original resolved wallet address for the duration of a session. The WalletAddressDetails contains an ID and a URL. The URL is currently the original URL and not the resolved one. So if we use this again it might not give the same result.

We separately need should make sure that CSP handles the resolved URLs insteadof/alongside the original one.

[sidvishnoi]

Given the payment session is set up once per tab/document session, how does re-resolving URL come into picture? We'll continue to use the same wallet address response (i.e. the id) for all payments in the session.

Just as a heads up, the url property for WalletAddressDetails is only part of the implementation spec, as a reference to the original URL (same as link.href). It's not meant to be used as part of payments.

[lukewarlow]

Assuming we use id everywhere than that's fine. What is url there for?

[sidvishnoi]

In the extension, we show the user both the url and id of their connected wallet, for informational purposes - as url is what user provided and id is actual identifier response, which aren't always the same (both wallet provider and the user can have custom redirects).

The extension also uses url to find the relevant link tag in some cases (like after page refresh) to emit the last monetization event.