API Create Card Policy
Endpoint: POST {{url_openapi}}/v2/vc/virtual-card-policies/
POST {{url_openapi}}/v2/vc/virtual-card-policies/
Description:
Create a new Virtual Card Policy for a merchant, specifying card limits, expiry, supported MCC groups, and other policy settings.
Request
Request Body Field Descriptions (JSON)
requestId
string
Yes
Unique request ID (UUID recommended)
name
string
Yes
Name of the virtual card policy
cardBrand
string
No
Card brand ("visa"
, "mastercard"
)
cardCurrency
integer
No
Card currency (Support: "USD"
, "EUR"
, "GBP"
, "SGD"
, "HKD"
, "VND"
). Default: USD
cardLimit
integer
No
Maximum card limit (in currency)
expiryDate
string
No
Card expiry date in format YYYY-MM
minTransAmount
integer
No
Minimum transaction amount (in currency)
maxTransAmount
integer
No
Maximum transaction amount (in currency)
activeOnCreate
boolean
No
Whether the card is active upon creation. Default: false
autoCloseCard
boolean
No
Whether the card should auto-close. Default: false
supportedMccGroup
string[]
No
List of supported Merchant Category Codes (MCC)
Request sample
Response
Response Field Descriptions
code
number
Response code
state
number
State of the response
data
object
Details of the created policy
message
string
Status message
neoResponseId
string
Internal response tracking ID
data
object fields:
data
object fields:requestId
string
Merchant request ID
merchantCode
string
Merchant code
name
string
Policy name
cardBrand
string
Card brand
cardCurrency
string
Card currency
expiryDate
string
Expiry date
cardLimit
number
Card limit (in currency)
minTransAmount
number
Minimum transaction amount (in currency)
maxTransAmount
number
Maximum transaction amount (in currency)
activeOnCreate
boolean
Active on create
autoCloseCard
boolean
Auto close card
supportedMccGroup
string[]
Supported MCC groups
isActive
boolean
Is policy active
extraData
object
Reserved for future use
revision
number
Revision number
createdAt
string
Creation timestamp (ISO 8601)
createdBy
string
Creator's email
Response sample
Example cURL
Notes
Requires Bearer token in the Authorization header.
The Accept-Language header can be used to specify the response language (Support: "vi", "en").
Use a unique
requestId
for each request to avoid duplicate creations.Ensure the MCC codes are valid and supported by your system.
Last updated
Was this helpful?