Creates a card and issues it to a cardholder.
Two calling modes are supported:
cardholder_id to issue a card to an existing cardholder. Optionally pass cardholder_required_fields to supplement missing cardholder data required by the card product.cardholder_id and pass a complete cardholder_required_fields block. The system creates the cardholder and the card in a single request. See One-Step Card Issuance for the full integration flow.Documentation Index
Fetch the complete documentation index at: https://developers-sandbox.uqpaytech.com/llms.txt
Use this file to discover all available pages before exploring further.
The API token for login provided by UQPay.
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 endpoint. If omitted or empty, the request is executed using the master account.
More information at Connected Accounts.
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.
The card currency.
SGD, USD, XUSD "USD"
The card product's unique identifier.
"7c4ff2cd-1bf6-4aaa-bf16-266771425011"
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.
For the following BINs, card_limit is required during card creation and must be greater than or equal to 0.01:
For all other BINs, card_limit is optional:
card_limit to 0.x >= 02100.02
The cardholder name shown on the card. When the Secure Iframe 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.
26"MARSHALL HU"
The unique identifier of the cardholder to issue the card to.
Either cardholder_id or a complete cardholder_required_fields block must be provided. When cardholder_id is omitted, the system creates a new cardholder inline using the values in cardholder_required_fields. See One-Step Card Issuance.
"7c4ff2cd-1bf6-4aaa-bf16-266771425011"
Rules that control spending for this card.
User-customized risk control settings.
Supported configurations depend on the card BIN. See [Supported BINs for Risk Control Configurations](/card-issuance/v1.6/guide/Supported BINs for Risk Control Configurations) for details.
Any key-value object. Max length = 3200 bytes. This must be valid JSON data.
{ "key1": "value1", "key2": "value2" }Indicates whether the card is a standard reusable card or a one-time-use card.
NORMAL - A standard card that can be used for multiple transactions.ONE_TIME - A one-time-use card that is automatically cancelled after the first transaction event defined
by auto_cancel_trigger.NORMAL, ONE_TIME "NORMAL"
Defines the transaction event that triggers automatic cancellation of a ONE_TIME card. Required when usage_type is ONE_TIME.
ON_AUTH - The card is cancelled immediately after the first authorization is approved. Subsequent authorization
requests on the same card will be declined.ON_CAPTURE - The card is cancelled after the first transaction's capture (settlement) succeeds, allowing
a full authorization and capture cycle to complete.ON_AUTH, ON_CAPTURE "ON_AUTH"
The absolute expiry date and time of the card. If the card has not been cancelled by a first-transaction event before this time, it is automatically cancelled and any unused balance is released.
"2026-03-19T18:46:43+08:00"
Cardholder information supplied at card creation time.
cardholder_id provided): optional; fields supplied here are used to supplement missing cardholder data before the card is issued.cardholder_id omitted): required and must contain a complete set of cardholder-creation fields (email, first_name, last_name, country_code, phone_number). The system creates the cardholder inline.Card creation successfully.
Unique identifier for the card.
"c0cef051-29c5-4796-b86a-cd5b684bfad7"
ID of the card order.
"c0cef051-29c5-4796-b86a-cd5ee34bfad7"
Create time at which the object was created.
"2024-03-21T17:17:32+08:00"
Card status enum. See the Card lifecycle and statuses guide for more information.
PENDING, ACTIVE, FROZEN, BLOCKED, CANCELLED, LOST, STOLEN, FAILED "ACTIVE"
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.PENDING, PROCESSING, SUCCESS, FAILED The risk control settings applied to the card. Echoed from the request, or populated from the card product defaults when not supplied.
The cardholder's unique identifier. In one-step mode, this is the newly-created cardholder — save this value to reference the cardholder later.
"7c4ff2cd-1bf6-4aaa-bf16-266771425011"
true when a new cardholder was created inline as part of this request. Omitted otherwise.
true
The cardholder's status.
FAILED, PENDING, SUCCESS, INCOMPLETE The KYC verification outcome for the cardholder. Returned when supplement fields triggered KYC processing.
VERIFIED, UNDER_REVIEW, ACTION_REQUIRED "UNDER_REVIEW"
Echoes the KYC verification method that was applied. Returned when cardholder_required_fields.kyc_verification was supplied in the request.
THIRD_PARTY - Merchant-supplied KYC proof was used.SUMSUB_REDIRECT - The cardholder is redirected to Sumsub to complete IDV.THIRD_PARTY, SUMSUB_REDIRECT "SUMSUB_REDIRECT"
The IDV verification URL the cardholder must visit to complete identity verification. Returned only when kyc_method is SUMSUB_REDIRECT.
"https://in.sumsub.com/websdk/p/sbx_4dwsbDuDbpJsMgou"
The expiry time of idv_verification_url. Returned only when kyc_method is SUMSUB_REDIRECT.
"2026-04-25T17:26:50+08:00"
Informational message when card creation is blocked or pending due to KYC requirements (e.g., insufficient KYC, missing fields).