Amadis

IFR Processing

What is an EEA CARD?

EEA cards allow cardholders to choose their application of choice, through the different methods in the table below.

How do you know if your card is an EEA card?

If the Application Selection Registered Proprietary Data (ASRPD - 9F0A with valid ID = ‘0001’) is present in the card, then the card is identified as EEA issued.

Currently, Arkos also has the F1 and F0 templates implemented. The EEA-specific process on the candidate list includes the priority settings and exclusions on the candidate list.

You can hardcode your F1 and F0 list currently, as the configurations are not supported on Atheos.

IFR Processing is required in the SEPA Region to allow cardholders to choose their application.

 

Arkos only supports the option with an upfront button during technology selection.

Therefore, bit8 should be activated when IFR Processing is required.

How to configure the upfront button?

static private TlvTree getTableE1(){ TlvTree E1 = null; TlvTree inner = TlvTree.FromRaw(ArkosConfiguration.Get()); TlvTree nexoFastConfig = inner.GetChild(Configuration.NEXO_FAST_CONFIGURATION); if (nexoFastConfig != null) { E1 = nexoFastConfig.GetChild(NexoFastConfiguration.E1_TABLE); } return E1; }

 

static public boolean isUpfrontButtonConfigured(){ TlvTree e1 = getTableE1(); if (e1 == null) { return false; } byte[] eeaProcessSettings = e1.GetElementValue(E1Table.EEA_PROCESS_SETTINGS); return ((eeaProcessSettings[0] & 0x80) !=0); }

 

 

Bit 6 and 5 are not supported since Arkos does not provide support to override selected applications during CVM Process.

 

When a cardholder enters an EEA card with multiple supported applications (for example a CB / Visa card), bit 7 will allow the application to automatically select the highest priority application without prompting for cardholder selection, unless the cardholder requests the choice of application.

It is the recommended default value for the best user experience.

 

When a cardholder presents a contactless EEA card with multiple supported applications (for example a CB Visa card), the application will automatically select the highest priority application without prompting for cardholder selection, unless the cardholder requests the choice of application. Bit 4 and 3 will also not be supported. Awaiting relevant use case to implement it.

 

How to use the Upfront Button

Payment

In the Payment application, ArkosPay in our case, proceeds to the execution of a payment. If we take as a reference point the following Payment Menu as an example, the AID button represents the position of the upfront button.

 

image-20240202-150148.png
Payment Menu

Upon presenting the payment card, the AID button needs to be pressed for the system to take into consideration the multiple supported applications of the Card.

In the following case, the supported applications are MasterCard and Maestro. Select one and proceed to the rest of the payment process.

Expected Results

The CustomerConsent <CstmrCnsnt> attribute is the value displaying if a choice was made in regards to the presented supported applications during the Payment process.

This attribute is located in the Transaction <Tx> section found in the Accepted Authorized Request <AccptrAuthReq>, Cancellation Advice <CxAdv>, Cancellation Request <CxlReq>, and Completion Advice <CmpltnAdvc>.

 

Example:

<AccptrAuthstnReq> <Hdr> ... </Hdr> <AuthstnReq> ... <Tx> ... <CstmrCnsnt>true</CstmrCnsnt> ... </Tx> </AuthstnReq> <SctyTrlr> ... </SctyTrlr> </AccptrAuthstnReq>

 

 

 

 

 

For test purpose

Visa Contactless Multiple Application VISA.Cl.1004

Visa Contact Multiple Application VISA.Cl.0024

Visa Contact Multiple Application with ARSPD (9F0A) ADVT #24

MasterCard Contact Multiple Application with ARSPD (9F0A) M-TIP50

MasterCard Contactless Multiple application with ARSPD (9F0A) COM01/COM02

Â