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

# How Crypto Payments Work

### How Crypto Payments Work

Cryptocurrency payments are a **modern alternative to traditional finance**, enabling peer-to-peer transactions without intermediaries like banks or payment processors.

#### 🔹 Basic Payment Flow

1. You hold cryptocurrency (e.g., Paycoin) in your **digital wallet**.
2. When you initiate a payment, the funds are sent directly to the recipient’s wallet address.
3. The transaction is validated and recorded on the **blockchain**.
4. Within seconds to minutes, the transaction is confirmed and cannot be altered.

#### 🔹 Crypto + Payprotocol  Card

When using a Payprotocol **Card**, the process is streamlined:

* You **top up your card** using Paycoin (PCI).
* When making a purchase, the payment is processed **using the balance that has been topped up with PCI.**
* The merchant receives payment in their preferred currency, while you enjoy **crypto-powered convenience**.

#### 🔹 Benefits Over Traditional Payments

* **Global accessibility**: No banking barriers or currency exchange restrictions.
* **Lower transaction fees**: Especially for international or cross-border payments.
* **Privacy and security**: No need to share sensitive banking information.

By combining blockchain efficiency with card usability, crypto payments are entering **everyday life** — securely and seamlessly.

***


---

# 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/markdown.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.
