> ## 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. # Update Card > Updates the specified issuing card object by setting the values of the parameters passed. Any parameters not provided will be left unchanged. ## OpenAPI ````yaml /card-issuance/v1.6/issuing.yaml post /v1/issuing/cards/{id} openapi: 3.0.2 info: title: Issuing API version: 0.0.1 description: > UQPAY Issuing API allows you to issue virtual cards, manage cardholders, and monitor card transactions. ## What you can do - Create and manage virtual cards (issue, activate, freeze, cancel) - Onboard and verify cardholders with KYC - Set spending limits and card controls - Recharge and withdraw card balances - Query card transactions and account balances - Transfer funds between issuing accounts - Generate and download reports ## 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 x-api-id: uqpay-issuing-api-v1.6.0 x-categories: - Card Issuing - Transaction Processing x-features: - Virtual Card Issuance - Real-time Processing - Webhook Notifications - Comprehensive Reporting - Transaction Monitoring servers: - url: https://api-sandbox.uqpaytech.com/api description: Sandbox base URL. - url: https://api.uqpay.com/api description: Production base URL. security: [] tags: - name: Card Lifecycle description: >- Create cards and manage their full lifecycle — issue, retrieve, update, activate, assign, and change status. - name: Card Secure Data description: >- Access sensitive card data (PAN, CVV) through the PCI-compliant endpoint or a tokenized iframe. Availability depends on your PCI status, not the card product. - name: Card Funding description: Load and unload a card's stored balance for prepaid-style cards. - name: Card PIN description: >- Set and manage card PINs. `reset-pin` covers physical cards; `manage-card-pin` covers virtual cards. - name: Card Add-ons description: >- Product-specific card capabilities. Each operation applies only to certain card products — see [Card products](/card-issuance/v1.6/guide/card-products). - name: Card Arts description: >- Manage the visual designs (card arts) available to your issuing account. Set an account-wide default, or pass `card_art_id` when issuing or updating a card to override per card. Available on Personal Visa. - name: Cardholders description: >- You can create cardholders, which are authorized representatives of your business that can be issued cards. - name: Transactions description: >- These APIs allow you to retrieve information on transactions that are made on your user's cards. - name: Products description: >- With this set of APIs, you will be able to create card orders for your customers. - name: Balances description: >- The available and pending amounts for each currency are broken down further by payment source types. You can retrieve it to see the balance currently on your issuing account. - name: Transfers description: Transfer funds between issuing accounts. - name: Reports description: Generate and download issuing reports. - name: Simulator description: Simulate card transactions on the sandbox environment. paths: /v1/issuing/cards/{id}: post: tags: - Card Lifecycle summary: Update Card description: >- Updates the specified issuing card object by setting the values of the parameters passed. Any parameters not provided will be left unchanged. operationId: update-card parameters: - $ref: '#/components/parameters/IdPath' - $ref: '#/components/parameters/XOnBehalfOf' - $ref: '#/components/parameters/XIdempotencyKey' requestBody: content: application/json: schema: $ref: '#/components/schemas/CardUpdateRequest' responses: '200': headers: x-response-id: $ref: '#/components/headers/XResponseId' description: Card update successfully. content: application/json: schema: title: CardUpdatedResponse type: object required: - card_id - card_order_id - card_status - order_status properties: card_id: $ref: '#/components/schemas/CardId' card_order_id: $ref: '#/components/schemas/CardOrderId' card_status: $ref: '#/components/schemas/CardStatus' order_status: $ref: '#/components/schemas/OrderStatus' example: SUCCESS security: - XAuthToken: [] components: parameters: IdPath: name: id description: Universally unique identifier (UUID v4) of a resource. in: path required: true schema: type: string format: uuid example: 71fdb0fe-9682-457a-9361-e8868694f12f XOnBehalfOf: in: header name: x-on-behalf-of schema: type: string required: false description: > Specifies the sub-account on whose behalf the request is made. This should be set to the `account_id`, which can be retrieved via the [List Connected Accounts](/account-center/v1.6/api-reference/list-connected-accounts) endpoint. If omitted or empty, the request is executed using the master account. More information at [Connected Accounts](/account-center/v1.6/guide/connected-accounts). example: 18523f72-f4de-4f9c-bb8e-ec7d1c4f32be XIdempotencyKey: in: header name: x-idempotency-key schema: type: string format: uuid required: true description: >- A unique identifier (UUID) used to maintain operation idempotency, ensuring that repeated executions of the same operation do not result in unintended effects or duplication. It helps preserve data consistency in the face of network errors, retries, or failures. example: 18523f72-f4de-4f9c-bb8e-ec7d1c4f32be schemas: CardUpdateRequest: type: object properties: card_limit: $ref: '#/components/schemas/CardLimit' description: > The total credit limit assigned to the card, currency refer to `card_currency`. This is **not a cumulative balance**, but a fixed credit limit similar to that of a credit card. - Leave empty when card mode_type is `SINGLE`. name_on_card: $ref: '#/components/schemas/NameOnCard' no_pin_payment_amount: $ref: '#/components/schemas/NoPINPaymentAmount' spending_controls: $ref: '#/components/schemas/SpendingControls' risk_controls: $ref: '#/components/schemas/RiskControls' metadata: $ref: '#/components/schemas/Metadata' card_art_id: $ref: '#/components/schemas/CardArtId' description: > Updates the card art on an existing card. Only allowed on `VIRTUAL` cards whose `card_status` and `processing_status` are both `ACTIVE`; the request is rejected otherwise. Card-art updates are processed asynchronously — the response returns `order_status: PROCESSING` and the new card art takes effect after channel confirmation. The value must be a card art available to the issuing account; list available card arts via [List card arts](/card-issuance/v1.6/api-reference/list-card-arts). CardId: type: string example: c0cef051-29c5-4796-b86a-cd5b684bfad7 description: Unique identifier for the card. CardOrderId: type: string example: c0cef051-29c5-4796-b86a-cd5ee34bfad7 description: ID of the card order. CardStatus: type: string description: > Card status enum. See the Card lifecycle and statuses guide for more information. - `PENDING`: The request to create the card has been received and is under review. - `ACTIVE`: The request to create the card was successful and the card is ready to use. - `FROZEN`: All incoming authorization requests will be declined. The card can be reactivated to accept new authorizations. - `BLOCKED`: The card was blocked by UQPAY due to suspicious activity. - `PRE_CANCEL`: The card is scheduled for cancellation and is in a waiting period during which all incoming authorization requests are declined. It transitions to `CANCELLED` when the waiting period ends. - `CANCELLED`: The card cannot be reactivated from this state, all incoming authorization requests will be permanently declined. - `LOST`: The card has been reported as lost to UQPAY. - `STOLEN`: The card has been reported as stolen to UQPAY. - `FAILED`: The request to create a card using [Create Card](/card-issuance/v1.6/api-reference/create-card) failed. example: ACTIVE enum: - PENDING - ACTIVE - FROZEN - BLOCKED - PRE_CANCEL - CANCELLED - LOST - STOLEN - FAILED OrderStatus: type: string description: | This field will contain the status of the request after processing. * `PENDING` -The initial status of the order request. * `PROCESSING` - If this status shall be subject to webhooks notification. * `SUCCESS` - The final status of the order request is successful. * `FAILED` - The final status of the order request is failed. enum: - PENDING - PROCESSING - SUCCESS - FAILED CardLimit: type: number example: 2100.02 minimum: 0 description: > The total credit limit assigned to the card, currency refer to `card_currency`. This is **not a cumulative balance**, but a fixed credit limit similar to that of a credit card. ##### Field behavior by card product: - **Business Mastercard** and **Personal Visa**: `card_limit` is **required** during card creation and must be **greater than or equal to 0.01**. - **Business Visa**: `card_limit` is **optional**. - If omitted, the system defaults `card_limit` to 0. - If provided, the value must be **greater than or equal to 0**, with up to two decimal places. **Negative values are not allowed.** See [Card products](/card-issuance/v1.6/guide/card-products) for the full capability matrix. NameOnCard: type: string maxLength: 26 example: MARSHALL HU description: > The cardholder name shown on the card. When the [Secure Iframe](/card-issuance/v1.6/guide/secure-iframe-guide) renders the cardholder name (`cardholder_name=true`), this value is used as the default; if omitted, the iframe falls back to `first_name + last_name` from the cardholder record. NoPINPaymentAmount: type: number example: 100 minimum: 0 description: > The allowable amount for card transactions without PIN verification. Default NO-PIN transaction amount applied when not explicitly set by the customer. Defaults to `200 SGD`. If you would like to opt-out from having any transactions without credentials or password, you may adjust the amount to zero (0). **Note:** This setting is only applicable to **Business Visa**. See [Card products](/card-issuance/v1.6/guide/card-products) and [No-PIN payments](/card-issuance/v1.6/guide/pin-and-no-pin-payments) for more information. SpendingControls: type: array description: Rules that control spending for this card. items: type: object required: - amount - interval properties: amount: type: number description: >- Maximum amount allowed to spend per interval, must be greater than or equal to zero. example: 100.03 minimum: 0 interval: type: string example: PER_TRANSACTION enum: - PER_TRANSACTION description: | Interval (or event) to which the amount applies. This field is mandatory and must be one of: * `PER_TRANSACTION` - Can not exceed the max authorization amount RiskControls: type: object description: > User-customized risk control settings. Supported configurations depend on the card product. See [Card products](/card-issuance/v1.6/guide/card-products) for the capability matrix. properties: enable_3ds: $ref: '#/components/schemas/Enable3ds' allow_3ds_transactions: $ref: '#/components/schemas/Allow3dsTransactions' allowed_mcc: $ref: '#/components/schemas/AllowedMcc' blocked_mcc: $ref: '#/components/schemas/BlockedMcc' Metadata: additionalProperties: maxLength: 3200 type: string example: key1: value1 key2: value2 description: >- Any key-value object. Max length = 3200 bytes. This must be valid JSON data. type: object CardArtId: type: string example: 01KD52BKQWDMFF63R1NNQN7A79 description: >- Identifier of a card art. Stable across card products; reuse the same value when creating multiple cards with the same design. Enable3ds: type: string description: > Controls whether [3D Secure](https://en.wikipedia.org/wiki/3-D_Secure) is registered for this card. - `Y` — Register 3DS. The challenge behavior at transaction time is then governed by `allow_3ds_transactions`. - `N` — Do not register 3DS. Online transactions bypass 3DS authentication entirely. Supported on **Business Visa** and **Personal Visa** only; ignored on Business Mastercard. See [Card products](/card-issuance/v1.6/guide/card-products). Returned only when explicitly set on the card. When absent, the card follows the account-level 3DS configuration. Modifiable only when the card is in `PENDING` or `ACTIVE` status. enum: - 'Y' - 'N' example: 'Y' Allow3dsTransactions: type: string description: > Determines whether [3D Secure](https://en.wikipedia.org/wiki/3-D_Secure) challenge flow is allowed when a transaction triggers 3DS. - **When creating a card:** Defaults to `Y` if not provided. - **When updating a card:** No default. If not provided, the existing value remains unchanged. Supported on **Business Visa** only. See [Card products](/card-issuance/v1.6/guide/card-products). > **Note:** This field only takes effect when `enable_3ds` is `Y`. If `enable_3ds` is `N`, the card bypasses 3DS entirely and this field has no effect. > **Important:** When set to `N`, your card uses a frictionless 3DS authentication mechanism — transactions complete without OTP input and are treated as cardholder-authenticated. As a result, disputes based on fraud or unauthorized use cannot be raised for such transactions. For enhanced security, it is recommended to keep this set to `Y`. - `Y`: OTP verification may be required. - `N`: No OTP will be required. enum: - 'Y' - 'N' example: 'Y' AllowedMcc: type: array items: type: string description: > Specifies a whitelist of Merchant Category Codes (MCCs) that are permitted for transactions. All transactions under MCCs not listed here will be declined. **Note:** Only one of `allowed_mcc` or `blocked_mcc` can be configured per card. If neither is provided, transactions will follow the default risk control logic. example: null BlockedMcc: type: array items: type: string description: > Specifies a blacklist of Merchant Category Codes (MCCs) that are restricted for transactions. Transactions under these MCCs will be declined, while all other transactions will proceed through the standard UQPAY risk control evaluation. **Note:** Only one of `allowed_mcc` or `blocked_mcc` can be configured per card. If neither is provided, transactions will follow the default risk control logic. example: - '5999' - '6011' headers: XResponseId: description: >- Universally unique identifier (UUID v4) for the response. Helpful for identifying a request when communicating with UQPAY support. schema: type: string format: uuid example: 2adba88e-9d63-44bc-b975-9b6ae3440dde securitySchemes: XAuthToken: type: apiKey in: header name: x-auth-token description: The API token for login provided by UQPay. ````