VTS spec - Approve Provisioning API - encrypted data objects outside part of root payload.....?!?!

[Beth]

Hello!  Within the VTS spec the Approve Provisioning API states required objects for:

• Token Information
• Device Information

However I have noted these are part of encrypted data.  It also states that encrypted data for this API will only be Cardholder Information & Risk Information.

Please may I have confirmation:

• are these two objects outside of encrypted data for this API and should be mapped as part of the root payload? or
• across the whole service, if a structure is recognised as part of encrypted data, then should we always expect to receive these as such and decrypt them our end?

Many thanks.

[SyedSa]

Hi @Beth,  Thank you for reaching out. An agent will get back to you as soon as possible. Until then, if any community member has information that may be helpful, feel free to reply in this thread.