[Digital Goods] PaymentRequest supportedMethods not works

I am testing the purchase flow within the Microsoft Store–installed PWA.

I can obtain digital goods according to the following documentation, but when I initiate a purchase, the purchase dialog pops up and disappears immediately.

https://learn.microsoft.com/en-us/microsoft-edge/progressive-web-apps/how-to/digital-goods-api#purchasing-an-item-paymentrequest-constructor-and-show-method

const request = new PaymentRequest([

	  {

			supportedMethods:"https://store.microsoft.com/billing",

            data: { sku: "lse12" }

	  }

	]);

	request.canMakePayment().then(result => {

	  if (result) {

	    console.log("This browser supports the specified payment method.")

	  } else {

	    console.log("This browser does NOT support the specified payment method.")

	  }

	}).catch(err => {

	   console.error("canMakePayment Error", err);

	});

	request.show()

	  .then(response => {

	    console.log("Success", response);

	    response.complete("success");

	  })

	  .catch(err => {

	    console.error("Pay Error", err);

	  });

This browser supports the specified payment method.

The console shows the following error.

Cross-site redirect from "https://store.microsoft.com/billing" to "https://www.microsoftstore.com/" not allowed for payment manifests.

Pay Error AbortError: User closed the payment app.

curl -I https://store.microsoft.com/billing
  HTTP/1.1 301 Moved Permanently
  Date: Tue, 10 Feb 2026 09:52:20 GMT
  Server: Kestrel
  Location: https://www.microsoftstore.com/
  Strict-Transport-Security: max-age=31536000

I also tested the alternative URL : https://www.microsoftstore.com/billing. Unfortunately, it also returns a 301 redirect (to https://www.microsoft.com/store/b/home), so it does not work either.

I am concerned about why the official payment URL (https://store.microsoft.com/billing) is returning a 301 redirect. Is this a known bug, or is there a specific configuration required in Partner Center to avoid this issue?

This problem is currently blocking users from making purchases, which is causing significant disruption.

Looking forward to your help.

Start with the PaymentRequest purchasing flow and reproduce the redirect using the two payment URLs in the report, including the shown curl checks. Investigate whether the payment manifest rejects the redirects and whether Partner Center has a required configuration. Done means documenting the cause and a verified URL or configuration that keeps purchases working.