Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

This API is the second level of integration for Agnos Framework. Hence, It is recommended to unit test all the services below outside the execution of a transaction before starting functional tests.

ACE Services

ACE Services

Description

Prerequisites to a Call

aceInitialize

aceInitializeCommunication

aceSetMode

There are three running modes defined in ACE:

  • pmNONE

  • pmSDK

  • pmAUTO

Use pmSDK for unit testing ACE integration

aceGetMode

Get current ACE mode

--

aceGetRequest

aceSendResponse

aceMsgToACE

aceClearScreen

Clear ACE screen

--

aceDisplayMessage

aceEmptyKeyPadCache

aceLogAPDU

aceLogAllBatchedAPDU

acePlayBeep

Play a beep in ACE

--

aceGetKey

Get key from ACE

--

aceSwitchLED

Switch a LED on ACE

--

aceOut

Out in ACE’s Console Log

Code Block
aceOut("Hello World!"); // Open Console Log under ACE prior the unit test

...

Options Services

This set of primitives is not dependent on the platform. It doesn’t require specific implementation or modification for a given integration. Hence, it works as is.

Trace

Trace = 0 will log APDU commands and responses to ACE

Trace 1 to max = will log commands and reponses to logout and only commands to ACE

Trace > max will log commands and responses offline

Automation

Reserved to Agnos Framework maintenance

Signal

Enable/disable signals display in ACE (in pmSDK mode)

APDULog

Enable/disable APDU logging (in pmSDK mode)

UIDisplay

Enable/disable UI services in ACE from the device

ID Message Display

Enable/disable message display (in signals) along with their message identifier

Digital Signal

Enable/disable digital signals display following standard bitmap as defined by EMVCo