Issue with Stripe Integration – Seeking Alternative Payment Solutions

[Atif NABIL]

Dear Support Team,
I hope this message finds you well.
I am currently experiencing an issue with publishing my extension on the Chrome Web Store. During the review process, the use of Stripe for payment processing has been flagged because Stripe relies on external libraries, which has resulted in my extension being blocked from publication.I would like to ask if you could recommend any alternative solutions or payment providers that are compliant with your policies. Specifically, I am looking for an option that allows payments to be processed directly within the page (without requiring redirections or pop-ups), similar to how Stripe operates.Any guidance you can provide on supported or recommended payment integration methods that meet your requirements would be greatly appreciated, as it is essential for my extension to offer a seamless payment experience to users.

[Alesandro Ortiz]

Hi Atif,

I'm an independent extension developer who uses Stripe to process payments.

You can host the Stripe payment on your own website or use https://extensionpay.com/ -- I've used both successfully. Both do require processing the payment either in a popup or tab, though.

I don't think there's an easy or policy-compliant way to process payments within extension pages. I don't remember if you can embed remote iframes in MV3 extensions, but if it's allowed, maybe you could use that approach (iframe to your own website with Stripe library). That said, it feels more complicated than integrating Stripe on your own website, using hosted Stripe checkout pages, or using ExtensionPay. The user experience is still acceptable if you use popups or tabs to process payments, which is quite common among extensions that accept payments.

If you want to move quickly, ExtensionPay is a great solution.

Regards,

Alesandro

[Simeon Vincent]

I’m not a Google rep, but it’s fine to embed an iframe for use cases like this. From the Additional Requirements for MV3 section of the developer policies:

Additionally, code run in contexts that are isolated from extension APIs (such as iframes and sandboxed pages) are exempt from the restriction on loading code from remote sources; however, these are treated similarly to our policy on communication with external servers. That is, it must still be possible to determine the full functionality of your extension and the interaction must still comply with our user data policies, including Limited Use and the extension's Privacy Policy.

Simeon - @dotproto

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/80bc7932-b396-4fc1-a5bb-c7d5601b94b3n%40chromium.org.