> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/emv-inside-emv/troubleshooting-emv/an-inserted-card-is-refused-or-declined.md).

# An Inserted Card is Refused or Declined

1. If an inserted card is refused or declined before the amount confirmation, see Using EMV: Transaction Steps.

a. The chip-read itself could have failed.

This can be tested by inserting a card with the “chip side out”. This guarantees a chip-read error. If the response is the same, the issue may be a chip-read failure. Attempt a chip-read with the card on another PIN pad to isolate and determine if the PIN pad or the card is bad.

b. The issue may be that no matching AIDs were found between the card and the terminal.

Is this a foreign card?

c. The Card table may not contain an entry for this card. Confirm with the Table Owner that they accept the card.

2. If an inserted card is refused or declined after the amount confirmation,

a. The Host authentication could have failed. Check for a response code indication.

b. The Host is unavailable and no stand-in was done. Verify AID Stand-In configuration logic.

c. The card may have been removed prior to completing the transaction. EMV processing will decline a transaction, even after host approval, if the terminal and the card cannot communicate after host approval. This is the Complete EMV 2nd Gen AC in the transaction steps. Confirm that the card remains firmly in the reader slot until instructed to remove it.

d. Confirm there are no expired CAPKs present in the system. If there are expired CAPKs present in the system, perform a PDL or Table Download, as appropriate for the FEP.

e. There is a possibility that the chip has failed.


---

# 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://commanderhelp.verifone.com/feature-references/features-and-products-references/emv-inside-emv/troubleshooting-emv/an-inserted-card-is-refused-or-declined.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.
