EMV Digital Payment Credential Specification - Schema Framework - v1.0 DRAFT: Comment Period ends 6-March 2026

EMV® Digital Payment Credential Specification Schema Framework Version 1.0 Draft 18 February 2026 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® Digital Payment Credential Schema Legal Notice Draft Legal Notice The EMV® Specifications are provided “AS IS” without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in these Specifications. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT, AS TO THESE SPECIFICATIONS. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to the Specifications. EMVCo undertakes no responsibility to determine whether any implementation of the EMV® Specifications may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, knowhow, or other intellectual property rights of third parties, and thus any person who implements any part of the EMV® Specifications should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, the Specifications may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement these Specifications is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology. EMVCo shall not be liable under any theory for any party’s infringement of any intellectual property rights in connection with the EMV® Specifications. © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® Digital Payment Credential Specification Contents Contents Legal Notice ............................................................................................................. i Contents .................................................................................................................. ii Tables ..................................................................................................................... iii 1 Executive Summary .......................................................................................... 4 2 Purpose and Scope........................................................................................... 5 2.1 Purpose...................................................................................................... 5 2.2 Scope ......................................................................................................... 5 3 Use-Cases.......................................................................................................... 6 4 Participants and Roles...................................................................................... 7 5 Definition of Data Elements .............................................................................. 8 5.1 Data Element Attributes.............................................................................. 8 5.2 Account related Data Elements .................................................................. 9 5.3 Credential Related Data Elements............................................................ 10 5.4 Payment Request Data Elements............................................................. 11 5.4.1 Payment Details............................................................................ 11 5.4.2 Credential Query........................................................................... 13 6 Security and Privacy Considerations ............................................................ 15 18 February 2026 Draft v1.0 Page ii © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® Digital Payment Credential Specification Tables Tables Table 5.1: Account related data elements ................................................................ 9 Table 5.2: Credential related data elements ........................................................... 11 Table 5.3: Payment request data elements ............................................................ 12 Table 5.4: Credential Query Data Elements ........................................................... 13 18 February 2026 Draft v1.0 Page iii © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV Digital Payment Credential Specification Schema Framework v1.0 Page 4 / 17 1 Executive Summary Verifiable Digital Credentials – VDCs are a cryptographically verifiable, digital representation of a credential or attributes secured in a dedicated application, often referred to as a digital wallet. VDCs come in many forms including government credentials (e.g., driver’s licenses), proof of certain personal characteristics or attributes (e.g., age over 21). VDCs can be presented both online and in-person. Source: nist.gov The structure and application of a Verifiable Digital Credential vary according to the specific use case for which the credential is requested and verified. For the purposes of Remote Commerce Payments, the Verifiable Digital Credential would be used as a Digital Payment Credential [DPC] that will allow the issuer of the credential to tie the credential to a payment instruments and verify it when the consumer presents the credential at the time of a remote commerce transaction. DPC is envisioned to enable interoperability across payment networks, wallets, and verification systems, while supporting privacy controls such as selective disclosure. Interoperability across these different components would be enabled through an extensible schema that allows common interpretation of data elements when it relates to a transaction. 18 February 2026 Draft v1.0 Page 4 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV Digital Payment Credential Specification Schema Framework v1.0 2 Purpose and Scope Page 5 / 17 2.1 Purpose While there are different standards for verifiable digital credentials and how they operate in terms of presentation and verification, EMVCo is looking to create a specific framework for use of such credentials [DPC] for the purposes of application in Remote Commerce usecases. This document serves as a framework from EMVCo describing data elements that could constitute a Digital Payments Credential that will be applicable in most Payments use-cases where strong consumer authentication is required. 2.2 Scope This document defines the list of data elements and provisional schema with an objective to: 1. Describe the Digital Payment Credential issued by the Credential Issuer into the Digital Wallet 2. Describe the Payment Details supplied by the Credential Verifier so the wallet can apply credential selection rules and display an accurate payment sheet on the user interface. The data element schema enables the interoperability between the participants listed below, delivering the following benefits to each participant: • Credential Issuer can issue Digital Payment Credentials to all compliant Digital Wallets. • Credential Holder (or Digital Wallet) knows how to handle standard Digital Payment Credentials and implements both credential provisioning and credential request processes. • Credential Verifier knows how to request the credential and verify the presentation request. While Digital Payment Credential represents the generic concept that may apply to any payment instrument, this document focuses on the definition of credential specific to the payment card. This document defines generic, data-format-neutral schema definitions for Digital Payment Credentials. It is designed to be abstract and suitable across multiple representation formats and protocols, including ISO mDoc (mobile Document), W3C VC (Verifiable Credential) and SD-JWT (Selective Disclosure-JSON WebToken) data models, along with communication frameworks like OIDC-based and defined by the ISO/IEC 18013-7 specification. This flexibility ensures that the schema can be adopted in diverse ecosystems without imposing a specific serialization or transport mechanism. 18 February 2026 Draft v1.0 Page 5 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV Digital Payment Credential Specification Schema Framework v1.0 Page 6 / 17 3 Use-Cases Payment Authentication with MFA: Multi-factor authentication (MFA) is enabled through device biometrics and device-bound keys, which helps with compliance with various regulations e.g., PSD2 and payment ecosystem security policies. a. With known Credential ID b. With credential discovery and selection allowing the Credential Verifier to request the Card ID attribute for the selected card, in support of the guest checkout scenario. The definitions outlined within this document allow support for various types of payment arrangements widely used by merchants and service providers. They provide comprehensive support for: • Immediate Payment: simple one-off payment • Recurring Payment: Fixed or variable amount arrangements with configurable recurrence intervals and optional reduced initial amounts 18 February 2026 Draft v1.0 Page 6 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV Digital Payment Credential Specification Schema Framework v1.0 Page 7 / 17 4 Participants and Roles The Digital Payment Credential process involves the following participants: Credential Issuer, Digital Wallet, and Credential Verifier. Each participant is assigned a distinct role within the process. The Credential Issuer generates the Digital Payment Credential, signs it with an attested key, and provisions the credential into the Digital Wallet on the user’s device. Note: the terminology “Issuer” does not refer to an issuing bank – it may be a card issuer or another entity provisioning the credentials. The Digital Wallet is expected to: • Securely store the credential provided by the Credential Issuer. • Generate a key pair in which the private key is stored securely on the user's device and does not leave the device, while the public key is provided to the Credential Issuer during the Digital Payment Credential provisioning process. • Handle requests for the Digital Payment Credential from the Credential Verifier. • Implement a user interface where the user can choose a card and view a payment sheet that shows all required payment details. • Verify the User in line with strong Multi-Factor Authentication (MFA) requirements such as biometrics or PIN and a device-bound key to produce a signed presentation payload. • Return the signed presentation payload to the Credential Verifier. The Digital Wallet uses a selective disclosure of the data provided in the Digital Payment Credential. The Digital Wallet shares only specific data elements of the credential with the Credential Verifier in accordance with the data minimization principle and to protect User’s privacy. To preserve transaction integrity, the Digital Wallet also includes the payment details shown to the user on the payment sheet (e.g., amount, currency, payee, payment type) incorporating those into the data that is signed with the user-verifying key stored on the device, according to the “sign what you see” principle. The Credential Verifier makes a request to Digital Wallet to get the signed presentation payload and further processes it according to the use case. 18 February 2026 Draft v1.0 Page 7 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV Digital Payment Credential Specification Schema Framework v1.0 Page 8 / 17 5 Definition of Data Elements This section defines the logical data elements for Digital Payment Credentials (DPC) and Payment Details supplied as a context by a merchant or Payment Service Provider (PSP). The goal is to provide a single set of field names, types, and rules that can be used consistently across Credential Issuers, Digital Wallets and Credential Verifiers, independent of the underlying representation format or transport. Table structure and common conventions are as follows: • R/C/O flags indicate whether a field is respectively REQUIRED, CONDITIONAL, or OPTIONAL. For CONDITIONAL this section states the exact predicate. Inclusion status of RECOMMENDED should be interpreted as OPTIONAL, but with recommendation to be provided. Note: While this paper describes certain fields as Required or Conditional, further evaluation is required with respect to each EMVCo Technology for the inclusion requirement in relevant specification or framework. • Data types use plain names (e.g., String, Integer, Boolean, DateTime, UUID) with format notes where relevant (e.g., 4 digits, ISO 4217, YYYY-MM-DD). For enumerations, the proposed values are provided. • The credential issuer and wallet will enable exchange of information where the credential issuer can request display of specific data elements relevant to the use-case and the Wallet can enable that subject to Wallet policies and configurations. 5.1 Data Element Attributes The following structure defines the attributes of each data element, indicating whether they can be requested, queried, or displayed. These attributes may apply individually or in combination with other attributes. Displayed Digital Wallet shall display the data to the user on the payment sheet. Attributes Queried Credential Verifier can provide the specific value for a data element to filter the matching DPCs. Requested Credential Verifier is permitted to specify the data element in the presentation request and Digital Wallet should provide the value in the DPC presentation. 18 February 2026 Draft v1.0 Page 8 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV Digital Payment Credential Specification Schema Framework v1.0 Page 9 / 17 5.2 Account related Data Elements Each Digital Payment Credential contains the necessary data related to the account and to the credential. Unless specified otherwise, all account related details in this document refer to card information. The credential issuer should be able to specify to the wallet what data fields can be displayed. Wallets should maintain default names and logos for the defined card networks; however Credential Issuer may override defaults using by passing additional information at the time of issuance. The Credential Issuer may also provide Card Issuer branding; Co-branding of cards can also be supported. Table 5.1: Account related data elements Data Element Card Last Four Inclusion Required Card Art URL Optional Card Name Optional Card Network Code Required Card Network Name Required Condition Type / Format String (4 digits) URL String String (Enum, e.g. MASTERCARD, VISA and others) String Credential Display Display MetaData Yes Wallet Display Remarks Yes Wallet displays the resource image not the URL. Yes Credential Query Query Value Matching Yes No Query Remarks / Expected Behavior Must be combined with Card BIN when used in query No No Yes Wallet should match value for any provided in the query Yes No Credential Request Can Be Requested Yes Yes No Yes Justification / Remarks Can be used by merchant/PSP on the order confirmation page Can be used by merchant/PSP on the order confirmation page. Can be used by merchant/PSP on the order confirmation page. Allows the merchant/PSP to determine the card network. No Card Network Logo URL Optional URL (Can be Yes Data URL as per RFC2397) Card Cobadged Network Code Optional String (Enum, Yes e.g. MASTERCARD, VISA and others) Card Cobadged Network Name Card Cobadged Network Logo URL Conditional Optional Required when Cobadged Network Code Specified String Yes URL (Can be Yes Data URL as per RFC2397) If not No provided, Wallet should display default logo basing on the Card Network Code. Yes No If not No provided, Wallet should display default logo basing on No Wallet Yes should match value for any provided in the query No No Allows the merchant/PSP to determine the card network. 18 February 2026 Draft v1.0 Page 9 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV Digital Payment Credential Specification Schema Framework v1.0 Page 10 / 17 Data Element Inclusion Card Issuer Name Card Issuer Logo URL Optional Optional Card Cobrand Name Optional Card Cobrand Logo URL Optional Card BIN Optional Card ID Optional Card PAR Optional Condition Type / Format String Credential Display Display MetaData Wallet Display Remarks the Card Network Code. Yes Credential Query Query Value Matching Query Remarks / Expected Behavior No Credential Request Can Be Requested Justification / Remarks No URL (Can be Yes Wallet No No Data URL as per displays RFC2397) the resource image not the URL String Yes No No URL (Can be Yes Data URL as per RFC2397) String (6 or 8 No digits) Wallet No displays the resource image not the URL. Yes String No Yes String (29 No Yes characters) or masked String No Must be No combined with Card Last Four when used in query Only one Yes can be provided: Credential ID, Card ID or Card PAR; Only one No can be provided: Credential ID, Card ID or Card PAR Allows the merchant to use the card in guest checkout scenario 5.3 Credential Related Data Elements The following table outlines the set of data elements important for Digital Payment Credential processing but may or may not be displayed to the User in the user interface implemented by the Digital Wallet. As described before, the credential issuer should be able to request display of relevant data elements at the time of the transaction. Each credential carries a globally unique Credential ID, enabling unambiguous selection when the Credential Verifier specifies known IDs and identification of the credential required for further processing after presentation. Credential expiry (if present) is independent of card expiry, reflecting that a DPC’s lifecycle can outlive card refresh or replacement events. Card ID is a reference to the underlying card and can be requested by the Credential Verifier in the guest checkout scenario when the card is not known to the merchant or Payment Service Provider. 18 February 2026 Draft v1.0 Page 10 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV Digital Payment Credential Specification Schema Framework v1.0 Page 11 / 17 Data Element Credential Type Inclusion Required Credential ID Required Credential Expiry Optional Table 5.2: Credential related data elements Condition Type / Format String (Fixed value: 'com.emvco.dpc.auth n') Credential Display Display MetaData No Wallet Display Remarks Credential Query Query Value Matching Yes Query Remarks / Expected Behavior Always required in query Credential Request Can Be Requested Yes Justification / Remarks Should always be returned. UUID (Version 4) No DateTime (ISO 8601 No UTC) Yes Only one Yes can be provided: Credential ID, Card ID or Card PAR No No Allows the merchant/PSP to identify credential for the SCA. Allowed Optional [TBD] No No No List 5.4 Payment Request Data Elements The Payment Request Data Elements comprises displayable Payment Details and nondisplayable Credential Section Criteria that should be provided by the Credential Verifier for each request for the Digital Payment Credential assertion. • The Payment Details define elements the Digital Wallet needs to present the payment sheet and generate the signature binding the data for non-repudiation. • The Credential Selection Criteria defines data elements allowing deterministic credential selection filters. 5.4.1 Payment Details The Payment Details table outlines the data elements that the Credential Verifier should provide during the DPC presentation request as a context for the payment arrangement confirmed by the User. Digital Wallet presents the Payment Details to the User on the payment sheet and includes all data elements in the data set signed by the Device Key managed by the Wallet. Core payment sheet fields, such as payment amount and currency are required to present clearly the value of the payment, payment summary, payee name and branding to enhance recognition and trust. The required payment type property drives the layout of the payment sheet. For recurring payment arrangements, requestors may need to supply the applicable recurrence unit and quantity, and may include start/end dates, number of payments, and optional reduced initial amount parameters. 18 February 2026 Draft v1.0 Page 11 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV Digital Payment Credential Specification Schema Framework v1.0 Page 12 / 17 Table 5.3: Payment request data elements Data Element Payment Reference Payment Amount Payment Currency Payment Amount Estimated Payment Summary Payee ID Inclusion Optional Required Required Optional Optional Optional Condition Type / Format String String (Decimal monetary value) String (3-letter ISO 4127) Default to FALSE Boolean String String Payment Sheet Display Displayed No Payment Sheet Display Remarks Yes Yes Yes If this value is set the Wallet should indicate the amount as estimated Yes No Payee Name Payee Website URL Payee Logo URL Payment Type Required Optional Optional Required String Yes URL Yes URL (Can be Data Yes URL as per RFC2397) String (Enum: N/A ONE_OFF, RECURRING) Recurring Payment Type Conditional Required when Payment Type is RECURRING String (Enum: Yes FIXED_AMOUNT, VARIABLE_AMOUNT) Recurring Conditional Required when String (Enum: DAY, Yes Interval Payment Type is WEEK, MONTH, Unit RECURRING YEAR) Recurring Conditional Required when Number (Integer) Yes Interval Payment Type is Unit RECURRING Quantity Recurring First Payment Date Optional Date (ISO 8601 date Yes only) Wallet displays the resource image not the URL Wallet renders the appropriate payment sheet based on the Payment Type Wallet should make it easy to understand if the Payment Amount relates only to the first payment or to each subsequent payment Wallet should combine the Recurring Interval Unit and Quantity to present the recurrence Wallet should combine the Recurring Interval Unit and Quantity to present the recurrence 18 February 2026 Draft v1.0 Page 12 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV Digital Payment Credential Specification Schema Framework v1.0 Page 13 / 17 Data Element Recurring Last Payment Date Recurring Number of Payments Recurring Reduce Amount Recurring Reduced Number of Payments Recurring Final Amount Inclusion Optional Optional Optional Optional Optional Condition Either Recurring Last Payment Date or Number of Payments can be provided (never both) Either Recurring Last Payment Date or Number of Payments cand be provided (never both) Type / Format Date (ISO 8601 date only) Number (Integer) String (Decimal monetary value) Number (Integer) Final Amount specifies the recurring final amount once reduced amount period is over. String (Decimal monetary value) Payment Sheet Display Displayed Yes Payment Sheet Display Remarks Yes Yes The currency for the Reduced Amount is the same as Payment Currency Yes Yes The currency for the Final Amount is the same as Payment Currency. 5.4.2 Credential Query The Credential Verifier may provide Credential Query data elements in the request to enable credential selection. Table 5.4: Credential Query Data Elements Credential Query Query by Credential ID Query by Card ID Query by Card PAR Query by Card BIN + Last Four Credential Discovery Query Type Any Any Exact Exact Any Query Description Merchant/PSP can request a credential by specifying the list of allowed Credential IDs. Merchant/PSP can request a credential by specifying the list of allowed Card IDs. Merchant/PSP can request the credential matching provided PAR Merchant/PSP can request the credential matching provided pair of Card BIN and Last Four Merchant/PSP can request any credential Wallet Remarks If more than one credential matches the query Wallet should allow card selection by the User If more than one credential matches the query Wallet should allow card selection by the User If there is a credential matching the query Wallet should progress to payment sheet i.e. no card selection If there is a credential matching the query Wallet should progress to payment sheet i.e. no card selection Wallet should present all the cards to the User and upon the selection progress to payment sheet 18 February 2026 Draft v1.0 Page 13 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV Digital Payment Credential Specification Schema Framework v1.0 Page 14 / 17 Credential Query Filter: Allowed Card Networks Query Type Any Query Description Merchant/PSP can specify the allowed Card Network Codes when requesting Credential Discovery. Wallet Remarks Wallet should present only cards with Card Network Code matching any of the provided in query 18 February 2026 Draft v1.0 Page 14 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV Digital Payment Credential Specification Schema Framework v1.0 Page 15 / 17 6 Security and Privacy Considerations • Data Minimization: Only disclose the necessary fields for a given transaction. • Holder Binding: Use device-bound keys for mDoc and VP-bound proofs for SD-JWT VC. • Revocation: Implement status check mechanisms. • Correlation Risk: Avoid over-disclosure of static identifiers (e.g., BIN + PANLastFour together). 18 February 2026 Draft v1.0 Page 15 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV Digital Payment Credential Specification Schema Framework v1.0 *** END OF DOCUMENT *** Page 16 / 17 18 February 2026 Draft v1.0 Page 16 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.