Amadis

C-5/JCB Kernel Settings

Owned by Seyhmus Cacina (Unlicensed)
Last updated: Oct 01, 2021 by Berkay Gurcan (Unlicensed)
2 min read

All payment applications registered onto Agnos Framework’s entry point are initialized with tags values present in ENTRY_POINT file (see DF0F). For some tags, if missing, then the following default values are applied to JCB kernel.

Default Values Set

Default Values Set

Tag

Description

Value

9F52

Terminal Compatibility Indicator

00

9F1A

Terminal Country Code

0000

9F33

Terminal Capabilities

606008

DF2D

Message Hold Time (100 of ms)

00000D

DF20

TAC Default

9040008000

DF21

TAC Denial

0410000000

DF22

TAC Online

9060009000

DF1B

Kernel Configuration where:
Byte1 (reflects Combination Options):
→ b8: RFU
→ b7: Status Check Supported
→ b6: ODA Supported
→ b5: Exception File Supported
→ b4: Random Transaction Selection Supported
→ b3: MagStripe Mode Supported (see here)
→ b2: EMV Mode Supported (see here)
→ b1: Legacy Mode Supported (see here)
Byte2 (reflects Combination Options):
→ b8..b1: RFU
Byte3:
→ b8: On Device CVM
→ b7: Transit Reader Supported
→ b6: Issuer Update Supported
→ b5..b3: RFU
→ b2: Do Not Display PROCESSING message → b1: TVR with Online Pin for Legacy

6B0080

DF1C

Max Lifetime Torn Transaction(s)

003C

DF1D

Torn Depth

01

9F53

Terminal Interchange Profile (Synthetic Tag Calculated at Run Time)

function(9F33, DF1B)

Clarification on Transaction Modes

JCB requires that v1.5 compliant kernels always support Legacy and EMV modes, but never support Mag-stripe mode. Thus, Byte1 bits b1, b2 and b3 of DF1B should be set to 1, 1 and 0, respectively.

(Our kernel code has been updated to disable magstripe mode, meaning Byte1 b3 of DF1B isn’t actually processed by the kernel. It continues to be processed by versions < 1.5.)