Welcome to the Getting Started guide for the BankAxept DES Issuer API.

This text is intended to give both clear descriptions and guidance for integrators and consumers of DES. It includes an overview of all critical features as well as some general hints of how to utilize this platform.

Introduction

DES (Digital Enablement Service) Issuer API (EPP) is a Tokenization and Life Cycle Management (LCM) system delivered by BankAxept. It is passed on synchronous calls between systems, consisting of the DES Issuer API as well as an expected Issuer side API for receiving callbacks from the DES system.

Setting up your DES integration

There are multiple points of configuration that need to be aligned before you can fully utilize the DES Issuer API. The necessary steps may be found in our Onboarding Guide.

Integration Guidelines

TID (Trace Identifier)

All requests must be done using a TID. This is a unique identifier for each request, and must be included in the header of each request. We recommend using a robust UUID generator for this. For example, UUIDv4.

ProcessId

Is used in enrolment. Must be provided as part of all subsequent API calls to or related to the same enrolment session.

Timestamps

All timestamps must be in UTC and in ISO8601 format YYYY-MM-DDThh:mm:ss. We recommend using a library for this, as it is crucial not to make mistakes with timestamps.

Checklist before going live.

Token states.

Here is an overview of all the accepted state change for a token:

The Card is always considered in an active state by DES, also when the card is Deleted. This is since the issuers are handling the card state while DES is only handling the token state.

Terminology

See our Dictionary for a list of terms used in the BankAxept ecosystem.

Response Codes

The following response codes are used in the API. These might be changed or expanded in the future.