PCI Watch

Tracking changes across the Payment Card Industry

EMV® Secure Remote Commerce Specifications – API

v1.6 Specifications
Secure Remote Commerce

EMV® Secure Remote Commerce Specification – API Version 1.6 October 2026 EMV® Secure Remote Commerce Specification – API v1.6 Page i / xv

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 NON - INFRINGEMENT, 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, know-how, 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. EMV® Secure Remote Commerce Specification – API v1.6

/ xv

Revision Log – Version 1.6 DRAFT The following changes have been made to the document since the publication of version 1.5:

  • Minor editorial changes throughout the document, with sections and tables renumbered where necessary
  • Changes described in “SB n° 320 Update to SRC Specifications – API v1.5” have been included
  • Section 1.6.2 Terminology and Conventions has been updated with the terminology and conventions originally contained with the SRC Core Specification
  • Section 2.1 Complex Data Objects, the following complex data objects have been added:
  • Section 2.1.44 PayloadRequestData
  • Table 2.5 AdditionalSource has been updated as follows: o additionalSourceId: conditionality updated o uriData: conditionality updated o complianceSettings: data element added
  • Table 2.26 DeviceIdentity has been updated as follows: o identityProvider: data element has been changed from Optional to Required o identityValueType: data element added o additionalAttributes: data element added
  • Table 2.30 DigitalCardUpdateNotification has been updated as follows: o additionalNotificationData: data element added
  • Table 2.31 DpaData has been updated as follows: o dpaPublicKeyCredentials: data element added
  • Table 2.32 DpaTransactionOptions has been updated as follows: o payloadRequestData: data element added
  • Table 2.43 Payload has been updated as follows: o payloadRequestId: data element added
  • Table 2.45 PaymentOptions has been updated as follows: o paymentValidFromDate: data element added
  • Section 2.2.2 Use Case Specific Attributes has had use case specific attributes added for the Tolling use case EMV® Secure Remote Commerce Specification – API v1.6 / xv
  • Section 2.3 Enumerations, the following have been added or modified:
  • DeviceIdentityAssuranceType (modified)
  • DeviceIdentityProvider (modified)
  • DeviceIdentityValueType (added)
  • TranscationType (modified)
  • Section 2.4.2 Checkout Payload Response has been updated as follows: o encryptedSignedPayloadList: data element added o encryptedPayloadList: data element added
  • Conditional for the existing encryptedSignedPayload and encryptedPayload data elements have been updated, with the full conditional described in Table 5.6.8 and Table 5.6.12
  • Section 5.2 Initialize SRC has been added
  • Table 5.5.2: Prepare SRC Profile Definition – Request Body has had the following data elements added: o deviceIdentity o additionalSources o initializationSessionId
  • Table 5.5.6: Add Consumer Identities Definition – Request Body has had the data element additionalBindingData added
  • Table 5.6.7: Checkout Definition – Request Body has had the data element initializationSessionId added
  • Table 5.6.8: Checkout Definition – Response Body has had the description of the data element checkoutResponse updated to reflect the permissible contents of the data element
  • Table 5.6.11: Get Payload Definition – Query Parameters has had the data element PayloadRequestId added
  • Table 5.8.2: Identity Lookup Definition – Request Body has had the following data elements added: o dpaLocale o initializationSessionId
  • Table 5.8.3: Identity Lookup Definition – Response Body has had the data element additionalSources added
  • Table 5.8.6: Initiate Identity Validation Definition – Request Body has had the following data elements added or modified: EMV® Secure Remote Commerce Specification – API v1.6 / xv o idLookupSessionId has had its description modified to remove the line “Can be used in subsequent Initiate Identity Validation operation” o additionalSources has been added o initializationSessionId has been added
  • Table 5.8.10: Complete Identity Validation Definition – Request Body has had the following data elements added or modified: o idLookupSessionId has had its description modified to remove the line “Used in subsequent Initiate Identity Validation operation” o initializationSessionId has been added
  • Table 5.8.15: Is Recognized Definition – Query Parameters has had the data element initializationSessionId added
  • Table 5.8.16: Is Recognized Definition – Response Body has had the data element recognitionDomainName deprecated
  • Table 5.9.2: Authentication Methods Lookup Definition – Request Body has had the data element initializationSessionId added
  • Table 5.9.6: Authenticate Definition – Request Body has had the data element initializationSessionId added
  • Annex A.1.1 SRC Data Elements has had the list of explicit Merchant Account Information IDs deleted. Going forward, this information will be provided by the relevant SRC System
  • Annex A.4 Tolling has been added to support the Tolling use case EMV® Secure Remote Commerce Specification – API v1.6 Page v / xv i Revision Log – Version 1. 1. 1. 1. 1. 1.4. 1.4. 1. 1. 1.6. 1.6. 2. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. EMV® Secure Remote Commerce Specification – API v1.6 / xv 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2.1. 2. 2.2. 2.2. 2. 2. 2.4. EMV® Secure Remote Commerce Specification – API v1.6 / xv 2.4. 2.4. 2. 3. 3.1. 3.1. 3.1. 4. 4. 4. 5. 5.1. 5.1. 5.1. 5.1. 5.1. 5.1. 5.1. 5. 5.2. 5.2. 5. 5.3. 5.3. 5.3. 5.3. 5. 5.4. 5.4. 5. 5.5. 5.5. 5.5. 5. EMV® Secure Remote Commerce Specification – API v1.6 / xv 5.6. 5.6. 5.6. 5.6. 5. 5.7. 5. 5.8. 5.8. 5.8. 5.8. 5. 5.9. 5.9. 5. 5.10. 5. 5.11. 5. 5.12. 6. 6.1. 6.1. 6. 6. 6. 6. A. A.1. A.1. A.1. A.1. A. A.2. EMV® Secure Remote Commerce Specification – API v1.6 / xv A.2. A. A.3. A.3. A.3. A. A.4. A.4. A.4. A.4. EMV® Secure Remote Commerce Specification – API v1.6 Page x / xv Tables Table 1. Table 1. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. EMV® Secure Remote Commerce Specification – API v1.6 / xv Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 2. Table 3. Table 3. Table 4. Table 5. Table 5.2. Table 5.2. EMV® Secure Remote Commerce Specification – API v1.6 / xv Table 5.2. Table 5.3. Table 5.3. Table 5.3. Table 5.3. Table 5.3. Table 5.3. Table 5.3. Table 5.3. Table 5.3.9: Add Billing Address Definition – HTTP Verb, Path and Parameters... 128 Table 5.3. Table 5.3. Table 5.3. Table 5.3. Table 5.3. Table 5.3. Table 5.3. Table 5.4.1: Add Shipping Address Definition – HTTP Verb, Path and Parameters132 Table 5.4. Table 5.4. Table 5.4. Table 5.4.5: Delete Shipping Address Definition – HTTP Verb, Path and Parameters134 Table 5.4. Table 5.4. Table 5.4. Table 5.5.1: Prepare SRC Profile Definition – HTTP Verb, Path and Parameters. 135 Table 5.5. Table 5.5. Table 5.5. Table 5.5.5: Add Consumer Identities Definition – HTTP Verb, Path and Parameters139 Table 5.5. Table 5.5. Table 5.5. Table 5.5.9: Unbind App Instance Definition – HTTP Verb, Path and Parameters. 142 Table 5.5. Table 5.5. Table 5.5. Table 5.6.1: Prepare Checkout Data Definition – HTTP Verb, Path and Parameters144 Table 5.6. Table 5.6. Table 5.6. Table 5.6. EMV® Secure Remote Commerce Specification – API v1.6 / xv Table 5.6. Table 5.6. Table 5.6. Table 5.6. Table 5.6. Table 5.6. Table 5.6. Table 5.6. Table 5.6. Table 5.6. Table 5.6. Table 5.7. Table 5.7. Table 5.7. Table 5.8. Table 5.8. Table 5.8. Table 5.8. Table 5.8.5: Initiate Identity Validation Definition – HTTP Verb, Path and Parameters159 Table 5.8. Table 5.8. Table 5.8. Table 5.8.9: Complete Identity Validation Definition – HTTP Verb, Path and Parameters 161 Table 5.8. Table 5.8. Table 5.8. Table 5.8. Table 5.8. Table 5.8. Table 5.8. Table 5.8. Table 5.9. Table 5.9. Table 5.9. Table 5.9. Table 5.9. Table 5.9. Table 5.9. Table 5.9. Table 5.9. Table 5.10.1: Public Key Retrieval Definition – HTTP Verb, Path and Parameters 172 EMV® Secure Remote Commerce Specification – API v1.6 / xv Table 5.10. Table 5.10. Table 5.11. Table 5.11.2: Latest Compliance Resources Retrieval Definition – Request Body 174 Table 5.11.3: Latest Compliance Resources Retrieval Definition – Response Body174 Table 5.11.4: Latest Compliance Resources Retrieval Definition – HTTP Status Codes 175 Table 5.12. Table 5.12. Table 5.12. Table 5.12. Table 6. Table 6.2. Table 6.2. Table 6.2. Table 6.3. Table 6.3.2: Identity Validation Completion Event Notification Definition – Request Body 180 Table 6.3. Table 6.4. Table 6.4. Table 6.4. Table 6.5.1: Payment Notification Definition – HTTP Verb, Path and Parameters. 182 Table 6.5. Table 6.5. Table A.1. Table A.1. Table A.1. Table A.1. Table A.1. Table A.1. Table A.1. Table A.1. Table A.1. Table A.1. Table A.1. Table A.1. Table A.1. Table A.1. Table A.1. EMV® Secure Remote Commerce Specification – API v1.6 / xv Table A.2. Table A.2. Table A.4. Table A.4. EMV® Secure Remote Commerce Specification – API v1.6 / 201 1

