6.4. Common¶
Nested objects¶
DeviceRenderOptions¶
Optional
One of:
01
02
03
Lists all of the SDK Interface types that the device supports for
displaying specific challenge user interfaces within the SDK.
Meaning of values:
| 01 | Native |
| 02 | HTML |
| 03 | Both |
Optional
One of:
01
02
03
04
05
Lists all UI types that the device supports for displaying specific
challenge user interfaces within the SDK.
Meaning of values:
| 01 | Text |
| 02 | Single Select |
| 03 | Multi Select |
| 04 | OOB |
| 05 | HTML Other (valid only for HTML UI) |
AcctInfo¶
Optional
One of:
01
02
03
04
05
Length of time that the cardholder has had the account with the 3DS
Requestor.
Meaning of values:
| 01 | No account (guest check-out) |
| 02 | Created during this transaction |
| 03 | Less than 30 days |
| 04 | 30−60 days |
| 05 | More than 60 days |
Scheme specific rules:
- Visa
- Field is required if available
Optional
Format:
yyyymmdd
Date that the cardholder’s account with the 3DS Requestor was last
changed, including Billing or Shipping address, new payment account,
or new user(s) added.
Scheme specific rules:
- Visa
- Field is required if available
Optional
One of:
01
02
03
04
Length of time since the cardholder’s account information with the 3DS
Requestor was last changed, including Billing or Shipping address, new
payment account, or new user(s) added.
Meaning of values:
| 01 | Changed during this transaction |
| 02 | Less than 30 days |
| 03 | 30−60 days |
| 04 | More than 60 days |
Scheme specific rules:
- Visa
- Field is required if available
Optional
Format:
yyyymmdd
Date that the cardholder opened the account with the 3DS Requestor.
Scheme specific rules:
- Visa
- Field is required if available
Optional
Format:
yyyymmdd
Date that cardholder’s account with the 3DS Requestor had a password
change or account reset.
Scheme specific rules:
- Visa
- Field is required if available
Optional
One of:
01
02
03
04
05
Indicates the length of time since the cardholder’s account with the
3DS Requestor had a password change or account reset.
Meaning of values:
| 01 | No change |
| 02 | Changed during this transaction |
| 03 | Less than 30 days |
| 04 | 30−60 days |
| 05 | More than 60 days |
Scheme specific rules:
- Visa
- Field is required if available
Optional
Max length:
4
Regexp:
^[0-9]{1,4}$
Number of purchases with this cardholder account during the previous
six months.
Scheme specific rules:
- Visa
- Field is required if available
Optional
Format:
yyyymmdd
Date that the payment account was enrolled in the cardholder’s account
with the 3DS Requestor.
Scheme specific rules:
- Visa
- Field is required if available
Optional
One of:
01
02
03
04
05
Indicates the length of time that the payment account was enrolled in
the cardholder’s account with the 3DS Requestor.
Meaning of values:
| 01 | No account (guest check-out) |
| 02 | During this transaction |
| 03 | Less than 30 days |
| 04 | 30−60 days |
| 05 | More than 60 days |
Scheme specific rules:
- Visa
- Field is required if available
Optional
Max length:
3
Regexp:
^[0-9]{1,3}$
Number of Add Card attempts in the last 24 hours.
Scheme specific rules:
- Visa
- Field is required if available
Optional
Format:
yyyymmdd
Date when the shipping address used for this transaction was first
used with the 3DS Requestor.
Optional
One of:
01
02
03
04
Indicates when the shipping address used for this transaction was
first used with the 3DS Requestor.
Meaning of values:
| 01 | This transaction |
| 02 | Less than 30 days |
| 03 | 30−60 days |
| 04 | More than 60 days |
Scheme specific rules:
- Visa
- Field is required if available
Optional
One of:
01
02
Indicates if the Cardholder Name on the account is identical to the
shipping Name used for this transaction.
Meaning of values:
| 01 | Account Name identical to shipping Name |
| 02 | Account Name different than shipping Name |
Scheme specific rules:
- Visa
- Field is required if available
Optional
One of:
01
02
Indicates whether the 3DS Requestor has experienced suspicious
activity (including previous fraud) on the cardholder account.
Meaning of values:
| 01 | No suspicious activity has been observed |
| 02 | Suspicious activity has been observed |
Scheme specific rules:
- Visa
- Field is required if available
Optional
Max length:
3
Regexp:
^[0-9]{1,3}$
Number of transactions (successful and abandoned) for this cardholder
account with the 3DS Requestor across all payment accounts in the
previous 24 hours.
Scheme specific rules:
- Visa
- Field is required if available
Optional
Max length:
3
Regexp:
^[0-9]{1,3}$
Number of transactions (successful and abandoned) for this cardholder
account with the 3DS Requestor across all payment accounts in the
previous year.
Scheme specific rules:
- Visa
- Field is required if available
PhoneNumber¶
MerchantRiskIndicator¶
Optional
Format:
email
Max length:
254
For Electronic delivery, the email address to which the merchandise
was delivered.
Scheme specific rules:
- Visa
- Field is required if available
Optional
One of:
01
02
03
04
Indicates the merchandise delivery timeframe.
Meaning of values:
| 01 | Electronic Delivery |
| 02 | Same day shipping |
| 03 | Overnight shipping |
| 04 | Two-day or more shipping |
Scheme specific rules:
- Visa
- Field is required if available
Optional
Regexp:
^\d{0,15}$
For prepaid or gift card purchase, the purchase amount total of
prepaid or gift card(s) in major units (for example, USD 123.45 is
123).
Scheme specific rules:
- Visa
- Field is required if available
Optional
Regexp:
^\d{2}$
For prepaid or gift card purchase, total count of individual prepaid
or gift cards/codes purchased.
Scheme specific rules:
- Visa
- Field is required if available
Optional
Format:
currency
For prepaid or gift card purchase, ISO 4217 three-digit currency code
of the gift card, other than those listed in Table A.5.
Scheme specific rules:
- Visa
- Field is required if available
Optional
Format:
yyyymmdd
For a pre-ordered purchase, the expected date that the merchandise
will be available.
Scheme specific rules:
- Visa
- Field is required if available
Optional
One of:
01
02
Indicates whether Cardholder is placing an order for merchandise with
a future availability or release date.
Meaning of values:
| 01 | Merchandise available |
| 02 | Future availability |
Scheme specific rules:
- Visa
- Field is required if available
Optional
One of:
01
02
Indicates whether the cardholder is reordering previously purchased
merchandise.
Meaning of values:
| 01 | First time ordered |
| 02 | Reordered |
Scheme specific rules:
- Visa
- Field is required if available
Optional
One of:
01
02
03
04
05
06
07
Indicates shipping method chosen for the transaction. Merchants must
choose the Shipping Indicator code that most accurately describes the
cardholder’s specific transaction, not their general business. If one
or more items are included in the sale, use the Shipping Indicator
code for the physical goods, or if all digital goods, use the Shipping
Indicator code that describes the most expensive item.
Meaning of values:
| 01 | Ship to cardholder’s billing address |
| 02 | Ship to another verified address on file with merchant |
| 03 | Ship to address that is different than the cardholder’s billing address |
| 04 | “Ship to Store” / Pick-up at local store (Store address shall be populated in shipping address fields) |
| 05 | Digital goods (includes online services, electronic gift cards and redemption codes) |
| 06 | Travel and Event tickets, not shipped |
| 07 | Other (for example, Gaming, digital services not shipped, emedia subscriptions, etc.) |
Scheme specific rules:
- Visa
- Field is required if available
MessageExtension¶
Required
A Boolean value indicating whether the recipient must understand the
contents of the extension to interpret the entire message.
Required
Max length:
8059
The data carried in the extension.
Required
Max length:
64
A unique identifier for the extension. Note: Payment System Registered
Application Provider Identifier (RID) is required as prefix of the ID.
Required
Max length:
64
The name of the extension data set as defined by the extension owner.
ThreeDSRequestorPriorAuthenticationInfo¶
Optional
Max length:
2048
Data that documents and supports a specific authentication process. In
the current version of the specification this data element is not
defined in detail, however the intention is that for each 3DS
Requestor Authentication Method, this field carry data that the ACS
can use to verify the authentication process. In future versions of
the specification, these details are expected to be included.
Scheme specific rules:
- Visa
- Field is required if available
Optional
Regexp:
^(0[1-4])|([89][1-10])$
Mechanism used by the Cardholder to previously authenticate to the 3DS
Requestor.
Meaning of values:
| 01 | Frictionless authentication occurred by ACS |
| 02 | Cardholder challenge occurred by ACS |
| 03 | AVS verified |
| 04 | Other issuer methods |
Scheme specific rules:
- Visa
- Field is required if available
Optional
Format:
yyyymmddhhmm
Date and time in UTC of the prior cardholder authentication.
Scheme specific rules:
- Visa
- Field is required if available
Optional
Max length:
36
This data element provides additional information to the ACS to
determine the best approach for handing a request.
Scheme specific rules:
- Visa
- Field is required if available
ACSRenderingType¶
Required
One of:
01
02
This the ACS interface that the challenge will present to the
cardholder.
Meaning of values:
| 01 | Native UI |
| 02 | HTML UI |
Required
One of:
01
02
03
04
05
Identifies the UI Template format that the ACS first presents to the
consumer.
Meaning of values:
| 01 | Text |
| 02 | Single Select |
| 03 | Multi Select |
| 04 | OOB |
| 05 | HTML Other |
Formats¶
uuid¶
UUID version 4.
ip¶
IPv4 or IPv6 address.
yymm¶
2-digit year and month.
yyyymmdd¶
4-digit year, 2-digit month and day-of-month.
yyyymmddhhmm¶
4-digit year, 2-digit month, day-of-month, hour and minute.
yyyymmddhhmmss¶
4-digit year, 2-digit month, day-of-month, hour, minute and second.
email¶
Email Address
url¶
Fully qualified URL
country¶
3-digit ISO 3166-1 country code string, for Denmark e.g.
{
"billAddrCountry": "208"
}
for France e.g.
{
"billAddrCountry": "250"
}
Country codes 901 – 999 are not valid.
currency¶
3-digit ISO 4217 currency code string, for DKK e.g.
{
"purchaseCurrency": "208"
}
or EUR
{
"purchaseCurrency": "978"
}
The following codes cannot be used:
955
956
957
958
959
960
961
962
963
964
999