# API Get Detail Card Policy

#### Endpoint: GET /v2/vc/virtual-card-policies/{requestId}

#### Description:

## Request

#### Request Body Field Descriptions

| Field Name | Type | Required | Description                               |
| ---------- | ---- | -------- | ----------------------------------------- |
| N/A        | N/A  | N/A      | GET request does not require a JSON body. |

#### Request sample

```json
// No request body required for this GET endpoint.
```

### Response

#### Response Field Descriptions

| Field Name    | Type   | Description                        |
| ------------- | ------ | ---------------------------------- |
| code          | number | Response code                      |
| state         | number | State of the response              |
| data          | object | Details of the virtual card policy |
| message       | string | Response message                   |
| neoResponseId | string | Unique Neo response identifier     |

#### `data` object fields:

| Field Name        | Type    | Description                                |
| ----------------- | ------- | ------------------------------------------ |
| requestId         | string  | Unique request identifier                  |
| merchantCode      | string  | Merchant code                              |
| name              | string  | Name of the policy                         |
| cardBrand         | string  | Card brand (e.g., visa)                    |
| expiryDate        | string  | Expiry date (YYYY-MM)                      |
| cardCurrency      | string  | Card currency                              |
| cardLimit         | number  | Card limit (*in currency*)                 |
| minTransAmount    | number  | Minimum transaction amount (*in currency*) |
| maxTransAmount    | number  | Maximum transaction amount (*in currency*) |
| activeOnCreate    | boolean | Whether active on creation                 |
| autoCloseCard     | boolean | Whether card auto closes                   |
| supportedMccGroup | array   | Supported MCC groups                       |
| isActive          | boolean | Whether the policy is active               |
| revision          | number  | Revision number                            |
| createdAt         | string  | Creation timestamp (ISO 8601)              |
| createdBy         | string  | Creator's email                            |
| updatedAt         | string  | Last update timestamp (ISO 8601)           |

#### Response sample

```json
{
  "code": 1,
  "state": 2,
  "data": {
    "requestId": "e424ae34-5c56-45c8-882e-98c4325981d3",
    "merchantCode": "COLRLC",
    "name": "DMD TEST CHINH SACH THE AO CHO MASTERCARD",
    "cardBrand": "visa",
    "expiryDate": "2028-12",
    "cardCurrency": "USD",
    "cardLimit": 30000000,
    "minTransAmount": 10000,
    "maxTransAmount": 20000000,
    "activeOnCreate": true,
    "autoCloseCard": false,
    "supportedMccGroup": [
      "9405",
      "8011"
    ],
    "isActive": true,
    "revision": 1,
    "createdAt": "2025-06-04T09:34:25.959Z",
    "createdBy": "sony@gmail.com",
    "updatedAt": "2025-06-04T09:34:25.959Z"
  },
  "message": "Successful",
  "neoResponseId": "ed849a63-1ffb-4032-b200-0548e53e2c08"
}
```

## Example cURL

```bash
curl -X GET "https://{base_url_openapi}/v2/vc/virtual-card-policies/e424ae34-5c56-45c8-882e-98c4325981d3" \
  -H "Authorization: Bearer <YOUR_TOKEN>" \
  -H "accept-language: en"
```

### Notes

* Requires Bearer token in the Authorization header.
* The Accept-Language header can be used to specify the response language (Support: "vi", "en").
* No request body required.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.neox.vn/docs/global/virtual-card/virtual-card-policies/get-detail-virtual-card-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.