Introduction

Secure Remote Commerce (SRC) is an evolution of remote commerce that provides for secure and interoperable card acceptance established through a standard specification. This document, the EMV® Secure Remote Commerce Specification – API, (hereafter the “SRC API Specification”), contains server-based APIs which can be used to securely build interfaces between SRC Systems and SRC System Participants. It is intended to be used in conjunction with the SRC Specifications (see Section 1.4.2 Published EMVCo Documents). 1.1

Scope

The SRC API Specification describes APIs to be used for the transmission of data between SRC Systems and SRC System Participants. These APIs are based on the following assumptions:

  • The server-based APIs provide a toolkit for SRC System Participants
  • They are not intended to provide context for all scenarios or use cases, and individual SRC Systems are responsible for creating implementation instructions for their SRC System Participants
  • They do not preclude an SRC System from providing additional technical components to support their implementations
  • The EMV SRC API specification offers levels of optionality for implementers of the specifications to add security layers based on the SRC solution provider’s own security requirements and risk controls 1.2 Constraints The SRC API Specification is designed to work within the constraints described in the SRC Core Specification. In particular, the SRC API Specification or any implementation of the SRC API Specification is not intended to replace or interfere with any international, regional, national or local laws and regulations; those governing requirements supersede any industry standards.

1.3 Audience This document is intended for use by SRC Systems and SRC System Participants. EMV® Secure Remote Commerce Specification – API v1.6

