D1 SDK Documentation

Digital First by Thales enables a ready-to-use digital card to be issued instantly, guaranteeing an enhanced premium experience with the ability to make instant payments online or in-store as soon as the bank account has been created.

Our Digital First (D1) platform provides a set of "ready-to-use" services and tools, allowing the issuers to launch new digital first experiences "Digital First, Physical Later" and "Digital only" in their mobile banking application.

With our D1 platform, issuers can choose from multiple advanced services to drive the best banking and payment experience for their cardholders.

D1 SDK exposes UX level APIs to facilitate the integration of digital services into the issuer mobile banking application, a set of services is provided to enable the management of Virtual Card, Physical Card and the creation of Digital Card.

Before the bank application can use the D1 SDK to provide service to end user, two actions must be taken by the issuer:

• Card Registration: The card(s) issued from the CMS needs to be registered within D1 prior any action taken in the bank application.
• Authorization: D1 SDK needs to take the confirmation from the bank application that the user is authorized to access D1 service. The expectation from D1 is the end user as been authenticated by the bank and be granted to access to a set of D1 services. For more information, please refer to the D1Task.login(byte[], Callback).

Terms of use

All information herein is either public information or is the property of and owned solely by Thales and/or its subsidiaries and affiliates who shall have and keep the sole right to file patent applications or any other kind of intellectual property protection in connection with such information.

Nothing herein shall be construed as implying or granting to you any rights, by license, grant or otherwise, under any intellectual and/or industrial property rights of or concerning any of Thales and any of its subsidiaries and affiliates (collectively referred to herein after as "Thales") information.

This document can be used for informational, non-commercial, internal, and personal use only provided that:

• The copyright notice below, the confidentiality and proprietary legend and this full warning notice appear in all copies.
• This document shall not be posted on any publicly accessible network computer or broadcast in any media, and no modification of any part of this document shall be made.

Use for any other purpose is expressly prohibited and may result in severe civil and criminal liabilities.

The information contained in this document is provided "AS IS" without any warranty of any kind. Unless otherwise expressly agreed in writing, Thales makes no warranty as to the value or accuracy of information contained herein.

The document could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Furthermore, Thales reserves the right to make any change or improvement in the specifications data, information, and the like described herein, at any time.

Thales hereby disclaims all warranties and conditions with regard to the information contained herein, including all implied warranties of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Thales be liable, whether in contract, tort or otherwise, for any indirect, special or consequential damages or any damages whatsoever including but not limited to damages resulting from loss of use, data, profits, revenues, or customers, arising out of or in connection with the use or performance of information contained in this document.

Thales does not and shall not warrant that this product will be resistant to all possible attacks and shall not incur, and disclaims, any liability in this respect. Even if each product is compliant with current security standards in force on the date of their design, security mechanisms' resistance necessarily evolves according to the state of the art in security and notably under the emergence of new attacks. Under no circumstances, shall Thales be held liable for any third party actions and in particular in case of any successful attack against systems or equipment incorporating Thales products. Thales disclaims any liability with respect to security for direct, indirect, incidental or consequential damages that result from any use of its products. It is further stressed that independent testing and verification by the person using the product is particularly encouraged, especially in any application in which defective, incorrect or insecure functioning could result in damage to persons or property, denial of service, or loss of privacy.

Copyright © 2024 Thales. All rights reserved. Thales and the Thales logo are trademarks and service marks of Thales and/or its subsidiaries and affiliates and are registered in certain countries. All other trademarks and service marks, whether registered or not in specific countries, are the property of their respective owners.

The open source licenses and components used by this product can be found in the license folder of the delivery package.

Package	Description
com.thalesgroup.gemalto.d1	This package provides generic structure for D1 features, such as callback, exception, configuration and initialization.
com.thalesgroup.gemalto.d1.authn	The D1 Authn provides convenient and easy APIs within D1 SDK to support EMV 3-D Secure (3DS) flows as defined by EMVCo.
com.thalesgroup.gemalto.d1.card	This package contains the data structure common to both virtual and digital cards.
com.thalesgroup.gemalto.d1.d1pay	With D1 Pay, eligible cards (virtual or physical card previously registered) can be digitized and used to perform contactless payment via NFC using the mobile banking application.