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

# Get static QR options

> Check the target account setup, enabled payment methods, and supported currencies. See the [static QR guide](/global-acquiring/v1.6/guide/static-qr-codes).



## OpenAPI

````yaml /global-acquiring/v1.6/payment.yaml get /v2/payment/static_qrs/options
openapi: 3.0.2
info:
  title: Payment API
  version: 0.0.1
  description: >
    UQPAY Payment API allows you to accept payments, manage transactions, and
    process refunds and payouts.


    ## What you can do

    - Create and confirm payment intents using cards, digital wallets, and local
    payment methods

    - Process full and partial refunds

    - Create payouts and bank account records

    - Query payment attempts, balances, and transaction history


    ## Authentication

    All requests require a valid auth token obtained via the [Access
    Token](/account-center/v1.6/api-reference/access-token) endpoint. Include
    the token in the `x-auth-token` header.


    ## Idempotency

    POST requests support the `x-idempotency-key` header to safely retry without
    creating duplicate resources.
  contact:
    name: UQPAY Support Team
    url: https://www.uqpay.com/support
    email: support@uqpay.com
  license:
    name: Proprietary
    url: https://www.uqpay.com/legal/api-terms
  termsOfService: https://www.uqpay.com/legal/terms
servers:
  - url: https://api-sandbox.uqpaytech.com/api
    description: Sandbox base URL.
  - url: https://api.uqpay.com/api
    description: Production base URL.
security:
  - XAuthToken: []
tags:
  - name: Payment Intents
    description: >-
      A PaymentIntent guides you through the process of collecting a payment
      from your customer. We recommend that you create exactly one PaymentIntent
      for each order or customer session in your system. You can reference the
      PaymentIntent later to see the history of payment attempts for a
      particular session.
  - name: Payment Attempts
    description: >-
      A PaymentAttempt object is created whenever a customer makes a payment
      with the chosen PaymentMethod. This API allows you to find out how your
      customer paid for your order.
  - name: Payment Refunds
    description: >
      You can create multiple partial refunds until reaching the original
      transaction amount. Each refund generates a unique record and undergoes
      automatic validation against available balances.

      A PaymentIntent guides you through the process of collecting a payment
      from your customer. We recommend that you create exactly one PaymentIntent
      for each order or customer session in your system. You can reference the
      PaymentIntent later to see the history of payment attempts for a
      particular session.
  - name: Payment Balances
    description: >
      Payment balance management allows you to query account balances for
      different currencies. You can retrieve individual currency balances or all
      currency balances with pagination support.
  - name: Payment Payouts
    description: >
      Payout management allows you to create and manage payout orders for fund
      transfers. You can create payouts, query individual payouts, and list all
      payouts with filtering and pagination support.
  - name: Terminal Management
    description: Terminal management APIs for POS device registration and key management.
  - name: Bank Accounts
    description: >
      Bank account management APIs for settlement accounts. Create, update,
      retrieve, and list bank accounts used for receiving settlement payments.
  - name: Static QR Codes
    description: Create, retrieve, list, and manage reusable payment QR codes.
paths:
  /v2/payment/static_qrs/options:
    get:
      tags:
        - Static QR Codes
      summary: Get static QR options
      description: >-
        Check the target account setup, enabled payment methods, and supported
        currencies. See the [static QR
        guide](/global-acquiring/v1.6/guide/static-qr-codes).
      operationId: get-static-qr-options
      parameters:
        - $ref: '#/components/parameters/XClientID'
        - $ref: '#/components/parameters/StaticQRTarget'
      responses:
        '200':
          description: Request completed. Interpret the resource status separately.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/StaticQROptions'
              examples:
                sandbox:
                  summary: Get static QR options
                  value:
                    eligible: false
                    ineligible_reasons:
                      - WECHAT_SGQR_NOT_CONFIGURED
                      - PAYNOW_CHANNEL_NOT_CONFIGURED
                    payment_methods:
                      - ALIPAY
                      - WECHAT
                      - PAYNOW
                      - UNIONPAY
                    currencies:
                      - SGD
        '400':
          description: Invalid fields or unmet static QR configuration requirements.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/StaticQRError'
        default:
          description: >-
            Other errors, including authentication failures, can use the common
            API error response.
components:
  parameters:
    XClientID:
      in: header
      name: x-client-id
      schema:
        type: string
      required: true
      description: The API client id generated by UQPAY
      example: Up1HIsjiETgON9PMGPXLy7
    StaticQRTarget:
      name: x-on-behalf-of
      in: header
      required: false
      description: >-
        The authorized connected sub-account to manage. Omit or send an empty
        value to use the credential account. Use the same target account for all
        operations on a code. Do not send the credential account ID as an
        explicit sub-account.
      schema:
        type: string
        format: uuid
  schemas:
    StaticQROptions:
      type: object
      required:
        - eligible
        - ineligible_reasons
        - payment_methods
        - currencies
      properties:
        eligible:
          type: boolean
          description: >-
            Whether the account satisfies the checked static QR setup
            requirements. Review ineligible_reasons alongside the payment
            methods you intend to use.
        ineligible_reasons:
          type: array
          description: >-
            Account or payment-method setup requirements that are not met.
            Contact UQPAY support for configuration assistance.
          items:
            type: string
        payment_methods:
          type: array
          description: >-
            Enabled payment methods. Inclusion does not by itself establish that
            all channel configuration requirements are met.
          items:
            type: string
            enum:
              - ALIPAY
              - WECHAT
              - PAYNOW
              - UNIONPAY
        currencies:
          type: array
          description: Currencies available for code creation.
          items:
            type: string
    StaticQRError:
      type: object
      required:
        - code
        - message
        - type
      properties:
        code:
          type: string
          description: Machine-readable error code.
        message:
          type: string
          description: Explanation of the failure and, where available, how to correct it.
        type:
          type: string
          enum:
            - static_qr_error
  securitySchemes:
    XAuthToken:
      type: apiKey
      in: header
      name: x-auth-token
      description: The API token for login provided by UQPAY.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.