> 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/linking-to-mobile-payments/troubleshooting-wallet-linking.md).

# Troubleshooting Wallet Linking

### Troubleshooting Wallet Linking

If you're having trouble adding your PayProtocol Card to a mobile wallet (Apple/Google/Samsung Pay), try the following solutions:

***

#### 🔧 Common Fixes

* Ensure your device’s **region and language** match the wallet service.
* Make sure your PayProtocol **Card is active** and not frozen.
* Restart your phone and try again.
* Update both the wallet app and the PayProtocol app.

***

**🔐 Security Verification**

* During online purchases, you may need to provide a **one-time password (OTP)** sent to your registered email (3D Secure verification).
* If your card was blocked due to suspicious activity, you'll need to unblock it through the app.
* Note that block/unblock actions may lock further status changes for 24 hours.

***

#### 📞 Still Not Working?

* Contact customer support through the PayProtocol app.
* Provide:
  * Phone model and OS version
  * Screenshot of the error
  * Your card’s last 4 digits (never share full number)

***

> 🛡️ Linking usually takes just a few seconds — persistent issues can often be fixed by reinstalling or updating apps.


---

# 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/linking-to-mobile-payments/troubleshooting-wallet-linking.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.
