> For the complete documentation index, see [llms.txt](https://docs.apacx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apacx.io/powercard/powercard/core-capabilities.md).

# Core Capabilities

### Multi-Currency Top-Up Support

PowerCard supports major stablecoins such as USDT, USDC, and PHT as funding assets. Enterprises can configure which tokens to accept based on their operational needs. All top-up amounts are converted into the designated spending currency (e.g., fiat balance) at real-time exchange rates and can be used immediately for global payments. The top-up process is highly flexible, supporting direct wallet transfers, third-party token payment gateways, API-based disbursements, and internal Web3 system integration, enabling seamless funding across various business architectures.

### Isolated User Funds & Controlled Spending

PowerCard operates on a prepaid model, meaning users can only spend within their loaded balance, eliminating credit risk. Enterprises can define card-specific spending controls such as transaction limits, daily/monthly caps, and usage categories to ensure tighter budget management. Funds are held in segregated accounts, maintaining clear separation between enterprise and user assets. Comprehensive financial reports and transaction logs are available for download to facilitate internal reconciliation and audits.

### Global Payment Acceptance

Backed by licensed payment institutions, PowerCard is fully integrated with the global Visa and Mastercard networks, supporting both online and in-store transactions across over 200 countries and regions. Whether used on e-commerce platforms, subscription services, point-of-sale terminals, restaurants, or transportation, PowerCard ensures seamless global payment experiences. Built-in foreign exchange and cross-currency processing mechanisms guarantee smooth, cost-efficient transactions, making it ideal for international use cases.

### Virtual & Physical Card Options

PowerCard enables enterprises to issue both virtual and physical cards, tailored to diverse geographic and payment scenarios. Virtual cards are suitable for instant issuance, online transactions, and mobile integration, while physical cards are optimized for everyday offline purchases, travel, and frequent cross-border use. Both types are managed through a unified backend system that supports batch issuance, funding, and transaction tracking, improving operational scalability and control.

### API / SDK Integration

PowerCard offers easy-to-use APIs and SDKs that allow enterprises to embed card issuance, funding, risk controls, and billing management directly into their own systems. This integration is ideal for companies with custom frontends, wallet apps, platform products, or Web3 infrastructure services. Through programmable interfaces, businesses can automate user onboarding, KYC data submission, card provisioning, and balance updates—without the need to build a full payments stack—enabling rapid deployment of tailored payment solutions.

<br>


---

# 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.apacx.io/powercard/powercard/core-capabilities.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.