Information allowing member to securely access account.
Loyalty program preferences specified by the enrolling member.
Identifies the alternate language for a customer or message. The human language is identified by ISO 639 codes.
Name of an individual and appropriate contact information. May be contact information for the customer or someone affiliated with the customer.
List of the vendor codes associated with a promotion.
Code used to identify a location.
Indicates how person became aware of loyalty program.
Provides a unique reference to this contact person.
value="Inherit" Permission for sharing data for marketing purposes.
Used to indicate whether the request is for the Test or Production system.
Provides the preferred method of communication. Refer to OTA code list Distribution Type (DTB).
When true, indicates a default value should be used.
Indicates the method of distribution for the booking documentation. Refer to OTA code list Distribution Type (DTB).
The message set will allow businesses to send enrolment information to their loyalty service provider to create a new account for one of their customers. This message will be based on the profile structure (OTA_Profile.xsd) with extensions for information that pertains only to loyalty account creation. In response, a message containing the newly created account information (e.g. membership ID) would be returned.
Indicates the creation date and time of the message in UTC using the following format specified by ISO 8601; YYYY-MM-DDThh:mm:ssZ with time values using the 24 hour clock (e.g. 20 November 2003, 1:59:38 pm UTC becomes 2003-11-20T13:59:38Z).
value="Inherit" Permission for sharing data for synchronization of information held by other travel service providers.
e.g "van der", "von", "de"
Identifes the primary language preference for the message. The human language is identified by ISO 639 codes.
Loyalty specific member profile information.
Type of name of the individual, such as former, nickname, alternate or alias name. Refer to OTA Code List Name Type (NAM).
A unique identifier to relate all messages within a transaction (e.g. this would be sent in all request and response messages that are part of an on-going transaction).
Method in which enrollment occurs.
Means by which the enrollment was initated. Refer to OTA Code List Enrollment Method (ENR).
Indicates if this contact should be used in the case of an emergency.
Used for Character Strings, length 1 to 32
Identifies the context of the identifying code (e.g., IATA, ARC, or internal code).
Promotion code is the identifier used by the host to link directly with a specific named advertising campaign. By including the required code, the client is able to gain access to special offers which may have been created for a specifically targeted group via a CRM system or for a wider advertising campaign using Television or press adverts.
The location code where the enrollment originated.
This indicates where this message falls within a sequence of messages.
This provides name information for a person.
A reference for additional message identification, assigned by the requesting host system. When a request message includes an echo token the corresponding response message MUST include an echo token with an identical value.
Method by which awards are allocated.
For all OTA versioned messages, the version of the message is indicated by a decimal value.
Indicates the type of relationship with the person or company in the profile, such as Spouse, Child, Family, Business Associate, Interest Group, Medical, Security,Other, etc.
Family name, last name.
Type of contact in the context of use for the travel experience; such as permanent, temporary, affiliation,
travel arranger, etc.
When true, indicates the message is being re-sent after a failure. It is recommended that this attribute is used (i.e., set to TRUE) only when a message is retransmitted.
Used to identify the sequence number of the transaction as assigned by the sending system; allows for an application to process messages in a certain order or to request a resynchronization of messages in the event that a system has been off-line and needs to retrieve messages that were missed.