/ 201

1.4

References

The latest version of any reference, including all published amendments, shall apply unless a publication date is explicitly stated.

1.4.1 Normative References The standards in Table 1.1 may be associated with the SRC API Specification. All ISO specifications can be found at https://www.iso.org/store.html. Table 1.1: Normative References Reference Publication Name ISO 639 Language Codes — ISO 639 ISO 3166 Country Codes — ISO 3166 ISO 4217 Currency Codes — ISO 4217 ISO/IEC 7812 Identification cards — Identification of issuers ISO 8583 Interchange Message Specifications — ISO 8583 ISO 15118 ISO 15118-2 Road vehicles — Vehicle-to-Grid Communication Interface — Part 2: Network and application protocol requirements ISO 15118-20 Road vehicles — Vehicle-to-Grid Communication Interface — Part 20: 2nd generation network layer and application layer requirements OCPI Open Charge Point Interface v2.2.1-d2 (located at https://evroaming.org/ocpi-downloads/) RFC 3339 Date and Time on the Internet (https://tools.ietf.org/html/rfc3339) RFC 3447 Public-Key Cryptography Standards (https://tools.ietf.org/html/rfc3447) RFC 5322 Internet Message Format (https://tools.ietf.org/html/rfc5322) RFC 7515 JSON Web Signature (https://tools.ietf.org/html/rfc7515) RFC 7516 JSON Web Encryption (https://tools.ietf.org/html/rfc7516) RFC 7517 JSON Web Key (https://tools.ietf.org/html/rfc7517) EMV® Secure Remote Commerce Specification – API v1.6

