Address Match Results Now Available in 3DS, ASA, and Authorization Rules

Overview

A new address_on_file_match field is now available in 3DS authentications and ASA requests. Additionally, a new ADDRESS_MATCH attribute is available for use in authorization rules. These additions allow programs to reference Lithic's evaluation of how the address data in the transaction event compares to the cardholder address information on file, supporting more robust fraud detection and authentication strategies.

Details

The address_on_file_match field appears within the avs object in ASA requests and in the cardholder object in 3DS authentications. This field contains Lithic's evaluation of how address data in the transaction event compares to the cardholder address stored on file.

Address Match Values

The address_on_file_match field supports the following enum values:

• MATCH - Both address and ZIP code match cardholder data on file
• MATCH_ADDRESS_ONLY - Street address matches but ZIP code does not match
• MATCH_ZIP_ONLY - ZIP code matches but street address does not match
• MISMATCH - Neither address nor ZIP code match cardholder data on file
• NOT_PRESENT - Either Lithic has no cardholder address data on file, or the transaction contains no address data

ASA - Example

The avs object in ASA requests now includes the address_on_file_match field:

"avs": {
   "address": "123 Main St",
   "zipcode": "94102",
   "address_on_file_match": "MATCH"
 }

3DS Authentications - Example

The cardholder object in 3DS authentications now includes the address_on_file_match field:

"cardholder": {
   "address_on_file_match": "MATCH",
   "billing_address": {
     "address1": "123 Main St",
     "city": "San Francisco",
     "country": "US",
     "postal_code": "94102"
   },
   "address_match": true
}

Authorization Rules - Example

The ADDRESS_MATCH attribute is now available in conditional action rules for authorization and 3DS authentication event streams. This attribute can be used with standard rule operations to create address verification policies.

Example rule configuration:

{
  "type": "CONDITIONAL_ACTION",
  "parameters": {
    "action": "DECLINE",
    "conditions": [
      {
        "attribute": "ADDRESS_MATCH",
        "operation": "IS_NOT_ONE_OF",
        "value": ["MATCH", "NOT_PRESENT"]
      }
    ]
  }
}

This rule would decline transactions where the address only partially matches or fully mismatches cardholder address data on file.

Release Timeline

Production availability: October 21, 2025

User Impact

This change is additive only. Existing integrations will continue to function without modification.

Updated Documentation

For detailed specifications, visit our API Reference:

• 3DS Authentication API
• Authorization Stream Access
• Authorization Rules API

If you have any questions or concerns, please contact us via the HELP link in your Lithic Dashboard.

The Lithic changelog has an RSS feed! To monitor for new update announcements, subscribe with your preferred RSS reader.