> For the complete documentation index, see [llms.txt](https://docs.neox.vn/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neox.vn/docs/virtual-card/virtual-cards.md).

# Virtual Card Management

**Virtual Card Policy Management APIs** provide the foundational programmatic interfaces for **defining, configuring, and managing the rules and parameters that govern the issuance and usage of virtual payment cards**. These APIs are the control center, allowing businesses and financial institutions to establish granular policies that dictate how virtual cards behave across their lifecycle.

By integrating with these APIs, organizations can:

* **Establish Granular Spending Controls:** Define precise limits on transaction amounts, frequencies, and specific merchant categories (MCCs) to prevent unauthorized spending and ensure financial compliance.
* **Configure Card Issuance Parameters:** Set rules for the automatic activation of new cards upon creation, specify maximum card limits, and determine expiry dates.
* **Automate Lifecycle Management:** Programmatically set conditions for a virtual card's state, including options for automatic closure or deactivation based on predefined criteria.
* **Define Usage Restrictions:** Implement broad or specific rules such as allowing or disallowing transactions for certain merchant groups, and setting minimum/maximum transaction values.
* **Streamline Policy Enforcement:** Ensure that every virtual card issued adheres strictly to the pre-configured rules, maintaining consistent control and reducing manual oversight.
* **Manage Policy Versions (DEVELOPING):** Update and revise policies over time, with mechanisms to track changes and apply new rules to existing or future virtual card programs.

In essence, **Virtual Card Policy Management APIs** will empower you to build a robust and highly adaptable framework for your virtual card program, ensuring that every card operates within the boundaries you define for security, control, and efficiency.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.neox.vn/docs/virtual-card/virtual-cards.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.