Payment Request BUG

Question

Payment Request BUG

fandian 5

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

1 answer

Your answer

Answer 1

Tom Tran (WICLOUD CORPORATION) 4,500 Microsoft External Staff Moderator

Hi @fandian,

From what you’ve shown, the purchase dialog closing immediately isn’t caused by your code. It’s happening because the Microsoft Store Billing URL used in the docs (https://store.microsoft.com/billing) is now returning a 301 redirect to https://www.microsoftstore.com/, and browsers block cross‑site redirects when loading a payment‑method manifest. Once that redirect happens, Edge treats the manifest as invalid and closes the sheet right away.

Your canMakePayment() result is correct, the method identifier format is supported but the redirect prevents the actual payment manifest from loading. That’s why you’re seeing:

Cross-site redirect … not allowed for payment manifests AbortError: User closed the payment app

Right now, the billing URL in Microsoft’s own Digital Goods API documentation still points to the redirecting host, so this appears to be an upstream issue rather than something wrong in your app.

Perhaps you could give these suggestions a try first:

Keep your Digital Goods API usage, but fallback to your normal web checkout when PaymentRequest.show() fails. This is the recommended pattern when a payment method identifier isn’t available.
If your app uses a Content Security Policy, make sure connect-src allows the PMI host, otherwise future requests may also get blocked, newer Chromium builds enforce this.
You can test https://www.microsoftstore.com/billing directly, but there’s no official confirmation that it hosts a proper payment manifest, so treat that only as an experiment.

If you’re running this outside a Microsoft Store–installed PWA, it also won’t complete purchases, so ensure you’re testing inside the Store installation.

Are you testing the purchase flow inside the Microsoft Store–installed version of your PWA, or just from the browser?

fandian 5 Reputation points

2026-02-10T11:47:16.0833333+00:00
Thank you for the suggestions. I have added the Content Security Policy as you recommended: <meta http-equiv="Content-Security-Policy" content="connect-src 'self' https://store.microsoft.com;">

I am testing the purchase flow within the Microsoft Store–installed PWA. Otherwise, the Digital Goods API would not be accessible at all.

I also tested the alternative URL you mentioned: 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. How can I escalate this issue to the relevant Microsoft team for a timely resolution?

Looking forward to your further guidance.
Tom Tran (WICLOUD CORPORATION) 4,500 Reputation points Microsoft External Staff Moderator

2026-02-11T03:49:40.28+00:00
Hi @fandian ,

Thanks for the extra details!

The connect-src policy you added is correct. Since the failure still occurs, this confirms CSP is not the blocking factor here. The payment flow is failing earlier, when the browser tries to resolve the payment‑method manifest and encounters a cross‑site redirect.

Thanks for confirming this. You’re right the fact that the Digital Goods API is accessible already confirms you’re testing in the correct environment. This rules out the most common setup issue.

The fact that both https://store.microsoft.com/billing and https://www.microsoftstore.com/billing return 301 redirects confirms there is currently no publicly exposed billing endpoint that resolves without a redirect. That means there’s no supported URL you can switch to as a workaround.

There is no Partner Center setting that controls the payment‑method identifier URL or its redirect behavior. The billing URL used by the Digital Goods API is global and not app‑ or publisher‑specific. Based on your findings, this behavior is unexpected relative to the current documentation and appears to be service‑side.

Because this affects the Microsoft Store billing infrastructure, it isn’t something that can be resolved through app configuration. Maybe you could give these platforms a try:

GitHub: the Digital Goods API is actively maintained in the Microsoft Edge Explainers repository. Posting or tracking an issue where platform‑level changes or acknowledgements appear first. You can check it out here: https://github.com/MicrosoftEdge/MSEdgeExplainers/issues

Stack Overflow (optional): if you want broader developer visibility, you can post there using tags like microsoft-edge, progressive-web-apps, payment-request-api, digital-goods-api, and microsoft-store, framing it as a platform behavior rather than a coding question.

Support requests: creating a Microsoft support case typically requires an active support plan, and even then, platform‑wide billing behavior is handled through product updates rather than per‑case fixes. I’d recommend this only if you already have a support plan in place. You can check it here: https://learn.microsoft.com/en-us/services-hub/microsoft-engage-center/support/create-new-support-case?pivots=enhanced or https://support.serviceshub.microsoft.com/supportforbusiness/create

Disclaimer: Some of these are non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classifies as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

In the meantime, since this blocks purchases, the only practical mitigation is to provide a temporary fallback purchase flow so users aren’t stuck while the billing endpoint behavior is addressed upstream.

Sorry if I couldn't assist you further, and I agree it’s not what the current documentation implies. You’ve provided solid repro data here, and that’s exactly what helps this get traction on the platform side.

If you find my assistance helpful, please kindly consider marking it as the final answer by following this instruction so others can find guidance from your post.

Thank you.
Tom Tran (WICLOUD CORPORATION) 4,500 Reputation points Microsoft External Staff Moderator

2026-02-18T10:13:53.7033333+00:00

Hi @fandian ,

I'm just checking in to see if you still have any questions, please feel free to comment below. I'll be happy to assist!
Tom Tran (WICLOUD CORPORATION) 4,500 Reputation points Microsoft External Staff Moderator

2026-03-05T10:25:30.92+00:00

Hi @fandian ,

It's been a while since we last heard from you. Hope things are going well.

If you're still interested or have any questions, feel free to reach out whenever it works best for you.

Share via

Payment Request BUG

1 answer

Your answer