> 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/openapi.md).

# Why Use Crypto for Payments?

### Why Use Crypto for Payments?

As digital currencies like **Paycoin (PCI)** gain mainstream attention, more people are discovering the **practical benefits** of using crypto for daily payments.

#### 🔹 Top Reasons to Use Crypto

* **Lower Fees**: Avoid high banking or credit card fees, especially for cross-border payments.
* **Faster Settlements**: Crypto transactions settle quickly, often in seconds.
* **Financial Freedom**: No need for banks or credit checks. Anyone with a smartphone can participate.
* **Enhanced Security**: Blockchain protects against fraud and unauthorized access.
* **Ownership and Control**: You hold your own money, not a bank.

#### 🔹 Real-World Use with PayProtocol  Card

With the PayProtocol **Card**, you can:

* Spend PCI at real stores and online
* Link to Apple Pay, Google Pay, or Samsung Pay
* Check usage and reload instantly via the app

This means you enjoy **crypto’s flexibility with the ease of a regular payment card**.

***


---

# 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/openapi.md?ask=<question>&goal=<user_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.
