title: Using external payments processor on Android for SaaS instead of Google Play In-app Billing
body: <p>I’ve built a SaaS website with subscriptions, enabled by an external payments processor (which could be <a href="https://stripe.com/" rel="noreferrer">Stripe</a>, <a href="https://www.braintreepayments.com/" rel="noreferrer">Braintree</a>, <a href="https://paddle.com/" rel="noreferrer">Paddle</a>, etc.).</p>
  
  <p>Now this website for my SaaS has been packaged in a small <a href="https://developer.android.com/reference/android/webkit/WebView.html" rel="noreferrer"><code>WebView</code></a> wrapper and is about to be released as an Android app. But on the Stripe website, I found this:</p>
  
  <blockquote>
    <p>Google’s developer terms require that purchases related to the app, such as premium features or credits, are made via their native In-app Billing API.</p>
    
    <p>– <a href="https://stripe.com/docs/mobile/android" rel="noreferrer">https://stripe.com/docs/mobile/android</a></p>
  </blockquote>
  
  <p>Diving deeper into Google Play’s terms, you can find this (emphasis mine):</p>
  
  <blockquote>
    <ul>
    <li>Developers offering products within a game downloaded on Google Play or providing access to game content must use <a href="https://developer.android.com/google/play/billing/index.html" rel="noreferrer">Google Play In-app Billing</a> as the method of payment.</li>
    <li><strong>Developers offering products within another category of app downloaded on Google Play must use <a href="https://developer.android.com/google/play/billing/index.html" rel="noreferrer">Google Play In-app Billing</a> as the method of payment, except for the following cases:</strong>
    
    <ul>
    <li>Payment is solely for physical products</li>
    <li><strong>Payment is for digital content that may be consumed outside of the app itself (e.g. songs that can be played on other music players)</strong></li>
    </ul></li>
    </ul>
    
    <p>– <a href="https://play.google.com/intl/en/about/monetization-ads/" rel="noreferrer">https://play.google.com/intl/en/about/monetization-ads/</a></p>
  </blockquote>
  
  <p>So that seems more permissive than Stripe’s interpretation, and since my SaaS is not a game and can be used via a generic web browser as well, my understanding would be that using an external payments processor instead of Google Play’s billing is fine.</p>
  
  <p>On the one hand, this would mean that most digital services could avoid Google Play’s billing and use something else, which seems (too) fair on Google’s part. On the other hand, this excludes games, which Google can generate a lot of revenue from, so it may be reasonable again.</p>
  
  <p>This is not a legal question, and the answer could not be found in legal literature or by asking a lawyer, anyway. Instead, it’s entirely up to Google’s discretion whether using an external payments processor is allowed or not, based on one’s interpretation of the terms presented above.</p>
  
  <p>So instead of legal advice, I’m looking for practical guidelines and examples of real-world usage that supports any interpretation of the terms above.</p>
  
  <p>One example that I’ve found is Dropbox: Having downloaded their app on Android, Dropbox allows me to select between two payment methods: Google Play, or debit card on Dropbox’s own site. This seems to support the more permissive interpretation of Google Play’s terms.</p>
  
  <p>Another example is Spotify, which opens a WebView where you can choose from several payment options, none of which is Google Play. The app still has Android’s permission for in-app purchases, though, which is also disclosed in the Play Store, so perhaps they’re using Google’s in-app billing in specific countries only.</p>
  
  <p>Are there any other real-world examples?</p>