> ## 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. # Get the authenticated user's one-time (app-OTP) payment by invoice number > `read:self`. Fetches one of the caller's own payments by Fanvue invoice number. 404 for unknown invoice numbers, another buyer's payment, or pre-migration rows. **Required scope** * `read:self` — Access your own user profile information, including basic account details and settings. ## OpenAPI ````yaml /openapi.json get /apps/{appUuid}/payments/me/{invoiceNumber} openapi: 3.1.0 info: title: Fanvue API version: '0.1' servers: [] security: [] paths: /apps/{appUuid}/payments/me/{invoiceNumber}: get: summary: >- Get the authenticated user's one-time (app-OTP) payment by invoice number description: >- `read:self`. Fetches one of the caller's own payments by Fanvue invoice number. 404 for unknown invoice numbers, another buyer's payment, or pre-migration rows. operationId: getMyAppPaymentByInvoiceNumber parameters: - $ref: '#/components/parameters/ApiVersionHeader' - schema: type: string format: uuid example: 00000000-0000-4000-8000-000000000001 required: true name: appUuid in: path - schema: type: string example: FVE-20260619-1234 required: true name: invoiceNumber in: path responses: '200': description: The user's one-time payment content: application/json: schema: type: object properties: uuid: type: string description: Horizon purchase identifier. appUuid: type: string description: UUID of the app the purchase belongs to. buyerUuid: type: string description: UUID of the purchasing Fanvue user. planUuid: type: string description: UUID of the purchased pricing plan / item. invoiceNumber: type: - string - 'null' description: >- Fanvue invoice number. Use as the idempotency key for fulfilment. Null for purchases that settled before reconciliation was enabled, or not yet settled. billingReferenceId: type: string description: The `appotp_…` reference minted at checkout. clientReferenceId: type: string description: >- Merchant-supplied reference passed at checkout via `?client_reference_id=`; empty string when unset. status: type: string enum: - pending - completed - failed - refunded - expired description: Lifecycle status of the one-time purchase. amount: type: number description: Amount in minor currency units, snapshotted at checkout. currency: type: string description: ISO currency code. externalPaymentId: type: string description: Provider payment id; empty string until completed. createdAt: type: string format: date-time description: When the purchase was created. updatedAt: type: string format: date-time description: When the purchase was last updated. required: - uuid - appUuid - buyerUuid - planUuid - invoiceNumber - billingReferenceId - clientReferenceId - status - amount - currency - externalPaymentId - createdAt - updatedAt example: uuid: 00000000-0000-4000-8000-0000000000aa appUuid: 00000000-0000-4000-8000-000000000001 buyerUuid: 00000000-0000-4000-8000-000000000003 planUuid: 00000000-0000-4000-8000-000000000002 invoiceNumber: FVE-20260619-1234 billingReferenceId: appotp_000000001VgEh72lXvTXkL clientReferenceId: order_9f8c status: completed amount: 4999 currency: USD externalPaymentId: pi_3Q1example createdAt: '2026-06-19T08:30:00.000Z' updatedAt: '2026-06-19T08:30:05.000Z' '400': description: >- Bad Request - API version not supported OR validation failed OR invalid UUID content: application/json: schema: oneOf: - $ref: '#/components/schemas/UnsupportedVersionError' - $ref: '#/components/schemas/ValidationError' - $ref: '#/components/schemas/InvalidUuidError' '401': $ref: '#/components/responses/UnauthorizedResponse' '403': $ref: '#/components/responses/UnauthorizedResponse' '404': description: App not found / not owned, or payment not found content: application/json: schema: type: object properties: message: type: string '410': $ref: '#/components/responses/SunsetVersionResponse' '429': $ref: '#/components/responses/RateLimitResponse' '502': description: Failed to load payments from upstream content: application/json: schema: type: object properties: message: type: string '503': description: Developer API upstream is not configured content: application/json: schema: type: object properties: message: type: string security: - BearerAuth: - read:self components: parameters: ApiVersionHeader: name: X-Fanvue-API-Version in: header required: true schema: type: string default: '2025-06-26' example: '2025-06-26' description: API version to use for the request schemas: UnsupportedVersionError: type: object properties: error: type: string message: type: string required: - error - message description: API version not supported ValidationError: type: object properties: errors: type: array items: type: string required: - errors description: Request validation failed InvalidUuidError: type: object properties: message: type: string required: - message description: Invalid UUID format provided responses: UnauthorizedResponse: description: Unauthorized Response content: application/json: schema: type: object properties: error: type: string required: - error SunsetVersionResponse: description: API version no longer supported (sunset) content: application/json: schema: type: object properties: error: type: string message: type: string nextVersion: type: string required: - error - message RateLimitResponse: description: Too many requests - rate limit exceeded headers: Retry-After: description: Number of seconds to wait before retrying the request schema: type: integer X-RateLimit-Limit: description: The maximum number of requests allowed in the current window schema: type: integer X-RateLimit-Remaining: description: The number of requests remaining in the current window schema: type: integer X-RateLimit-Reset: description: The Unix timestamp (seconds) when the rate limit window resets schema: type: integer content: application/json: schema: type: object properties: error: type: string required: - error securitySchemes: BearerAuth: type: oauth2 description: >- OAuth 2.0 access token, presented as a JWT bearer token in the `Authorization` header. Obtain a token via the authorization-code flow; the scopes granted to the token determine which operations it may call. flows: authorizationCode: authorizationUrl: https://auth.fanvue.com/oauth2/auth tokenUrl: https://auth.fanvue.com/oauth2/token refreshUrl: https://auth.fanvue.com/oauth2/token scopes: read:self: >- Access your own user profile information, including basic account details and settings. read:chat: >- Read chat conversations, messages, and chat-related data. This includes viewing chat lists and message history. write:chat: >- Create new chats and send messages. This scope is required for any chat-related actions that modify data. read:experience: >- Exchange a fan's experience token for the resolved experience and the fan's identity, so an embedded fan-facing experience can render the right content. write:experience: >- Request that the creator publish or unpublish a fan-facing experience. The app mints a request token; the creator confirms and Fanvue performs the change. read:fan: Access fan-related data and information within the platform. read:post: Read posts, including post details, comments, likes, and tips. write:post: Create, edit, and manage posts and content on behalf of users. read:media: Access media files, images, videos, and other content assets. write:media: >- Upload, modify, and manage media files and content assets. Also required for vault folder management. read:creator: >- Access creator profiles, content, and creator-specific information. write:creator: Modify creator profiles, settings, and creator-specific data. read:insights: >- Access analytics, metrics, and insights data for performance tracking. read:tracking_links: >- Read tracking links and the users associated with them, including per-user tracking metadata. write:tracking_links: Create and delete tracking links. read:agency: Read agency information, including the agency's team members. write:agency: >- Manage agency team members and invites, including inviting new team members and creators. ````