> ## 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.
# Elevate Per-Transaction Limit
> Personal Visa only
Temporarily raise the per-transaction limit on an `ACTIVE` card without an approval flow. The elevated limit auto-reverts to the card's standard per-transaction limit when the elevation expires; the card's long-term limit settings stay unchanged.
**Per-currency caps**
| Currency | Maximum elevated per-transaction limit |
|---|---|
| USD / XUSD | 80,000 |
| SGD | 100,000 |
**Concurrency**
A card can hold only one elevation in `processing` or `active` state at a time. Submitting another request while one is still in effect returns `400`.
**Fields managed by the server (do not send in the request body)**
| Field | Reason |
|---|---|
| `currency` | Resolved from the card's currency. |
| `intent` | Fixed by the server to an internal enum. |
| `reason` | Not accepted. |
**Asynchronous result**
The synchronous response only acknowledges the request and returns `order_status: PENDING`. The final outcome is delivered via the [`card.elevate_limit.succeeded`](/card-issuance/v1.6/webhooks/card-elevate-limit) or [`card.elevate_limit.failed`](/card-issuance/v1.6/webhooks/card-elevate-limit) webhook. Match the webhook to the request by `card_id` — a card can only have one elevation in flight at a time.
## OpenAPI
````yaml /card-issuance/v1.6/issuing.yaml post /v1/issuing/cards/{id}/elevate_limit
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}/elevate_limit:
post:
tags:
- Card Add-ons
summary: Elevate Per-Transaction Limit
description: >
Personal Visa only
Temporarily raise the per-transaction limit on an `ACTIVE` card without
an approval flow. The elevated limit auto-reverts to the card's standard
per-transaction limit when the elevation expires; the card's long-term
limit settings stay unchanged.
**Per-currency caps**
| Currency | Maximum elevated per-transaction limit |
|---|---|
| USD / XUSD | 80,000 |
| SGD | 100,000 |
**Concurrency**
A card can hold only one elevation in `processing` or `active` state at
a time. Submitting another request while one is still in effect returns
`400`.
**Fields managed by the server (do not send in the request body)**
| Field | Reason |
|---|---|
| `currency` | Resolved from the card's currency. |
| `intent` | Fixed by the server to an internal enum. |
| `reason` | Not accepted. |
**Asynchronous result**
The synchronous response only acknowledges the request and returns
`order_status: PENDING`. The final outcome is delivered via the
[`card.elevate_limit.succeeded`](/card-issuance/v1.6/webhooks/card-elevate-limit)
or
[`card.elevate_limit.failed`](/card-issuance/v1.6/webhooks/card-elevate-limit)
webhook. Match the webhook to the request by `card_id` — a card can only
have one elevation in flight at a time.
operationId: elevate-card-limit
parameters:
- $ref: '#/components/parameters/IdPath'
- $ref: '#/components/parameters/XOnBehalfOf'
- $ref: '#/components/parameters/XIdempotencyKey'
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/ElevateLimitRequest'
responses:
'200':
headers:
x-response-id:
$ref: '#/components/headers/XResponseId'
description: >-
Elevation request accepted. Listen on the webhook for the final
result.
content:
application/json:
schema:
$ref: '#/components/schemas/ElevateLimitResponse'
title: ElevateLimitResponse
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:
ElevateLimitRequest:
type: object
required:
- limit_amount
properties:
limit_amount:
type: number
multipleOf: 0.01
example: 80000
description: >
The new per-transaction limit to apply, denominated in the card's
currency. Must be greater than `0`, up to two decimal places, and
within the per-currency cap (`80000` for USD/XUSD, `100000` for
SGD).
duration_in_days:
type: integer
minimum: 1
maximum: 14
default: 14
example: 14
description: >
Number of days the elevation remains in effect. When the elevation
expires, the per-transaction limit auto-reverts to the card's
standard cap.
ElevateLimitResponse:
type: object
required:
- card_id
- card_order_id
- order_status
properties:
card_id:
$ref: '#/components/schemas/CardId'
card_order_id:
$ref: '#/components/schemas/CardOrderId'
order_status:
type: string
enum:
- PENDING
example: PENDING
description: >
Always `PENDING` on a freshly accepted elevation request. Listen on
the
[`card.elevate_limit.succeeded`](/card-issuance/v1.6/webhooks/card-elevate-limit)
or
[`card.elevate_limit.failed`](/card-issuance/v1.6/webhooks/card-elevate-limit)
webhook for the terminal outcome.
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.
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.
````