> For the complete documentation index, see [llms.txt](https://card.payprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://card.payprotocol.io/crypto-basics-for-card-users/editor.md). # What is Paycoin (PCI)? ### What is Paycoin (PCI)? **Paycoin (PCI)** is a blockchain-based digital currency developed by **PayProtocol**, designed to be used for everyday payments in a fast, secure, and user-friendly way. Unlike many other cryptocurrencies that are often held as speculative assets, Paycoin is optimized for **real-world usage**, allowing users to spend PCI at affiliated merchants and within the PayProtocol ecosystem. #### 🔹 Key Features of PCI * **Fast Transactions**: PCI enables near-instant payments on-chain and through integrated services. * **Stable Utility**: Designed to reduce volatility and encourage everyday usage. * **Wide Usability**: Use PCI with the **Payprotocol Card** in physical stores, online platforms, and across various partner services. * **Blockchain Transparency**: Every PCI transaction is recorded on a secure, immutable ledger. #### 🔹 PCI within the PayProtocol Ecosystem The PayProtocol network connects merchants, users, and service providers, making PCI a **payment bridge** between blockchain technology and traditional commerce. Whether you're paying for coffee, shopping online, or transferring funds to a friend, PCI is designed to make digital payments simple and efficient. *** --- # 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://card.payprotocol.io/crypto-basics-for-card-users/editor.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.