Improving avs.zipcode Values in ASA

Beginning on August 19th, we will deploy an improvement which aligns the behavior of the avs.zipcode field (contained within the ASA request) with our existing product documentation (ASA request spec). Today, Lithic truncates any value provided in card network messages to 5 characters. This can create scenarios where non-US postal codes are unnecessarily shortened or US ZIP codes mistakenly entered with spaces are not passed through in full. For example, a Canadian postal code of V6E 0C6 is shortened to V6E 0 or a US ZIP code entered with an accidental space 89 109 becomes 89 10.

With this release, customers may begin receiving longer strings in the zipcode field than were previously passed. Our documentation states that the zipcode value can have a variable length, and we currently pass variable length values in this field which are shorter than 5 characters (e.g. 2 character values). With this release, customers will be able to receive full US 9-digit ZIPs as well as international postal codes in their full lengths, better aligning production behavior with product documentation.

If you have any questions or concerns about this change, please reach out to [email protected].

[Update 8/7] - Previously, this changelog included mentions of updates affecting the transaction object. These references have been removed as there will be no impact to transactions (which already exhibit the expected behavior).