The optional ‘lang’ property in the payload can be used to specify the ISO 939-2 code for the language of the comment. If omitted the default is to assume a comment in English, so the above example is not actually necessary (there is no distinction in that particular ISO standard between British and American English, for example, but I doubt that’s something we have to worry about).

shopperLanguageCode: String, optional

ISO ISO 639-1 language code indicating the preferred language of the shopper, where supported by the Payment Provider.

Translations to non-English languages of the purposes will be hosted at

https://vendorlist.consensu.org/purposes-language.json with older versions at

https://vendorlist.consensu.org/v-versionnum/purposes-language.json where language is the

two-letter lowercase ISO 639-1 language code.

ConsentLanguage 12 bits Two-letter ISO639-1

language code that

CMP asked for

consent in

Each letter should be encoded as 6 bits,

a=0..z=25 . This will result in the base64-

encoded bytes spelling out the language

code (in uppercase).

    The human language code in which the Expression is drafted (a three-letter code according to ISO 639-2 alpha-3). For an Akoma Ntoso XML representation, this value MUST correspond to the content of the first element <FRBRlanguage> in the metadata section. According with ISO 639-2 alpha-3 “mul” means multilingual document (text with different languages), while “und” means undetermined language