MoonPay checkout blocked in production — CSP frame-ancestors missing checkout.web3auth.io

Embedded Wallets (Web3Auth)
, ,
1

Hi Web3Auth team,

The showCheckout() function from @web3auth/modal v10.14.1 is completely broken in production. MoonPay’s
buy dot moonpay dot com returns a Content-Security-Policy header that blocks the iframe from loading:

frame-ancestors https://*.moonpay.com https ://app dot tor dot us https: //testing .tor.us https ://lrc .tor.us
https://develop-checkout.web3auth.io https://staging-checkout.web3auth.io

develop-checkout.web3auth.io and staging-checkout.web3auth.io are whitelisted, but the production domain
checkout.web3auth.io is not. This means every Web3Auth app on SAPPHIRE_MAINNET using showCheckout() gets a blank
iframe. The same issue also affects the built-in top-up flow inside showWalletUI().

This is on your side — MoonPay’s frame-ancestors whitelist is managed through your partner account with them. The
production domain simply needs to be added the same way dev and staging were.

Can you please get this resolved with MoonPay? This is blocking our users from funding their wallets.

Our setup:

  • @web3auth/modal v10.14.1
  • Network: SAPPHIRE_MAINNET
  • Chain: Solana (chainId 0x65)

Thanks

(sorry it would only allow me to post 6 links so I had to expand some links here)

2

Hi @antiquatedbot Sorry for the late. We will check and get back to you soon.

1 Like
5

@antiquatedbot Our team already noticed this issue and we will fix it as soon as possible.

6

Okay, please keep us updated. Another issue that we have been facing is making a specific chain the dominant chain. Our platform is Solana native. We support Base and BNB but throughout our transaction process, web3auth continuously switches back to eth; it does not continuously stay on solana after we call switch chains. Our hope would be that it was persistent on the specified chain until called to switch.

And the final issue is the error we get when the user closes the modal without logging in. Just a nuance, but it does show up in devtools.

7

Sure, we’ll share here when there is an update. Thank you for understanding!

8

Hey @antiquatedbot Can you open separate issues for each problem you are facing? I have raised the Moonpay issue with the engineering team and it will be resolved by this week. They will update us with the particular. For you other issues, we will need some more particular information about what exact behavior you are expecting and what you are getting. We will accordingly recommend you the best course of action on that. Please open up separate issues for those since it helps us manage it much better.

9

This issue should be fixed, please check and let us know if you are facing this still. For the other issues, feel free to open up new threads as needed.

1 Like