> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/hardware/card-readers/mms-dyna-devices/dynaflex-ii-ped/documentation/developers-manuals/dynaflex-ii-ped-programmers-manual/device-settings/application-selection-behavior.md). # Application Selection Behavior ## Table - Property 1.2.1.1.1.2 Application Selection Behavior (Contactless Only)Application Selection Behavior


Property Description
Property OID	1.2.1.1.1.2 / 0x010201010102
Name	Application Selection Behavior
Description	The device uses this property to set the device’s application selection behavior for payment brand selection.
Securing Key	None
Min. Len (b)	1
Max. Len (b)	1
Data Type	Binary
Valid Values	0x00 –Card Preference. The device automatically chooses the application that is mutually supported by the card and the terminal, based on the priority order specified by the card. This is the default and is standard EMV transaction flow behavior. 0x01 – Reserved 0x02 – Reserved 0x03 – Enhanced Prompt Cardholder. The device sends the host Notification 0x1803 – 02 02 00 00 (Display Cardholder, Data Attached, Reserved) to request that the cardholder select from a list of available applications. Each application may include additional tags such as - priority indicator, Issuer Country Code and Issuer Identification Number. After the cardholder selects an application, the host passes the selection to the device using Command 0x1802 - Report Cardholder Selection to device to return the cardholder’s selection to the device. Note that if the device is configured to use this option, the cardholder must hold the card or contactless payment device in contact with the device for until cardholder application selection is complete, otherwise the device will report the transaction failed. For this reason, MagTek does not recommend using this setting.
Default	0x00 – Card Preference

## Table - Property 1.2.1.1.1.2 - Get Request Example


Example (Hex)
AA00 8104 0155D101 840F D101 8501 01 8704 02010101 8902 C200

## Table - Property 1.2.1.1.1.2 - Get Response Example

Example (Hex)

AA 00 81 04 82 55 D1 01 82 04 00 00 00 00 84 82 00 10 D1 01 85 01 01 87 04 02 01 01 01 89 03 C2

01 00

## Table - Property 1.2.1.1.1.2 - Set Request Example


Example (Hex)
AA00 81040155D111 8410 D111 850101 870402010101 8903 C20103

## Table - Property 1.2.1.1.1.2 - Set Response Example

Example (Hex)

AA 00 81 04 82 55 D1 11 82 04 00 00 00 00 84 82 00 10 D1 11 85 01 01 87 04 02 01 01 01 89 03 C2

01 03

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://developer.magtek.com/hardware/card-readers/mms-dyna-devices/dynaflex-ii-ped/documentation/developers-manuals/dynaflex-ii-ped-programmers-manual/device-settings/application-selection-behavior.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.