AVS Response Code Lookup

Interpret actual AVS response via caller scheme edition street/postal/known mapping and review policy, unknown not false identity or proof of card fraud. Caller independently verifies edition, jurisdiction, applicability and one currency; screening does not establish legal compliance, coverage or bank approval.

Description

AVS codes map address evidence under processor-specific conventions.

AVS codes map address evidence under processor-specific conventions.^[1]

Unknown evidence and partial matches must be distinguished from complete address verification. Use AVS Response Code Lookup to evaluate the supplied inputs under the model explained below.

When to use AVS Response Code Lookup

Use AVS Response Code Lookup to evaluate the supplied inputs under the model explained below. Establish the currency and minor-unit convention, measurement period and applicable transaction or institution context.

How to use AVS Response Code Lookup and understand its results

Establish the currency and minor-unit convention, measurement period and applicable transaction or institution context.
Enter Caller avs response codes, Caller street match flags, Caller postal match flags, Caller match evidence known flags, Observed avs code, Caller require both matches using the field table and validation rules below, then run the tool.
Read Caller mapped street matches, Caller mapped postal matches, Match evidence unknown, Caller avs review required; interpret the units, signs, ordering and unknown-value placeholders described below.
Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.

Input field	Meaning	Value type	Requirement
callerAvsResponseCodes	Caller avs response codes	array of string	Required; constraints below
callerStreetMatchFlags	Caller street match flags	array of number	Required; constraints below
callerPostalMatchFlags	Caller postal match flags	array of number	Required; constraints below
callerMatchEvidenceKnownFlags	Caller match evidence known flags	array of number	Required; constraints below
observedAvsCode	Observed avs code	string	Required; constraints below
callerRequireBothMatches	Caller require both matches	boolean	Required; constraints below

Supply unique nonblank AVS codes with aligned binary street-match, postal-match and known-evidence flags, an exact observed code and a require-both boolean. Unknown codes fail. With unknown evidence, both match booleans are false placeholders and review is always true. Known evidence requires both matches or at least one according to the policy. No address normalization, identity verification or authorization occurs.

review=unknown OR (requireBoth ? NOT street OR NOT postal : NOT street AND NOT postal)

Use the field order, units and branch conditions described above.

Output field	Meaning	Value type
callerMappedStreetMatches	Caller mapped street matches	boolean
callerMappedPostalMatches	Caller mapped postal matches	boolean
matchEvidenceUnknown	Match evidence unknown	boolean
callerAvsReviewRequired	Caller avs review required	boolean

json

{
  "input": {
    "callerAvsResponseCodes": [
      "Y",
      "N",
      "U"
    ],
    "callerStreetMatchFlags": [
      1,
      0,
      0
    ],
    "callerPostalMatchFlags": [
      1,
      0,
      0
    ],
    "callerMatchEvidenceKnownFlags": [
      1,
      1,
      0
    ],
    "observedAvsCode": "U",
    "callerRequireBothMatches": true
  },
  "output": {
    "callerMappedStreetMatches": false,
    "callerMappedPostalMatches": false,
    "matchEvidenceUnknown": true,
    "callerAvsReviewRequired": true
  }
}

Limitations and assumptions

Unknown evidence and partial matches must be distinguished from complete address verification. Apply the exact scope and assumptions explained above.

All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.

Alternative or Complementary methods

Use CVV Mismatch Decline Code Lookup for a related task: CVV response mappings and decline policies are separate inputs.

Use Decline Code Do Not Honor Meaning Lookup for a related task: A generic issuer decline does not disclose a unique underlying cause.

References

AVS Response Code Lookup — tool.io

Similar or alternative tools

CVV Mismatch Decline Code Lookup
CVV response mappings and decline policies are separate inputs.
Decline Code Do Not Honor Meaning Lookup
A generic issuer decline does not disclose a unique underlying cause.