New Merchant Address and Service Location Fields Available in Transactions, ASA, and Auth Rules

Overview

Beginning Tuesday, March 18th, additional merchant location details and a new service location object is available across transaction responses, ASA requests, and auth rules. These fields enable card programs to access postal codes, street addresses, and service-level geographic data for use in fraud prevention, geo-based authorization decisioning, and richer transaction analytics.

Details

This release introduces changes across three areas: expanded merchant data, a new service location object, and new auth rule attributes.

Expanded Merchant Object

The merchant object in transaction responses and ASA requests now includes three new nullable fields:

• postal_code - Postal code of the card acceptor (e.g., "10001")
• street_address - Street address of the card acceptor (e.g., "123 MAIN ST")
• phone_number - Phone number of the card acceptor (e.g., "5551234567")

These fields are nullable because not all transactions include this data from the card network.

New Service Location Object

A new top-level service_location object is available in transaction responses and ASA requests. This object represents where the cardholder received the service, when different from the card acceptor location.

The service_location object is nullable. When present, it contains the following fields (all nullable):

• street_address - Street address of the service location
• city - City of the service location
• state - State/province code, ISO 3166-2
• country - Country code, ISO 3166-1 alpha-3
• postal_code - Postal code of the service location

New Auth Rule Attributes

Two new attributes are available for use in Authorization Rules:

• SERVICE_LOCATION_STATE - The state/province code (ISO 3166-2) where the cardholder received the service (e.g., "NY"). When a service location is present in the network data, the service location state is used. Otherwise, falls back to the card acceptor state.
• SERVICE_LOCATION_POSTAL_CODE - The postal code where the cardholder received the service (e.g., "10001"). When a service location is present in the network data, the service location postal code is used. Otherwise, falls back to the card acceptor postal code.

The fallback behavior makes these attributes suitable for geo-based authorization rules without requiring special handling for transactions that lack service location data.

Example: Transaction Response

Previously, the merchant object contained only basic acceptor information:

{
  "merchant": {
    "acceptor_id": "333301802529120",
    "acquiring_institution_id": "191231",
    "city": "NEW YORK",
    "country": "USA",
    "descriptor": "SQ *SOMA EATS",
    "mcc": "5812",
    "state": "CA"
  }
}

With this update, the merchant object includes additional location fields, and a new service_location object appears at the top level:

{
  "merchant": {
    "acceptor_id": "333301802529120",
    "acquiring_institution_id": "191231",
    "city": "NEW YORK",
    "country": "USA",
    "descriptor": "SQ *SOMA EATS",
    "mcc": "5812",
    "state": "CA",
    "postal_code": "94107",
    "street_address": null,
    "phone_number": null
  },
  "service_location": null
}

When service location data is available from the network, the service_location object is populated:

{
  "service_location": {
    "street_address": "456 OAK AVE",
    "city": "SAN FRANCISCO",
    "state": "CA",
    "country": "USA",
    "postal_code": "94107"
  }
}

Release Timeline

Production availability: March 18, 2026

User Impact

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

Updated Documentation

For transaction details, visit our API Reference. For ASA request specifications, visit our ASA Guide. For auth rule configuration, visit our Authorization Rules Guide.

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.