Skip to main content

CompleteDigitalCard

Complete Digital Card used for ApplePay or GooglePay

Once the pending phase is over, more data will be available in the response

type CompleteDigitalCard implements DigitalCard {
  id: ID!
  type: DigitalizationType!
  createdAt: DateTime!
  updatedAt: DateTime!
  walletProvider: WalletProvider!
  device: Device!
  walletId: String
  cardMaskedNumber: String!
  statusInfo: CompleteDigitalCardStatusInfo!
  projectId: ID!
  cardContractId: ID!
}

Fields

`CompleteDigitalCard.id` ● `ID!` non-null scalar

Unique identifier of a digital card

`CompleteDigitalCard.type` ● `DigitalizationType!` non-null enum

The type of digitalization that created this digital card.

`CompleteDigitalCard.createdAt` ● `DateTime!` non-null scalar

Created date

`CompleteDigitalCard.updatedAt` ● `DateTime!` non-null scalar

Updated date

`CompleteDigitalCard.walletProvider` ● `WalletProvider!` non-null object

Wallet Provider (ApplePay, GooglePay ...)

`CompleteDigitalCard.device` ● `Device!` non-null object

Device In case of a wallet application, some information about the device will be provided

`CompleteDigitalCard.walletId` ● `String` scalar

Id of the wallet application. Will not be present for Merchant

`CompleteDigitalCard.cardMaskedNumber` ● `String!` non-null scalar

Masked DPAN with the last four digits visible

This value is present in the user wallet application

`CompleteDigitalCard.statusInfo` ● `CompleteDigitalCardStatusInfo!` non-null interface

Digital Card status information

In this type the status will be either ConsentPending or Pending

`CompleteDigitalCard.projectId` ● `ID!` non-null scalar

The project ID

`CompleteDigitalCard.cardContractId` ● `ID!` non-null scalar

The card contract ID

Interfaces

`DigitalCard` interface

Digital Card used for ApplePay or GooglePay

Fields
Interfaces