> 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/business-model.md). # Business Model ### Card Issuance Fees Enterprises can choose from **different pricing models based on their issuance volume and operational goals.** For standard collaborations, PowerCard offers a tiered pricing structure—where the per-card cost decreases as issuance volume increases. For long-term or high-volume partners, **a hybrid model with free card issuance + annual service fee** is also available, helping reduce upfront costs while maintaining budget predictability. ### Top-Up Processing Fees All user top-ups are routed through compliant stablecoin channels integrated with PowerCard. A fixed percentage fee per transaction (typically 0.5% to 1%) is applied to cover blockchain network fees, settlement costs, and liquidity routing. Enterprises may choose to absorb this fee or partially pass it on to users, depending on their business model—whether it's for incentive payouts, task-based rewards, or self-funded reloads. ### Spend-Based Rebate Mechanism Whenever users make purchases through the PowerCard on the Visa or Mastercard networks, a percentage of the transaction amount is returned to the enterprise as a rebate. This rebate is offered by clearing partners or merchant networks and serves as a key monetization channel for enterprises. It is especially well-suited for growth-driven use cases like “spend-to-earn” or “reward-upon-action” programs. ### Customization Fees (Optional) For enterprises seeking advanced brand customization or deeper system integration, PowerCard offers a suite of premium services. These include **custom card design, tailored risk strategies, API/SDK integration support, and operational dashboards**. Fees for these services are charged on a modular basis or based on resource usage, allowing partners to configure the right feature set while maintaining control over cost and deployment scale. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.apacx.io/powercard/powercard/business-model.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.