Amadis

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

AgnosTVR

See Agnos TVR Bitmap page.

Kernel Processing States

As per implementation pattern, each Agnos CL kernel is ruled by a state machine. Following tables present all states related to each CL kernel,

C-2/Mastercard

This kernel is ruled by the following state machine:

Kernel Processing States

State

Value

Definition

psNone

0

Init

psState1

1

Idle

psState2

2

Waiting For PDOL Data

psState3

3

Waiting For GPO Response

psStateR1

4

Waiting For Exchange Relay Resistance Data Response

psState3R1

5

States 3, R1, Common Processing

psState4

6

Waiting For EMV Read Record Response

psState5

7

Waiting For GET DATA Response

psState6

8

Waiting For EMV Mode First Write Flag

psState456

9

States 4, 5, 6 Common Processing

psState7

10

Waiting For Magstripe Read Record Response

psState8

11

Waiting For Masgstripe First Write Flag

psState78

12

States 7, 8, Common Processing

psState9

13

Waiting For gen AC Response - 1

psState10

14

Waiting for Recover Response AC

psState910

15

States 9, 10 , Common Processing

psState11

16

Waiting For Gen AC Response -2

psState12

17

Waiting For PUT DATA Response Before Gen AC

psState13

18

Waiting For CCC Response - 1

psState14

19

Waiting For CCC Response - 2

psState15

20

Waiting For PUT DATA Response After Gen AC

C-3/Visa

This kernel is ruled by the following state machine:

Kernel Processing States

State

Value

Definition

psNone

0

Init

psState1

1

Idle

psState2

2

GPO

psState3

3

Common Processing

psState4

4

Magstripe

psState5

5

EMV

psState6

6

EMV - Perform Restrictions

psState7

7

EMV - Perform DDA

psState8

8

EMV - Perform SDA TTIG

psState9

9

EMV - Perform CVM

psState10

10

EMV - DDA TTIG when ODA for Online Authorization

psState11

11

EMV - SDA TTIG when ODA for Online Authorization

psState12

12

GPO 6985

psState13

13

GPO qVSDC-6984

psState14

14

GPO qVSDC-6986

psState15

15

GPO qVSDC-Other

psState16

16

Start D

C-4/American Express

This kernel is ruled by the following state machine:

Kernel Processing States

State

Value

Definition

psNone

0

Init

psState1

1

Idle

psState2

2

Waiting For GPO Response

psState3

3

Common Processing

psState3b

4

CVM Specific - Extracted From State3

psState3c

5

TRM Specific - Extracted From State3

psState6

6

Waiting for Gen AC Response

psState4

7

Magstripe Start D

psState5

8

EMV Start D

C-5/JCB

This kernel is ruled by the following state machine:

Kernel Processing States

State

Value

Definition

psNone

0

Init

psTransactionInitialisation_a

1

psStateRecovery

2

psTransactionInitialisation_b

3

psStateInitiateApplicationProcessing

4

psStateReadApplicationData

5

psStateTerminalRiskManagement

6

psStateProcessingRestrictions

7

psStateTerminalActionAnalysis

8

psStateCompletionEMVMode_a

9

psStateCompletionEMVMode_b

10

psStateCompletionMastripeMode

11

psStateCompletionLegacyMode

12

psStateIssuerUpdateProcessing

13

C-6/Discover

This kernel is ruled by the following state machine:

Kernel Processing States (DPAS)

State

Value

Definition

psNone

0

Init

psStateIdle

1

psStateInitiateApplication

2

psStateChecksForCDA

3

psStateReadApplicationData

4

psStateOfflineDataAuthentication

5

psStateCardholderVerification

6

psStateProcessingRestrictions

7

psStateTerminalActionAnalysis

8

psStateAfterOnlineRequest

9

psStateIssuerUpdates

10

psFinalOutcome

11

Kernel Processing States (ZIP)

State

Value

Definition

psNone

0

Init

psState1

1

After Initiate

psState2

2

Before GPO

psState3

3

Before Read Application

C-7/CUP

