There is no process to "submit" an app for inclusion in Odoo SaaS. The apps on the SaaS are certified modules covered by the Odoo Enterprise contract. Certifying a module is a big deal as it extends the responsibility of Odoo towards all its customers in terms of maintenance. This is why a module goes through an extensive certification process at Odoo R&D before being certified. You cannot ask that Odoo "looks into" your module to see if it's good enough to be included because everybody creating a module would ask that and this is just not feasible from a resources standpoint (think of the 4000 modules). Additionally, the modules that the community develop are project-driven while the Odoo product roadmap is mass-adoption/innovation/usability driven. Example: a customer is never going to ask a partner (or its IT department) to make the framework API more efficient; they will ask for more features. If only project-driven modules were added to the certified modules, we would end up with a frankenstein Odoo with modules whose rationales come from different projects in different industries with different requirements; it's a threat to genericity.

In regards with your Stripe integration, your best bet is to develop it as similarly as the Ogone one as possible. You have a higher chance with a module like this than with a module that introduces a brand new feature because you can copy another certified module that does the same (except with a different payment processor). Then, make a pull request into Odoo master: https://github.com/odoo/odoo/pulls

There is no way to include new modules in the SaaS platform. We limit the number of features so that we can guarantee smooth upgrades and bug fix guarantee at very low costs. Odoo prefers to focus its efforts on making existing features become perfect rather than adding more features.

At the current price, we can't afford loosing a few days\hours per monthly upgrade due to a third party module. We would loose all our margins. Usually, the maintenance cost of a module is twice its development costs over the span of 3 years, that's why we can't maintain third party modules at our charge.

Could you make this module publically available? I'd like to make use of it.

Thanks!