Amadis

Amadis One - Architecture & integration points

Merchant application

The Amadis One SDK provides two interfaces:

  • The Secure Client API (secclt module) that allows the merchants app to provision and control the attestation and monitoring, keys and configuration update, and PIN entry.

  • The Agnos API (agnos module - OLA) that provides payment transaction features.

Notes:

  • The Secure Client maintains its own connection with its backend. The system administrator must provide the required connection and authentication parameters to the SDK provisioning API.

  • The Secure Client API and Agnos API are independent. If an online PIN verification is required, the L3 module is responsible for invoking the secure PIN entry API and send the resulting cryptogram to its servers.

Secure Backend

The Secure backend provides the following interfaces:

  • The Secure Backend REST API is meant to be used only by the Secure Client and must be accessible from the internet.

  • The administration REST API allows performing administration operations such as:

    • Managing device models.

    • Adding devices to the system.

    • Registering users.

  • The remediation REST API allows the incident and fraud detection console operator to trigger an application specific remediation action in a specific application instance.

The Secure Backend consumes the following interfaces:

  • The security incidents notification interface that sends the details of possible security issues detected in the deployed merchants’ applications.

  • The cryptographic provider interface that exposes the cryptographic operations required by the Secure Backend.

Â