> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/billing.md).

# Billing screens

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/billing/README.md).
{% endhint %}

Plans and subscriptions: the Site Console's subscription tab on the web, the payment page that customers get from the Snapfix team (the separate web\_payments app), and in-app purchase on iOS. Their endpoints are in the [Billing API](https://docs.snapfix.com/engineering-reference/api/billing.md); the site reads they start from are in the [Console API](https://docs.snapfix.com/engineering-reference/api/console.md). The staff side, where packages and the paywall are set up, is in the staff admin app: [Paywall](https://docs.snapfix.com/how-the-apps-work/screens/staff/paywall.md), [Stripe payment](https://docs.snapfix.com/how-the-apps-work/screens/staff/stripe-payment.md) and [Credit card payment](https://docs.snapfix.com/how-the-apps-work/screens/staff/card-payment.md).

None of these screens was seen live. The QA site has no subscription, so its Site Console has no subscription tab \[[ASK-135](https://github.com/snapfix/docs/blob/main/ASK.md#ask-135-which-qa-site-can-show-the-your-subscription-tab)]; the live passes open no payment link and cover the web only.

| Screen                                                                                          | Platforms | Where                                                                                                  |
| ----------------------------------------------------------------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------ |
| [Your subscription](https://docs.snapfix.com/how-the-apps-work/screens/billing/subscription.md) | web       | web `/account/:id/subscription`, a Site Console tab shown to site admins of a site with a subscription |
| [Snapfix payment](https://docs.snapfix.com/how-the-apps-work/screens/billing/payment-page.md)   | web       | web: package.snapfix.com `/single/:id`, `/multi/:id`                                                   |
| [Choose plan](https://docs.snapfix.com/how-the-apps-work/screens/billing/choose-plan.md)        | ios       | iOS: side menu "Settings", "Subscriptions" (shown when a site allows in-app purchase)                  |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snapfix.com/how-the-apps-work/screens/billing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
