Active wallet authorization detection

API request: The ability for a website to detect if the user has an active Web Monetization wallet authorization

Situation: Web Monetization cannot be used as a paywall in countries where a payment requirement to access content is considered a digital good purchase. Digital good purchases require sales tax collection and potentially invoice issuance. Paywalls are best implemented using a payment method, such as Open Payments and Interledger, an underlying payment method used by Web Monetization.

However, one workaround may be access based on association. Users with Web Monetization could be given access to content based on having an active wallet rather than having paid. An analog is certain credit card holders getting exclusive early access to concert ticket sales or restaurant reservation blocks. No payment is involved, only proof of being a card holder.

Web Monetization needs something similar: proof of being a user. Feature detection of Web Monetization does not provide proof the user is using it. An additional API is needed to verify the user has an active wallet. Waiting for the first payment in inadequate, as relying on a payment to provide access is equivalent to a paywall. The access must be based on a user's ability to pay, not an actual payment, with the accepted risk to the website that the user may not actually ever contribute a Web Monetization payment.

Start with the Web Monetization specification's feature-detection section and the API request in this issue. The issue names no repository files or tests; done would require an agreed design for detecting active wallet authorization, including its privacy and payment implications.