> 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/security-and-card-management/lost-or-stolen-card-guide.md).

# Lost or Stolen Card Guide

### Lost or Stolen Card Guide

If your card is lost or stolen, take the following actions immediately to protect your funds.

***

### Card Blocking

The PayProtocol system may automatically block your card if it detects unusual or suspicious activity. You can check your card status and unblock it directly via the PayProtocol App.

> ℹ️ Card status updates are reflected in real time.

***

### Card Theft

Since PayProtocol cards are virtual, physical theft is not possible. However, if the **private key** linked to your **PayProtocol NFT** is compromised, your card may be misused.

**Action Steps:**

* Immediately transfer all your assets and NFTs to a secure blockchain address.

> ⚠️ If your private key is compromised, both your NFT and the associated card could be at risk.
>
> 💡 Never share your private key with anyone.

***

### Card Data Breach

If you suspect that your card information has been compromised, you should immediately **deactivate (lock)** your card via the PayProtocol App.

* After deactivating or reactivating your card, you must wait 24 hours before making further changes.
* You can change the status again the following day.

After deactivation,\
**you must send an email to the PayProtocol support team to request a card renewal.**

> ⚠️ If a data breach is suspected, promptly lock your card and apply for renewal to prevent further damage.

***

### Card Issuer Information

The PayProtocol MasterCard debit card is issued under the following conditions:

* **Issuer:** SR Saphirstein AG (Switzerland)
* **BIN Number:** 5481 0849

> ℹ️ **BIN (Bank Identification Number)** refers to the first 8 digits of the card number, used to identify the issuing bank.


---

# 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/security-and-card-management/lost-or-stolen-card-guide.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.
