New Name Validation Fields Available in ASA

Overview

Rolling out between June 1st and June 5th, Authorization Stream Access requests will include a name_validation object when the card network has requested name validation for a transaction. ASA responders can optionally return a name_validation_result value to override Lithic's internally computed match. This allows card programs to apply their own name-matching logic against the cardholder data they hold on file.

Details

When a transaction arrives with a network name validation inquiry, the ASA request body will include a top-level name_validation object containing the cardholder name supplied by the network alongside Lithic's internally computed match result. Card programs can use this data to evaluate the match against their own records and return an authoritative result on the ASA response.

name_validation Request Object

The object is present only when the card network requested name validation for the transaction. It contains the following fields:

• name.first - First name provided by the network
• name.middle - Middle name provided by the network (optional)
• name.last - Last name provided by the network
• name_on_file_match - Lithic's internally computed match result, included so responders can see it before deciding whether to override

name_validation_result Response Override

ASA responses may include an optional name_validation_result field to override Lithic's internally computed match. If omitted, Lithic's internal result is used.

The field accepts the following values:

• MATCH - The submitted name matches the name on file
• PARTIAL_MATCH - The submitted name partially matches the name on file
• NO_MATCH - The submitted name does not match the name on file
• UNVERIFIED - The match could not be determined

Example: ASA Request with Name Validation

{
  "token": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "amount": 2500,
  "status": "AUTHORIZATION",
  "name_validation": {
    "name": {
      "first": "Jane",
      "middle": "Q",
      "last": "Doe"
    },
    "name_on_file_match": "PARTIAL_MATCH"
  }
  // other fields...
}

Example: ASA Response Overriding the Result

{
  "result": "APPROVED",
  "name_validation_result": "MATCH"
}

Release Timeline

Production availability: Week of June 1, 2026

User Impact

This change is additive only. Existing integrations will continue to function without modification. The name_validation object appears in ASA requests only when the card network requests name validation, and the name_validation_result response field is optional.

Updated Documentation

For complete ASA request and response specifications, visit our API Reference.

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.