Indicates the type of SCA exemption requested.

The "lowValue" exemption is supported only for transaction amount less than 30 EUR. 

In case when requested, the liability for fraud lies with the Merchant.

Allows the Merchants to request skipping 3DS for the Out of Scope transactions. Implemented for One-Leg-Out only.

Universally unique ID created upon all installations and updates of the 3DS Requestor APp on a Customer Device. This will be newly generated and stored by the 3DS SDK for each installation or update. The field is limited to 36 characters and it shall have a canonical format as defined in IETF RFC 4122. This may utilise any of the specified versions as long as the output meets specified requirements.

Counter used as a security measure in the 3DS SDK to ACS secure channel.

JWE Object as defined Section 6.2.2.1 containing data encrypted by the SDK for the DS to decrypt. This element is the only field encrypted in this version of the EMV 3-D Secure specification. The field is sent from the SDK and it is limited to 64.000 characters. The data will be present when sending to DS, but not present from DS to ACS.

Public key component of the ephemeral key pair generated by the 3DS SDK and used to establish session keys between the 3DS SDK and ACS. In AReq, this data element is contained within the ACS Signed Content JWS Object. The field is limited to maximum 256 characters.

Indicates the maximum amount of time (in minutes) for all exchanges. The field shall have value greater or equals than 05.

Identifies the vendor and version of the 3DS SDK that is integrated in a 3DS Requestor App, assigned by EMVCo when the 3DS SDK is approved. The field is limited to 32 characters.

Universally unique transaction identifier assigned by the 3DS SDK to identify a single transaction. The field is limited to 36 characters and it shall be in a canonical format as defined in IETF RFC 4122. This may utilise any of the specified versions as long as the output meets specific requirements.

Data that supports and documents a specific authentication process carried out by the merchant such as FIDO

Cardholder mechanism used for prior authentication.O

Date and time (see RFC 3339) of the previous cardholder authentication in UTC.

JJJJ-MM-DD*D*HH:MM:SS+00:00

This data element contains an ACS transaction ID for a previous authenticated transaction (for example, the first recurring transaction authenticated by the cardholder).

For electronic delivery, the e-mail address to which the goods were delivered

Indicates the time period for the delivery of goods.

For the purchase of prepaid or gift cards, the total purchase amount of prepaid or gift cards in the smallest currency unit

For the purchase of prepaid or gift cards, the total number of individual prepaid or gift cards/codes purchased

For the purchase of prepaid or gift cards, the three-digit currency code of the gift card according to ISO 4217

For a pre-ordered purchase, the expected date on which the goods will be available (YYYYMMDD)

Indicates whether the customer places an order for a product with future availability or future release date

Indicates whether the customer reorders a previously purchased product

Specifies the delivery method selected for the transaction. If the sale includes one or more items, use the Code Shipping Indicator for the physical goods, or if all are digital goods, use the Code Shipping Indicator to describe the most expensive item.

The customer's salutation

First name of customer; optional if company is used, i.e.: you may use

• "company"
• or "lastname"
• or "firstname" plus "lastname"

Last name of customer; optional if company is used, i.e.: you may use

• "company"
• or "lastname"
• or "firstname" plus "lastname"

Company name of customer; The company name is optional if lastname is used, i.e.: you may use

• "company"
• or "lastname"
• or "firstname" plus "lastname"

Date of birth of customer YYYYMMDD, e.g. 19771015

Doing business as – name. For applicable suppliers.

VAT identification number. Used for b2b transactions to indicate VAT number of customer.

Specifies the number of days between authorizations

Determines the date of the first authorization according to the recurring mandate

Date after which no further authorizations should be processed.

Indicates whether a card transaction with stored data is the first transaction in a series or a subsequent transaction

Card verification number. Not required if pseudocardpan ist used.

Card start date in format YYMM

Card expiry date in format YYYYMM. Not required if pseudocardpan ist used.

Name of the cardholder as indicated on the card. Otherwise we will join firstname and lastname as cardholder.

Card issue number

Card number

Cardpan or pseudocardpan will be needed.

Card token

Cardpan or pseudocardpan will be needed.

Card Network. Not required if pseudocardpan ist used.

Exact content of the HTTP accept header as sent by the customer's browser

Boolean value that indicates the ability of the customer's browser to execute Java. Required if browserinfo_java_script_enabled = true; otherwise optional.

Boolean value that indicates the ability of the customer browser to execute JavaScript

Value of the browser language according to IETF BCP47

This value specifies the bit depth of the color palette for displaying images in bits per pixel. Required if browserinfo_java_script_enabled = true; otherwise optional.

Total screen height of the cardholder in pixels. Required if browserinfo_java_script_enabled = true; otherwise optional.

Total screen width of the cardholder in pixels. Required if browserinfo_java_script_enabled = true; otherwise optional.

Time zone shift in minutes between UTC and the cardholder's local browser time. Required if browserinfo_java_script_enabled = true; otherwise optional. Note that the offset is positive if the local time zone is behind UTC and negative if it is ahead.

Exact content of the HTTP user-agent header

The cardholder's account ID in the merchant environment / website (e.g. customer number)

This data element specifies the mechanism used by the cardholder to authenticate himself/herself to the merchant.

Date and time (see RFC 3339) of cardholder authentication in UTC.

YYYY-MM-DD*D*HH:MM:SS+00:00

Duration, how long the customer has the method of payment / payment account with the merchant.

Date of the last change of the customer's method of payment (account) with the merchant including billing or delivery address, new payment account or newly added user(s) (YYYYMMDD).

For a pre-ordered purchase, the expected date on which the goods will be available (YYYYMMDD)

Time period since the last change of the customer's account information at the merchant including billing or shipping address, new payment account or newly added user(s).

Date on which the customer opened the account in the format YYYYMMDD

Date of the last password change or resetting of the customer account in format YYYYMMDD

Specifies the length of time since the password was changed or since the customer account was reset.

Number of purchases in the last 6 months

Number of attempts to add a card in the last 24 hours

Number of transactions (successful and aborted) in the last 24 hours

Number of transactions (successful and aborted) in the last year

Date on which the payment account was registered in the customer account, in the format YYYYMMDD

Indicates the period of time for which the payment account is registered in the customer account.

Date when the delivery address provided for this transaction was first used, in format YYYYMMDD

Indicates when the shipping address specified for this transaction was first used.

Indicates whether the merchant has detected suspicious activity (including past fraud) in the customer account