> For the complete documentation index, see [llms.txt](https://developer.siteminder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.siteminder.com/smx-api/additional-resources/reference-tables/strong-customer-authentication-codes.md).

# Strong Customer Authentication Codes

Lists codes for authentication types required for secure transactions.

### Electronic Commerce Indicator

<table><thead><tr><th width="130">Value</th><th>Definition</th></tr></thead><tbody><tr><td>02 or 05</td><td>Fully Authenticated Transaction</td></tr><tr><td>01 or 06</td><td>Attempted Authentication Transaction</td></tr><tr><td>00 or 07</td><td>Non 3-D Secure Transaction</td></tr><tr><td>02, 01, 00</td><td>Mastercard</td></tr><tr><td>05, 06, 07</td><td>Visa</td></tr><tr><td>05, 06, 07</td><td>Amex</td></tr><tr><td>05, 06, 07</td><td>JCB</td></tr><tr><td>05, 06, 07</td><td>Diners</td></tr></tbody></table>

### Transactions Status Result Identifier

<table><thead><tr><th width="133">Value</th><th>Definition</th></tr></thead><tbody><tr><td>Y</td><td>Successful Authentication</td></tr><tr><td>N</td><td>Failed Authentication</td></tr><tr><td>U</td><td>Unable to Complete Authentication</td></tr><tr><td>A</td><td>Successful Attempts Transaction</td></tr><tr><td>B</td><td>You can proceed to authorisation using the information received</td></tr><tr><td>R</td><td>Authentication Rejected (Merchant must not submit for authorisation)</td></tr></tbody></table>

### Transaction Signature Status

<table><thead><tr><th width="134">Value</th><th>Definition</th></tr></thead><tbody><tr><td>Y</td><td>Indicates that the signature of the PARes has been validated successfully and the message contents can be trusted.</td></tr><tr><td>N</td><td>Indicates that the PARes could not be validated. This result could be for a variety of reasons; tampering, certificate expiration, etc., and the result should not be trusted.</td></tr><tr><td>null</td><td>If not sent then null</td></tr></tbody></table>

### Status of Authentication

<table><thead><tr><th width="136">Value</th><th>Definition</th></tr></thead><tbody><tr><td>Y</td><td>Yes, Bank is participating in 3-D Secure protocol and will return the ACSUrl</td></tr><tr><td>N</td><td>No, Bank is not participating in 3-D Secure protocol</td></tr><tr><td>U</td><td>Unavailable, The DS or ACS is not available for authentication at the time of the request</td></tr><tr><td>B</td><td>Bypass, Merchant authentication rule is triggered to bypass authentication in this use case</td></tr></tbody></table>


---

# 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://developer.siteminder.com/smx-api/additional-resources/reference-tables/strong-customer-authentication-codes.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.