> ## Documentation Index
> Fetch the complete documentation index at: https://api.fanvue.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# App Payments

> Charge creators for your Fanvue app through Fanvue’s payment rails: pricing plans, one-time items, checkout links, webhooks, and reconciliation.

Once your app is listed on the App Store, you can charge for it through Fanvue's payment rails. Fanvue handles checkout, cards, billing, and refunds. **Fanvue takes 20% of each sale; you keep 80%.**

<Note>
  App Store billing charges **creators** (or agency team members managing them), signed in to Fanvue. Fans pay creators through [checkout links](/docs/payments/accept-payments) or, inside fan-facing apps, through **fan experiences**, which run on their own rails.
</Note>

## Two ways to charge

|              | **Pricing plans**                                                     | **One-time items**                |
| ------------ | --------------------------------------------------------------------- | --------------------------------- |
| **Best for** | App access: tiers, Pro plans                                          | Consumables: credit packs, boosts |
| **Billing**  | Monthly subscription                                                  | One-off, repurchasable            |
| **Price**    | Free, or \$3.99 to \$500                                              | \$3.99 to \$500                   |
| **Sold via** | Listing plan picker, [deeplinks](/docs/app-store/deeplinks), checkout link | Checkout link                     |

Both are configured in your app's **Pricing** tab in the Builder. See [Pricing Plans](/docs/app-store/payments/pricing-plans) and [One-time Items](/docs/app-store/payments/one-time-items).

## The flow, end to end

<Steps>
  <Step title="Configure pricing">
    Add plans and items in the **Pricing** tab. Paid apps must be [listed](/docs/app-store/app-types#listing-payment-and-app-type).
  </Step>

  <Step title="Get approved">
    Plans show **Pending setup** and activate when your app [passes review](/docs/app-store/publishing-your-app).
  </Step>

  <Step title="Share">
    Plan picker on your listing, [deeplinks](/docs/app-store/deeplinks), or `app_` checkout links.
  </Step>

  <Step title="Receive webhooks">
    Fulfil access off [`app.subscription.activated`](/docs/app-store/webhooks/subscriptions), reconcile revenue off [`app.payment.succeeded`](/docs/app-store/webhooks/payments).
  </Step>

  <Step title="Gate access">
    Check [`GET /apps/{appUuid}/subscription/me`](/docs/app-store/app-subscriptions) server-side: `hasActiveSubscription`, with `currentPeriodEnd` and `cancelAtPeriodEnd` for when access ends.
  </Step>

  <Step title="Reconcile">
    Webhooks can be missed; re-read state from the [read endpoints](/docs/app-store/webhooks#reconciliation).
  </Step>
</Steps>

## Money and access are separate events

A subscription's initial charge emits **both** `app.payment.succeeded` (`billing_reason: subscription_initial`) **and** `app.subscription.activated`. Fulfil access off the subscription event; reconcile revenue off the payment event.

## Next steps

<CardGroup cols={2}>
  <Card title="Pricing Plans" icon="arrows-rotate" href="/docs/app-store/payments/pricing-plans">
    Setup, statuses, plan IDs, and subscription events.
  </Card>

  <Card title="One-time Items" icon="coins" href="/docs/app-store/payments/one-time-items">
    Consumables, attribution, and fulfilment.
  </Card>

  <Card title="App Webhooks" icon="bolt" href="/docs/app-store/webhooks">
    The `app.*` event reference.
  </Card>

  <Card title="App Subscriptions" icon="user-check" href="/docs/app-store/app-subscriptions">
    Pricing lifecycle and entitlement endpoints.
  </Card>
</CardGroup>