This kernel is ruled by the following state machine:

Kernel Processing States

State

Value

Definition

psNone

0

Init

psState1

1

Idle

psState2

2

TTR

psState3a

3

AAC Case

psState3b

4

ARQC Case

psState3c

5

TC Case

psStateStandardUICSFlow

6

Transit Standard Flow

Gemalto PURE

This kernel is ruled by the following state machine:

Kernel Processing States

State

Value

Definition

psNone

0

Init

1

2

3

4

5

6

7

8

9

10

EFTPOS

This kernel is ruled by the following state machine:

Kernel Processing States

State

Value

Definition

psNone

0

Init

psStateIdle

1

psStateInitiateApplication

2

psStateReadApplicationData

3

psStatePreTerminalActionAnalysis

4

psStateCardActionAnalysis

5

psStateOfflineCAMChecking

6

psStateProcessingRestrictions

7

psStateCardholderVerification

8

psStatePostTerminalActionAnalysis

9

psStateAfterOnline

10

Interac Flash

This kernel is ruled by the following state machine:

Kernel Processing States

State

Value

Definition

psNone

0

Init

psApplicationSelection

1

psRetryChecks

2

PreInitiation

3

psReadApplication

4

psODA

5

psProcessingRestrictions

6

psCVM

7

psTRM

8

psTAA

9

psCompletion

10

Idemia WISE

This kernel is ruled by the following state machine:

Kernel Processing States

State

Value

Definition

psNone

0

Init

psStateIdle

1

psStateInitiateTransactionProcessing

2

psStateReadApplicationData

3

psStateProcessingRestrictions

4

psStateCardholderVerification

5

psStateKernelActionAnalysis

6

psStateOfflineDataAuthentication

7

psStateAfterOnlineProcessing

8

Not Supported Yet

psIssuerScriptProcessing

9

Not Supported Yet

psStateTransactionCompletion

10

Not Supported Yet

Bancomat

This kernel is ruled by the following state machine:

Kernel Processing States

State

Value

Definition

psNone

0

Init

psStateIdle

1

psStateInitiateTransactionProcessing

2

psStateReadApplicationData

3

psStateCardholderVerification

4

psStateProcessingRestrictions

5

psStateOfflineDataAuthentication

6

psStateTerminalActionAnalysis

7

psStateOnline

8

Card Emulation (using AVT, for CL only)

In some debugging situations, it may be useful to be able to replay an EMV transaction without having the corresponding card. Replaying a transaction requires a specific GPI/DEVICE implementation. Make sure that your AVT uses that specific a GPI/DEVICE_REPLAY library having the exact same interface version as GPI/DEVICE_PCSC

Procedure to replay a transaction from ACE:

  a) From ACE, run a transaction with an actual device. Enable all traces, including APDU log
  b) From ACE, do an export
  c) Unzip the export file, and spot the signal file (signals.txt)
  d) In the AVT running directory, copy the signals.txt file, and rename it starting with "CL-" (example: "CL-replay"):
  c) From the AVT/agnos.ini file:
      - Set Replay = yes; (or set that specific mode from TMS/Administrative dialog: **Replay**).
      - Set ReaderCL = name_of_the_file_containing_APDU; Starting with ''CL-''
      - Set CL=yes
  d) From ACE, load the following files exported from ACE in b). This will restore the exact same pre-conditions to run the test case:
      - TRD
      - TERMINAL
      - PROCESSING
      - ENTRY POINT
  e) From ACE/Configuration/ENTRY POINT:
      - Open the contactless combination that will be replayed
      - Or, do step f) for all available combinations
  f) In Other TLVs section within an ENTRY POINT combination configuration, set 9F3704xxxxxxxx with xxxxxxxx set to the value corresponding to the transaction to be replayed
  g) Run the transaction

Trouble shooting:
When replaying CL transactions unsing the AVT, make sure that DOLs are in sync with the APDU traces fetched from the actual transaction execution. GPO, GenAC are - most of the time - the root of dysfunctional replays.

  • No labels