# Payments

My goal with Gravity Native is to make it accessible for Javascript developers to build mobile apps without spending months learning new skills

To achieve this, I’ve chosen a stack of [React Native](https://facebook.github.io/react-native/) managed with [Expo](https://expo.io) which means you can deploy a fully functional mobile app to both iOS and Android with Javascript and no native programming experience.

While payments are currently possible with Expo, it requires ejecting from the Expo managed workflow and working with complicated procedures and debugging using native IDEs.

This process is not for the faint-hearted or those without native development experience.

Therefore, to keep things simple for everyone, I’ve decided to hold off on implementing payments until Expo releases a payments module that can be used in the managed workflow without ejecting.

The good news is that this is the [most requested Expo feature](https://expo.canny.io/feature-requests?sort=top). 

If you need payments urgently, you can eject your Gravity Native app at any point and [install the Expo payments module.](https://docs.expo.io/versions/latest/sdk/payments/) 

{% hint style="danger" %}
In-app subscriptions will be subject to Apple’s 30% commission. Alternatively, you can accept subscription payments using [Gravity Web ](/gravity-web/introduction.md)for \~3% using [Stripe](https://stripe.com).
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.usegravity.app/gravity-native/payments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.