/ 201

Reference Publication Name RFC 7518 JSON Web Algorithms (https://tools.ietf.org/html/rfc7518) RFC 7519 JSON Web Token (https://tools.ietf.org/html/rfc7519) RFC 8176 Authentication Method Reference Values (https://tools.ietf.org/html/rfc8176) W3C W3C Specification Secure Payment Confirmation (https://www.w3.org/TR/secure-payment-confirmation/) 1.4.2 Published EMVCo Documents The documents in Table 1.2 are related to or are associated with SRC and are located at www.emvco.com. Table 1.2: EMVCo References Reference Publication Name EMV 3-D Secure Specification EMV® 3-D Secure – Protocol and Core Functions Specification Merchant-Presented Mode EMV® QR Code Specification for Payment Systems (EMV QRCPS) – Merchant-Presented Mode Payment Tokenisation EMV® Payment Tokenisation Specification – Technical Framework SRC Core Specification EMV® Secure Remote Commerce Specification SRC Reproduction Requirements EMV® Secure Remote Commerce (SRC): Click to Pay Icon Reproduction Requirements SRC UI Guidelines and Requirements EMV® Secure Remote Commerce Specification – User Interface Guidelines and Requirements SRC JavaScript SDK EMV® Secure Remote Commerce Specification – JavaScript SDK SRC Version Management EMV® Secure Remote Commerce Version Management for SRC API and SRC JavaScript SDK Specifications SRC Use Cases EMV® Secure Remote Commerce Use Cases EMV® Secure Remote Commerce Specification – API v1.6

/ 201

Reference Publication Name SRC CX Guidelines EMV® Secure Remote Commerce – Click to Pay Customer Experience (CX) Guidelines Collectively, the term SRC Specifications refers to:

  • SRC Core Specification
  • SRC Reproduction Requirements
  • SRC UI Guidelines and Requirements
  • SRC API (this document)
  • SRC JavaScript SDK
  • SRC Version Management 1.5

Definitions

For the definition of the terms used in the SRC API Specification, refer to Table 1.3: Definitions in the SRC Core Specification. For definitions of data elements refer to Section 2 Data Dictionary.

1.6 Notational Conventions 1.6.1 Abbreviations For the definition of the abbreviations used in the SRC API Specification, refer to Section 1.9.1 Abbreviations in the SRC Core Specification.

1.6.2 Terminology and Conventions The SRC Specifications use capitalisations, camel case and different fonts, with the following conventions, to refer to:

  • Defined terms (see Table 1.3: Definitions in the SRC Core Specification) are capitalised with no other qualification (e.g. Digital Card Facilitator)
  • SRC API operations are capitalised and followed by the word “operation” (e.g. Checkout operation)
  • SRC JavaScript SDK methods are in camel case and followed by “() method” (e.g. enrollCard() method) EMV® Secure Remote Commerce Specification – API v1.6 / 201
  • SRC API and SRC JavaScript SDK complex data objects are capitalised and in Courier New font (e.g. DigitalCardData)
  • SRC API and SRC JavaScript SDK data elements are in camel case and Courier New font (e.g. srcCorrelationId)
  • Booleans are in lower case and in Courier New font (e.g. true) EMV® Secure Remote Commerce Specification – API v1.6 / 201 2 Data Dictionary 2.1 Complex Data Objects Table 2.1 to Table 2.55 introduce the common data objects used across the APIs defined in the SRC API Specification. Each table defines a single data object. The column headed R/C/O in each table refers to whether the data element is required, conditional or optional. The following notation is used:
  • R = Required – always present
  • C = Conditional – present under certain conditions (as specified in the description)
  • O = Optional – can be present 2.1.1 AcceptanceChannelData Table 2.1: AcceptanceChannelData Data Element R/C/O Constraints Description consumerData Type: JSONObject C Acceptance channel specific Consumer supplied data, either manually entered (or supplied by other means, e.g. voice, camera etc.) or previously stored Conditionality: At least one of consumerData or sellerData is required sellerData Type: JSONObject C Acceptance channel specific Seller supplied data supplied over the acceptance channel technology, or other means Conditionality: At least one of consumerData or sellerData is required EMV® Secure Remote Commerce Specification – API v1.6 / 201

2.1.2 AcceptanceChannelRelatedData Table 2.2: AcceptanceChannelRelatedData Data Element R/C/O Constraints Description acceptanceChannelType Type: AcceptanceChannelType R See AcceptanceChan nelType Type of acceptance channel acceptanceChannelTechnol ogy Type: AcceptanceChannelTechnolog y O See AcceptanceChan nelTechnology Technology used to transmit/receive the acceptance channel data acceptanceChannelData Type: AcceptanceChannelData R See AcceptanceChan nelData Acceptance channel data 2.1.3 AccountReference Table 2.3: AccountReference Data Element R/C/O Constraints Description srcDigitalCardId Type: String C Max Length = 36 Reference identifier to the Digital Card representing the PAN or Payment Token Conditionality: Required when consumerIdentity is not present consumerIdentity Type: ConsumerIdentity C See ConsumerIdentity Primary verifiable Consumer Identity within an SRC Profile (e.g. an email address or a mobile phone number) Conditionality: Required when srcDigitalCardId is not present EMV® Secure Remote Commerce Specification – API v1.6

/ 201

2.1.4 AdditionalAmount Table 2.4: AdditionalAmount Data Element R/C/O Constraints Description additionalAmountType Type: AdditionalAmountType R See AdditionalAmount Type Type of additional amount additionalAmountValue Type: String R Value of the additional amount 2.1.5 AdditionalSource Table 2.5: AdditionalSource Data Element R/C/O Constraints Description additionalSourceId Type: String C Max Length = 255 Additional source identifier associated with an SRC System specific configuration Conditionality: One and only one of additionalSourceId, complianceSettings or uriData must be present EMV® Secure Remote Commerce Specification – API v1.6

/ 201

uriData Type: UriData C See UriData URI associated with the additional source that the SRC Initiator may use to trigger consent flows. Response to the flow may be provided asynchronously using a cross origin post message between the windows (i.e. the caller and the SRC System). Response must be either:

  • CHANGE_CARD
  • CANCEL Conditionality: One and only one of additionalSourceID, ComplianceSettings or uriData must be present complianceSettings Type: ComplianceSettings C See ComplianceSettin gs Consumer compliance settings Conditionality: One and only one of additionalSourceID, ComplianceSettings or uriData must be present displayName Type: String R Max Length = 255 Presentation text created by the SRC System to enable Consumer consent flows artUri Type: String O Max Length = 1024 URI that hosts the image to be used for presentation purposes artHeight Type: String (Numeric) O Height of the image in pixels artWidth Type: String (Numeric) O Width of the image in pixels EMV® Secure Remote Commerce Specification – API v1.6 / 201

2.1.6 Address Table 2.6: Address Data Element R/C/O Constraints Description addressId Type: String O UUID Reference identifier of the address name Type: String O Max Length = 100 Name of the Consumer line1 Type: String C Max Length = 75 Address line 1 Conditionality: Required when used with the DPA Registration operation in the Management Service APIs line2 Type: String O Max Length = 75 Address line 2 line3 Type: String O Max Length = 75 Address line 3 city Type: String C Max Length = 50 Address city Conditionality: When used with the DPA Registration operation in the Management Service APIs at least one of the following is required:

  • both city and state
  • zip EMV® Secure Remote Commerce Specification – API v1.6 / 201 Data Element R/C/O Constraints Description state Type: String C Max Length = 30 Address state Recommendation to support ISO 3166-2 format i.e. made up of ISO 3166-1 alpha 2 country code, followed by an alphanumeric string of 3 characters representing the state or sub-division Conditionality: When used with the DPA Registration operation in the Management Service APIs at least one of the following is required:
  • both city and state
  • zip zip Type: String C Max Length = 16 Address zip/postal code Conditionality: When used with the DPA Registration operation in the Management Service APIs at least one of the following is required:
  • both city and state
  • zip countryCode Type: String C ISO 3166-1 alpha-2 country code Address country code Conditionality: Required when used with the DPA Registration operation in the Management Service APIs deliveryContactDetails Type: DeliveryContactDetails O See DeliveryContactD etails Delivery contact details EMV® Secure Remote Commerce Specification – API v1.6 / 201 Data Element R/C/O Constraints Description createTime Type: String (Numeric) O UTC time in Unix epoch format Date and time the address was created lastUsedTime Type: String (Numeric) O UTC time in Unix epoch format Date and time the address was last used 2.1.7 AppInstance Table 2.7: AppInstance Data Element R/C/O Constraints Description userAgent Type: String C N/A User agent string of the connecting client application Conditionality:
  • Required for browsers
  • Optional for non- browsers applicationName Type: String O Max Length = 255 Name of the connecting client application countryCode Type: String O ISO 3166-1 alpha-2 country code The country where the Consumer is accessing the service from deviceData Type: DeviceData O See DeviceData Device specific data 2.1.8 AssuranceData Table 2.8: AssuranceData Data Element R/C/O Constraints Description verificationData Type: List<VerificationData> R See VerificationData Set of verification data structures relating to different types of assurance EMV® Secure Remote Commerce Specification – API v1.6 / 201 Data Element R/C/O Constraints Description eci Type: String O Max Length = 2 Payment System-specific value to indicate the results of the attempt to authenticate the Cardholder and whether this resulted in an authenticated payload cardVerificationEntity Type: String (Numeric) DEPRECATED O Length = 2 Entity performing card verification. Valid values are:
  • 01 SRC Initiator
  • 02 SRC System
  • 03 SRCPI
  • 04 DCF
  • 05 DPA
  • 06 - 99 Others cardVerificationMethod Type: String (Numeric) DEPRECATED O Length = 2 Card verification check to validate that the PAN is active and valid at the Card Issuer. Valid values are:
  • 01 $0 authorisation, or single unit of currency authorisation
  • 02 Card Verification Number validation
  • 03 Postal code and address verification, where supported
  • 04 - 20 EMVCo future use
  • 21 - 99 SRC System specific EMV® Secure Remote Commerce Specification – API v1.6 / 201 Data Element R/C/O Constraints Description cardVerificationResults Type: String (Numeric) DEPRECATED O Length = 2 Verification status of the PAN. Valid values are:
  • 01 Verified
  • 02 Not Verified
  • 03 Not performed
  • 04 - 20 EMVCo future use
  • 21 - 99 SRC System specific cardVerificationTimestamp Type: String (Numeric) DEPRECATED O UTC time in Unix epoch format Date and time when the card verification was conducted cardAssuranceData Type: String DEPRECATED O Data collected that is associated with the PAN and presented to the SRC System cardholderAuthenticationEnt ity Type: String DEPRECATED O Max Length = 64 Entity performing Cardholder authentication EMV® Secure Remote Commerce Specification – API v1.6 / 201 Data Element R/C/O Constraints Description cardholderAuthenticationMe thod Type: String (Numeric) DEPRECATED O Length = 2 Card Issuer verification of the Cardholder. Valid values are:
  • 01 Use of a 3-D Secure ACS
  • 02 Mobile banking verification of the Cardholder with an authentication code
  • 03 Federated login systems
  • 04 A shared secret between the Card Issuer and the Cardholder such as One Time Passcode (OTP), activation code
  • 05 - 20 EMVCo future use
  • 21 - 99 SRC System specific cardholderAuthenticationRe sults Type: String (Numeric) DEPRECATED O Length = 2 Indicates whether the Cardholder was verified or not, and what the results are when verified.
  • 01 Verified
  • 02 Not Verified
  • 03 Not performed
  • 04 - 20 EMVCo future use
  • 21 - 99 SRC System specific cardholderAuthenticationTi mestamp Type: String (Numeric) DEPRECATED O UTC time in Unix epoch format Date and time when the Cardholder authentication was conducted EMV® Secure Remote Commerce Specification – API v1.6 / 201 Data Element R/C/O Constraints Description cardholderAssuranceData Type: String DEPRECATED O Data collected that is associated with the Cardholder and presented to the SRC System consumerVerificationEntity Type: String DEPRECATED O Max Length = 64 Entity performing Consumer verification consumerVerificationMethod Type: String (Numeric) DEPRECATED O Length = 2 The verification method used to verify Consumer credential. Valid values are:
  • 01 Static Passcode
  • 02 SMS One Time Passcode (OTP)
  • 03 Keyfob or EMV cardreader One Time Passcode (OTP)
  • 04 Application One Time Passcode (OTP)
  • 05 One Time Passcode (OTP) Other
  • 06 Knowledge Based Authentication (KBA)
  • 07 Out of Band Biometrics
  • 08 Out of Band Login
  • 09 Out of Band Other
  • 10 Risk-Based
  • 11 Other
  • 12 - 99 EMVCo future use EMV® Secure Remote Commerce Specification – API v1.6 / 201 Data Element R/C/O Constraints Description consumerVerificationResult s Type: String (Numeric) DEPRECATED O Length = 2 Indicates whether the Consumer was verified or not, and what the results are when verified. Valid values are:
  • 01 Verified
  • 02 Not Verified
  • 03 Not performed
  • 04 - 20 EMVCo future use
  • 21 - 99 SRC System specific consumerVerificationTimest amp Type: String (Numeric) DEPRECATED O UTC time in Unix epoch format Date and time when the Consumer verification was conducted consumerAssuranceData Type: String DEPRECATED O Data collected that is associated with the Consumer for assurance purposes deviceVerificationEntity Type: String (Numeric) DEPRECATED O Length = 2 Entity performing device verification. The valid values are:
  • 01 SRC Initiator
  • 02 SRC System
  • 03 SRCPI
  • 04 DCF
  • 05 DPA
  • 06 - 99 Others EMV® Secure Remote Commerce Specification – API v1.6 / 201 Data Element R/C/O Constraints Description deviceVerificationMethod Type: String (Numeric) DEPRECATED O Length = 2 Verification method used to verify Consumer Device information. Valid values are:
  • 01 - 20 EMVCo future use
  • 21 - 99 SRC System specific deviceVerificationResults Type: String (Numeric) DEPRECATED O Length = 2 Indicates whether the device was verified or not, and what the results are when verified. Valid values are:
  • 01 Verified
  • 02 Not Verified
  • 03 Not performed
  • 04 - 20 EMVCo future use
  • 21 - 99 SRC System specific deviceVerificationTimestam p Type: String (Numeric) DEPRECATED O UTC time in Unix epoch format Date and time when the device verification was conducted deviceAssuranceData Type: String DEPRECATED O Data collected that is associated with the device for assurance purposes EMV® Secure Remote Commerce Specification – API v1.6 / 201 Data Element R/C/O Constraints Description relationshipVerificationEntit y Type: String (Numeric) DEPRECATED O Length = 2 Entity performing relationship verification of a combination of data. The valid values are:
  • 01 SRC Initiator
  • 02 SRC System
  • 03 SRCPI
  • 04 DCF
  • 05 DPA
  • 06 - 99 Others relationshipVerificationMeth od Type: String (Numeric) DEPRECATED O Max Length = 2 Verification method used to verify information associated with the relationship relationshipVerificationResu lts Type: String (Numeric) DEPRECATED O Max Length = 2 Results of the verification of the relationship of a combination of data relationshipVerificationTime stamp Type: String (Numeric) DEPRECATED O UTC time in Unix epoch format Date and time when the relations

仅显示部分内容。全文请阅读原文。