> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/credentials/mobile-connect/troubleshoot/mobile-connect-04-apple-pay-coming-up.md).

# Apple Pay appears when presenting an iPhone to a reader

Prevent Apple Pay from opening when an iPhone is presented to a Mobile Connect reader.

**Cause:** close proximity to the reader initiates an NFC transaction, which triggers Apple Pay.

### Options

1. **Disable Apple Pay.** Not likely to be acceptable to the user.
2. **Instruct iOS users not to bring the phone so close to the reader.** Close proximity initiates the NFC transaction. This may require increasing the Auto Connect range.

> **Do not** disable NFC for the entire site via Server Properties under the Mobile Connect Settings tab. This does not prevent Apple Pay triggering. Even with all reader technologies disabled, Apple Pay will still be triggered by proximity. Disabling site NFC is a non-solution.

***

🔗 **Related**

* [Reader BLE Calibration](/knowledge-hub/products/cc-hardware/credentials/mobile-connect/mobile-connect-reader-ble-calibration.md). Adjust auto connect and manual connect ranges.


---

# 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://help.security.gallagher.com/knowledge-hub/products/cc-hardware/credentials/mobile-connect/troubleshoot/mobile-connect-04-apple-pay-coming-up.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.