The referenceId of a previous ID+ transaction. Allows you to link multiple transactions together. See transaction linkage for more information.

A client-specified unique identifier for the transaction.

The consumer’s first name.

Note:

• UTF-8 single byte latin characters are supported.
• The following special characters are not supported: ^±!@£$%&*_+¡€#¢§¶•ªº«<>?\/:;|=
• The field accepts backslashes to prevent HTTP 400 errors; these are removed during preprocessing to guard against injection attacks and ensure consistent data storage, resulting in an HTTP 200 response. If a backslash is the only input, it returns an empty string.

The consumer’s last name.

Note:

• UTF-8 single byte latin characters are supported.
• The following special characters are not supported: ^±!@£$%&*_+¡€#¢§¶•ªº«<>?\/:;|=
• The field accepts backslashes to prevent HTTP 400 errors; these are removed during preprocessing to guard against injection attacks and ensure consistent data storage, resulting in an HTTP 200 response. If a backslash is the only input, it returns an empty string.

The consumer's date of birth, preferably in YYYY-MM-DD, YYYYMMDD, or YYYY/MM/DD format.

The consumer’s phone number in E.164 format, which includes the country code (e.g., + followed by international dialing code and number).
Hyphens are optional. A mobile phone number is preferred.

Example formats:

• United States: +13475550100
• United Kingdom: +447911123456
• Brazil: +5511987654321
• India: +919876543210
• Australia: +61412345678

The first line of the consumer's address.

An optional second line for the address.

The consumer's city of residence in valid postal address format.

Note: city is required for international requests.

The state, province, or region where the consumer resides, specified in ISO 3166-2 format.

Note:

• If the physical address is within a U.S. territory, you can pass the territory name in either the state or country field.
• If the physical address is in a country or state that does not require state, do not include this field in the API call.

The consumer's five or nine-digit ZIP code must be in a valid postal address format. Hyphens or spaces are optional.

Note:

• If the physical address is in a country or state that does not require zip, do not include this field in the API call.
• This field accepts a 9-digit zip code, with spaces allowed in place of hyphens (e.g., 94502 1397 instead of 94502-1397).

The country where the consumer resides, specified in ISO 3166-1 alpha-2 format.

Note: country is required for international requests.