Terminal Configuration & Deployment

This page provides the complete terminal configuration reference for deploying ColossusNet on EMVCo Level 1/2/3 certified POS terminals. These parameters must be loaded into the terminal's configuration before it can process ColossusNet transactions.

ColossusNet AID Configuration

The Application Identifier (AID) configuration tells the terminal how to recognize and process ColossusNet cards.

TAC Configuration Explained

The Terminal Action Codes (TAC) work together with the card's Issuer Action Codes (IAC) to determine transaction outcomes:

• TAC Denial (0010000000): Minimal denial conditions. The terminal will only deny offline if the ICC Data Missing bit is set.
• TAC Online (D84004F800): Aggressively forces online authorization. Any ODA failure, expired application, or risk management trigger pushes the transaction online.
• TAC Default (D84000A800): If online authorization is not possible, these conditions determine whether to decline. Combined with the card's IAC settings, this ensures no offline approvals occur.

The Floor Limit = 0 setting means every transaction, regardless of amount, requires online authorization. The Threshold, Target Percentage, and Max Target Percentage are all zero because random transaction selection for online processing is unnecessary; all transactions go online by design.

DDOL and TDOL

The Terminal Default DDOL (9F3704) specifies that the Unpredictable Number (4 bytes) is sent to the card for the INTERNAL AUTHENTICATE command.

The Terminal Default TDOL (9F02065F2A029A039C0195059F3704) specifies the data elements the terminal provides during transaction processing:

ICS Configuration: Type 1 (Attended, All CVM)

The Integrated Circuit card Specification (ICS) configuration defines the terminal's capabilities for contact chip transactions.

Key Configuration Notes

• Terminal Type 22 indicates a merchant-attended terminal capable of both online and offline operation. Although offline approval is never granted for ColossusNet cards, the terminal type must advertise offline capability so the EMV flow proceeds normally through ODA before being forced online.
• Card Data Input Capability 20 restricts the terminal to IC (chip) only. Magnetic stripe fallback is not supported.
• CVM Capability 00 indicates no cardholder verification methods are required at the terminal level. CVM processing is handled by the card's CVM List.
• Security Capability 40 indicates DDA support only. SDA and CDA are not used.
• Forced Online Capability = Yes is critical. This ensures the terminal can force transactions online when TAC/IAC conditions are met (which they always are for ColossusNet, due to the deliberate ODA failure).

CAPK Entry

The Certification Authority Public Key (CAPK) is used by the terminal to verify the issuer's public key certificate during offline data authentication. Although ODA always fails by design (because the card produces ECDSA signatures instead of RSA), the CAPK must still be present for the terminal to attempt ODA at all.

The CAPK RID (A000000951) matches the ColossusNet Registered Application Provider Identifier. The Key ID 92 is referenced by the card's CAPK Index field (Tag 8F). The RSA modulus and checksum values are deployment-specific and omitted from this reference.

Contactless Configuration: payWave

Contactless parameters for the ColossusNet AID matching the Visa payWave (Kernel C-3) configuration pattern:

Contactless Limits

• CVM Limit = 0 means no cardholder verification is required at any amount. CVM processing is handled through the contactless CVM flow (CDCVM or Online PIN if applicable).
• Transaction Limits = 9999999 ($99,999.99) are effectively unlimited. All authorization decisions are made on-chain, not at the terminal.
• Floor Limit = 0 forces every contactless transaction online. No offline contactless approvals are permitted.

Kernel Configuration Byte (DF8101 = 0xB0)

The kernel configuration byte controls Kernel C-3 behavior:

CVM Capabilities

• CVM Required (60): Enciphered PIN online + Signature. When a CVM is required (amount above CVM limit, which is $0.00 in this configuration), the terminal supports online PIN and signature.
• No CVM Required (08): No CVM. When no CVM is required, the transaction proceeds without cardholder verification.

Network Parameters

Supported Stablecoins

The terminal uses standard EMV currency codes. The EMVSettlement contract automatically maps the transaction's currency code (tag 5F2A, ISO 4217) to the corresponding ERC-20 token. Token selection is an acquirer-level configuration; no terminal-side changes are required.

See Smart Contracts for the full list of supported stablecoins.

Source code