Card Transaction File

A list of debit card transactions which have settled for a given day, containing data specific to debit card transactions. Intended to be paired with the Posted Transaction File for a complete view of the entire transaction detail.

Card Transaction File Definition

The Card Transaction File is created by Helix on a daily basis. It has the following properties:

  1. Fixed-length
  2. ANSI encoded
  3. Line endings are Windows-style CarriageReturn + LineFeed (\r\n, or 0x0D0A)
  4. File will be available in the relative directory of /PostedTransaction
  5. File name follows a specific, case-sensitive pattern of: yyyyMMddhhmm_DEBITCARDTRANSACTION.TXT

🚧

Format Disclaimer
Helix reserves the right to append new field(s) to the end of any Header or Content line without notice. This is to allow new data points to be added as needed in a timely fashion.

Implementation Note
Your code should be written such that unexpected characters after the "last" field but prior to the end of each line should be ignored. That is, if the file is documented as being 872 bytes per line, receiving a file with 984 bytes per line should not disrupt your processing. This applies to both Header and Content lines.

File Name Disclaimer
The date in file name should be used as a guideline for human eyes only. Any date-related programmatic dependencies should rely on the FileCreatedDate or FileEffectiveDate contained within the header line of each file, as these will be precise to the second and will be in the appropriate timezone.

Header Row

Property

Data Type (Length)

Alignment

Start Position

Description

RecordType

string (1)

Left

1

The flag for the header row. Will always be H.

FileName

string (50)

Left

2

The name of this request file excluding path.
Format: yyyyMMddhhmm_DEBITCARDTRANSACTION.TXT
Example: 201809110304_DEBITCARDTRANSACTION.TXT

RecordCount

integer (10)

Right

52

The number of records represented within the file. This field is zero-padded on the left side.
Example: 0000000872

FileCreatedDate

datetime (34)

Left

62

The date the file was created. Follows same format as API.
Example: 2014-10-20T10:30:31.456-05:00
See data format guidelines

FileEffectiveDate

datetime (34)

Left

96

The date to which the data in the file pertains. Follows same format as API.
Example: 2014-10-20T23:59:59.999-05:00
See data format guidelines

Content Row

Property

Data Type (Length)

Alignment

Start Position

Description

TransactionId

long integer (19)

Right

1

The Helix-assigned unique ID for the transaction. This field is zero-padded on the left side.
Example: 0000000000000000872

MasterId

long integer (19)

Right

20

The unique identifier for a group of related transactions. This field is zero-padded on the left side.
Example: 0000000000000000899

CardId

integer (10)

Right

39

The unique identifier for the card that the transaction occurred against. This field is zero-padded on the left side.
Example: 0000000872

PANLastFour

string (4)

Left

49

The rightmost four digits of the 16-digit card number.

CardHolderFirstName

string (64)

Left

53

The first name of the card holder.

CardHolderMiddleName

string (64)

Left

117

The middle name of the card holder.

CardHolderLastName

string (128)

Left

181

The last name of the card holder.

CardAcceptorLocation

string (25)

Left

309

The location of the merchant where the transaction originated.

CardAcceptorCity

string (13)

Left

334

The city of the merchant where the transaction originated.

CardAcceptorState

string (2)

Left

347

The two character state code of the merchant where the transaction originated.

CardAcceptorZip

string (9)

Left

349

The nine digit postal code of the merchant where the transaction originated.

RetrievalReferenceNumber

string (12)

Left

358

The Retrieval Reference Number (Field #37 from the ISO-8583 specification) as defined by the network provider. Useful when interfacing with the network provider's support tools or staff.

SystemTraceAuditNumber

string (6)

Left

370

The System Trace Audit Number (Field #11 from the ISO-8583 specification) as defined by the network provider. Useful when interfacing with the network provider's support tools or staff.

MerchantId

string (15)

Left

376

The Merchant Identifier (Field #42 from the ISO-8583 specification) as defined by the network provider. Useful to help identify a specific merchant uniquely.

SubTypeCode

string (6)

Left

391

The Merchant Category Code of the merchant where the transaction originated. Categorizes merchants with similar lines of business together.

MerchantGroupCode

string (6)

Left

397

The Merchant Group Code of the merchant where the transaction originated. This is a higher-level grouping construct for various Merchant Category Codes that all belong to the same "group" of businesses. Merchant Group Codes

TerminalId

string (15)

Left

403

The identifier of the terminal at the merchant where the transaction originated.

CashbackAmount

int (10)

Right

418

The amount of cash given to the user as part of the transaction. This field is zero-padded on the left side and two decimals will be assumed, e.g., 0000002000 represents an amount of $20.00.

SurchargeAmount

int (10)

Right

428

The amount of the surcharge applied as part of the transaction. This field is zero-padded on the left side and two decimals will be assumed, e.g., 0000000250 represents an amount of $2.50.

UnverifiedDepositAmount

int (10)

Right

438

The amount of the check deposit for this transaction. This field is zero-padded on the left side and two decimals will be assumed, e.g., 0000002000 represents an amount of $20.00.

CashDepositAmount

int (10)

Right

448

The amount of cash deposited for this transaction. This field is zero-padded on the left side and two decimals will be assumed, e.g., 0000002000 represents an amount of $20.00.

AtmNetworkIndicator

string (3)

Left

458

The network from which the transaction was acquired. See ATM Network Indicators for more information.

NetworkProviderTypeId

int (1)

Left

461

The id of card's network provider.

  • 1: Shazam
  • 2: VisaDps

TransactionFeeAmount

integer (10)

Right

462

The Total Transaction Fee Amount (Field #28 from the ISO-8583 specification). Contains the surcharge amount.

SettlementFeeAmount

integer (10)

Right

472

The Settlement Fee Amount (Field #29 from the ISO-8583 specification). Contains the surcharge amount in the issuer's currency.

AdditionalFees_CCA

integer (10)

Right

482

AdditionalFees_ICA

integer (10)

Right

492

MessageTypeIndicator

string (4)

Left

502

The incoming message type

OutputMessageTypeIndicator

string (4)

Left

506

The outgoing message type

OutputResponseCode

string (2)

Left

510

Helix's response code

AcquirerInstitutionCountryCode

string (3)

Left

512

AuthorizationIdentificationResponse

string (12)

Left

515

The authorization code for the transaction (Field #38 from the ISO-8583 specification).

ResponseCode

string (2)

Left

527

The code that defines the disposition of a message when present in a response, advice, or reversal.

  • 00: Approved or completed successfully
  • 01: Refer to card issuer
  • 02: Refer to card issuer, special conditions
  • 03: Invalid merchant
  • 04: Pick-up card
  • 05: Do not honor
  • 06: Error
  • 07: Pick-up card, special conditions
  • 08: Honor with identification
  • 09: Request in progress
  • 10: Approved for partial amount
  • 11: Approved (VIP)
  • 12: Invalid transaction
  • 13: Invalid amount
  • 14: Invalid card number (no such number)
  • 15: No such issuer
  • 16: Approved, update Track 3
  • 19: Re-enter transaction
  • 20: Invalid response
  • 23: Unacceptable transaction fee
  • 24: File update not supported by receiver. Use only in 03xx messages.
  • 25: Unable to locate record on file. Use only in 03xx messages.
    26: Duplicate file update record, no action. Use only in 03xx messages.
  • 27: File update field edit error. Use only in 03xx messages. See Field 44 - Additional Response Data to determine the field number in error.
  • 28: File update record locked out. Use only in 03xx messages
  • 29: File update not successful, contact acquirer. Use only in 03xx messages.
  • 30: Format error. See Field 44 - Additional Response Data to determine the field number in error.
  • 31: Bank not supported by switch
  • 33: Expired card, pick-up
  • 34: Suspected fraud, pick-up
  • 35: Card acceptor contact acquirer, pick-up
  • 36: Restricted card, pick-up
  • 37: Card acceptor call acquirer security, pick-up
  • 38: Allowable PIN tries exceeded, pick-up
  • 39: No credit amount
  • 40: Requested function not supported
  • 41: Lost card, pick-up
  • 42: No universal account
  • 43: Stolen card, pick-up
  • 44: No investment account
  • 45: Check Rejected - NSF
  • 46: Check Rejected - Stop Payment
  • 47: Check Rejected - Two Signatures Required
  • 48: Check Rejected - Closed Account
  • 49: Check Rejected - Other Reason
  • 50: Check Rejected - Hold on Funds
  • 51: Insufficient funds
  • 52: No checking account
  • 53: No savings account
  • 54: Expired card
  • 55: Incorrect PIN
  • 56: No card record
  • 57: Transaction not permitted to cardholder
  • 58: Transaction not permitted to terminal
  • 59: Suspected fraud
  • 60: Card acceptor contact acquirer
  • 61: Exceeds amount limit
  • 62: Restricted card
  • 63: Security violation
  • 65: Exceeds frequency limit
  • 66: Card acceptor call acquirer security
  • 67: Hard capture, pick-up
  • 75: Allowable number of PIN tries exceeded
  • 76: Key synchronization error
  • 87: Check already posted
  • 88: Information not on file
  • 89: Card verification value (CVV) verification failed (no pickup)
  • 90: Cutoff is in progress
  • 91: Issuer or switch is inoperative
  • 92: Financial institution or intermediate network unknown for routing
  • 93: Transaction cannot be completed, violation of law
  • 94: Duplicate transaction
  • 96: System malfunction
    D1 - NSF - Overdraft Fee Eligible
  • LK: Cardholder Blocked
    R0 - Payment Cancellation Order
  • R1: Revocation of Authorization Order
  • R3: Preauthorized Payment Revocation Order (block all recurring transactions for closed account)
  • X4: Consumer Transaction Controls Decline

PinValidationCode

string (1)

Left

529

Indicates whether the entered PIN was Valid (1).

AdditionalAmounts_Purchase

integer (10)

Right

530

The amount of the partial pay. This field is zero-padded on the left side, and two decimals will be assumed. e.g.: 000000000000832 represents an amount of $8.32.

AdditionalAmounts_Gratuity

integer (10)

Right

540

The amount of gratuity provided when the transaction occurred. This field is zero-padded on the left side, and two decimals will be assumed. e.g.: 000000000000832 represents an amount of $8.32.

Advice_OriginatorCode

string (1)

Left

550

Advice_ReasonCode

string (1)

Left

551

The identifying reason for an advice and/or reversal.

PrivatelyDefintedData_IssuerNetworkIdCode

string (3)

Left

552

PrivatelyDefinedData_AdditionalTransactionElement_FallbackIndicator

string (1)

Left

555

The fallback indicator (Field #63.4, Position 5 from the ISO-8583 specification).

PrivatelyDefinedData_ProcessingFlag_SpecialTransactionIndicator

string (1)

Left

556

The special transaction indicator (Field #63.7, Position 1 from the ISO-8583 specification).

  • A: Payment Account Status Inquiry (ASI) Transaction
  • B: Token account verification
  • C: Cloud based payment/HCE
  • D: Device Binding
  • T: Tokenized Message
  • V: Verified by Visa enrollment authorization request
  • blank: No special transaction considerations

PrivatelyDefinedData_ProcessingFlag_ISAIndicator

string (1)

Left

557

Visa International Service Assessment (ISA) Indicator (Field #63.7, Position 2 from the ISO-8583 specification), used to indicate whether a transaction is single or multi-currency.

  • C: Single Currency ISA (0.8%)
  • S: Multi-Currency ISA (1.0%)
  • R: ISA assessed and rebated
  • blank: Transaction does not qualify for fee assessment.

PrivatelyDefinedData_ProcessingFlag_PartialAuthIndicator

string (1)

Left

558

Transaction eligibility for Partial Authorization Indicator (Field #63.7, Position 3 from the ISO-8583 specification).

  • Y: Acquirer supports a partial authorization for transaction
  • blank: Acquirer does not support a partial authorization for transaction

PrivatelyDefinedData_RiskData_ScoreSource

string (1)

Left

559

(Field #63.8, Position 1 from the ISO-8583 specification)

  • 1: Online. If the card is currently in fraud monitoring suppression, 1 is the only possible value.
  • 2: Online Plus
  • 3: Real-Time
  • blank: No Falcon processing

PrivatelyDefinedData_RiskData_ScoreValue

string (4)

Left

560

Numeric score generated by Falcon ranging from 0000 to 0999. Higher score indicates a greater likelihood of fraud. If the card is currently in fraud monitoring suppression, the Score Value is 9998 or 9999. This field is populated for Falcon Real-Time transactions only. (Field #63.8, Positions 2-5 from the ISO-8583 specification)

PrivatelyDefinedData_RiskData_ResponseCode

string (1)

Left

564

Response code generated by Falcon Expert (Field #63.8, Position 6 from the ISO-8583 specification)

  • 0: No response code generated
  • 1: Approve
  • 2: Decline
  • 3: Refer
  • 4: Approve with identification
  • 5: Pick up card
  • blank: Card is currently in fraud monitoring suppression

PrivatelyDefinedData_RiskData_FalconReason1

string (2)

Left

565

Falcon Reason 1 (Field #63.8, Positions 7-8 from the ISO-8583 specification)

  • 00: No Code
  • 01: Unusual Time
  • 02: Unusual MCC
  • 03: High Risk MCC
  • 04: Suspicious High Dollar
  • 05: Suspicious Dollar Amounts
  • 06: Suspicious Geographic
  • 07: Suspicious Apprv Decln
  • 08: Suspicious Auth Velocity
  • 09: Suspicious Post Velocity
  • 10: Suspicious Transaction Type
  • 11: Suspicious Account Info
  • 12: Suspicious Keyed Activity
  • 13: High Risk Keyed Activity
  • 14: Suspicious ATM Cash
  • 15: Suspicious non-ATM Cash
  • 16: Suspicious Cash
  • 17: Suspicious Phone
  • 18: Suspicious Unattended Gas
  • 19: Suspicious CAT Activity
  • 20: High Risk MCC Amount
  • 21: Suspicious Foreign Activity
  • 22: CVV Expiration Date Mismatch
  • 51: Suspicious Payment Activity
  • 52: Suspicious Payment Amount
  • 53: Suspicious Payment Amount Nums
  • blank: Card is currently in fraud monitoring suppression

PrivatelyDefinedData_RiskData_FalconReason2

string (2)

Left

567

Falcon Reason 2 (Field #63.8, Positions 9-10 from the ISO-8583 specification). See example values in _FalconReason1.

PrivatelyDefinedData_RiskData_FalconReason3

string (2)

Left

569

Falcon Reason 3 (Field #63.8, Positions 11-12 from the ISO-8583 specification). See example values in _FalconReason1.

PrivatelyDefinedData_RiskData_VisaRiskScore

string (2)

Left

571

A value that indicates the degree of risk associated with the transaction. Higher values indicate higher authorization risk. Valid values: 01-99, blank if card is in fraud monitoring or data is not present. (Field #63.8, Positions 13-14 from the ISO-8583 specification).

PrivatelyDefinedData_RiskData_VisaRiskReason

string (2)

Left

573

A code that represents the logic behind the _VisaRiskScore (Field #63.8, Positions 15-16 from the ISO-8583 specification).

PrivatelyDefinedData_RiskData_VisaRiskConditionCode1

string (2)

Left

575

Contains a value relative to a high-risk Compromised Account Management System (CAMS) event. (Field #63.8, Positions 17-18 from the ISO-8583 specification).

PrivatelyDefinedData_RiskData_VisaRiskConditionCode2

string (2)

Left

577

Contains the Compromised Event Reference (CER) ID assigned to a significant CAMS event. (Field #63.8, Positions 19-20 from the ISO-8583 specification).

PrivatelyDefinedData_RiskData_VisaRiskConditionCode3

string (2)

Left

579

Reserved for future release

PrivatelyDefinedData_RiskData_VAAConditionCode1Rank

string (2)

Left

581

Grouping value assigned to VAA Risk Condition Code 1. (Field #63.8, Position 23 from the ISO-8583 specification).

  • 0: Low Risk for Fraud
  • 1: Medium Risk for Fraud
  • 2: High Risk for Fraud
  • blank: Card is currently in fraud monitoring suppression

PrivatelyDefinedData_RiskData_RTDResultCode

string (1)

Left

583

The Real Time Decisioning result code. (Field #63.8, Position 24 from the ISO-8583 specification)

  • D: Transaction declined by RTD
  • R: Transaction referred b RTD
  • blank: No RTD result code provided

PrivatelyDefinedData_RiskData_TravelStatusIndicator

string (1)

Left

584

Describes the cardholder's travel status. (Field #63.8, Position 34 from the ISO-8583 specification)

  • A: Cardholder may be traveling, destination matches
  • B: Cardholder may be traveling, destination unknown
  • blank: Card is currently in fraud monitoring suppression

TextInfo

string (255)

Left

585

Track2Data_ServiceCode

string (3)

Left

840

The Service Code encoded on Track 2 of the magnetic stripe

CardAcceptorTerminalIdentification

string (8)

Left

843

The identification code of the device at the merchant that accepted the card information (Field #41 from the ISO-8583 specification).

Cvv2PresenceIndicator

string (1)

Left

851

CVV2 Presence Indicator (Field #123, Usage 3, Position 3 from the ISO-8583 specification).

  • 0: CVV2 Value is deliberately bypassed or is not provided by the merchant
  • 1: CVV2 Value is present
  • 2: CVV2 Value is on the card but is illegible
  • 9: Cardholder states that the card has no CVV2 imprint

Cvv2Result

string (1)

Left

852

CVV2 Result (Field#123, Usage 3, Position 9 from the ISO-8583 specification).

  • M: Match
  • N: No Match
  • P: Not Processed
  • S: CVV2 should be on the card, but the merchant has indicated that CVV2 is not present
  • U: Issuer is not certified and/or has not provided Visa with the encryption keys

Token

string (19)

Left

853

Payment Account Reference Number (PAR) with a maximum length of 29. This field only applies if PrivatelyDefinedData_ProcessingFlags=T

TokenAssuranceLevel

string (2)

Left

872

Cardholder Verification Method. This field only applies if PrivatelyDefinedData_ProcessingFlags=T.

  • 1: Unknown
  • 2: None
  • 3: Signature
  • 4: Online PIN
  • 5: Offline PIN or Passcode
  • 6: Cardholder Device Code
  • 7: Fingerprint biometric verified by cardholder device
  • 8: Cardholder device pattern

DigitalWalletTokenRequestorTypeId

integer (10)

Right

874

Digital Commerce Indicator. This field only applies if PrivatelyDefinedData_ProcessingFlags=T.

  • 01: Visa Digital Commerce
  • 10: Apple Pay
  • 20: Google Pay
  • 30: Samsung Pay
  • 40: Visa Checkout (Click to Pay)
  • 50: Facebook
  • 60: Netflix
    Note: Other tokenized merchants may be undefined

TokenExpirationDate

string (4)

Left

884

The year and month the token expires (YYMM). This field only applies if PrivatelyDefinedData_ProcessingFlags=T

PaymentAccountReferenceNumber

string (29)

Left

888

The Payment Account Reference Number

MerchantCategoryCode

string (4)

Left

917

The exact Merchant Category Codes value received from the network provider.

CardAcceptorRegionCode

string (2)

Left

921

The region code of the card acceptor (Field #34, Positions 37-38 from the ISO-8583 specification).

CardAcceptorCountryCode

string (2)

Left

923

The country code of the card acceptor (Field #34, Positions 39-40 from the ISO-8583 specification).

NationalPointOfServiceCondition_TerminalUnattended

string (1)

Left

925

Terminal Unattended (Field #58, Position 1 from the ISO-8583 specification).

  • 0: Attended
  • 1: Unattended

NationalPointOfServiceCondition_TerminalOperator

string (1)

Left

926

Terminal Operator (Field #58, Position 2 from the ISO-8583 specification).

  • 0: Customer operated
  • 1: Card acceptor-operated
  • 2: Administrative

NationalPointOfServiceCondition_TerminalPremises

string (1)

Left

927

Terminal Premise (Field #58, Position 3 from the ISO-8583 specification).

  • 0: On premise
  • 1: On premise
  • 3: Electronic commerce

NationalPointOfServiceCondition_CardPresentation

string (1)

Left

928

Presentation Type (Field #58, Position 4 from the ISO-8583 specification).

  • 0: Customer present
  • 1: Customer not present
  • 2: Mail/Telephone Order
  • 4: Recurring transaction
  • 5: Installment Payment
  • 6: Account top up
  • 7: Pre-authorized purchase
  • 9: Single transaction for Mail/telephone Order

NationalPointOfServiceCondition_CardPresence

string (1)

Left

929

Card Presence (Field #58, Position 5 from the ISO-8583 specification).

  • 0: Card present
  • 1: Card not present
  • 8: Pre-authorized purchase

NationalPointOfServiceCondition_CardRetention

string (1)

Left

930

Card Retention (Field #58, Position 6 from the ISO-8583 specification).

  • 0: Device does not have card retention capability
  • 1: Device has card retention capability

NationalPointOfServiceCondition_CardTransaction

string (1)

Left

931

Card Transaction (Field #58, Position 7 from the ISO-8583 specification).

  • 0: Original transaction/clearing
  • 1: Incremental authorization
  • 2: Delayed charges
  • 3: No show
  • 4: Merchant authorized transaction
  • 5: Resubmission
  • 6: Reauthorization

NationalPointOfServiceCondition_SecurityCondition

string (1)

Left

932

Security Condition (Field #58, Position 8 from the ISO-8583 specification).

  • 0: No security concern
  • 1: Suspected fraud
  • 2: Identification verified
  • 3: Secure Electronic Commerce transaction
  • 4: Non-authorized security transaction at a 3-D Secure capable merchant. Merchant attempted to authenticate the cardholder using 3-D Secure.
  • 5: Non-authenticated security transaction
  • 6: Non-secure transaction
  • 7: Non-authenticated security transaction at a SET capable merchant
  • 8: CVV, dynamic CVV, or iCVV validated and valid
  • 9: CVV, dynamic CVV, or iCVV validated and invalid

NationalPointOfServiceCondition_TerminalType

string (2)

Left

933

Terminal Type (Field #58, Positions 9-10 from the ISO-8583 specification).

  • 00: Administrative terminal
  • 01: POS terminal
  • 02: ATM
  • 03: Home terminal
  • 04: ECR
  • 05: Dial terminal
  • 06: Travelers check machine
  • 07: Fuel machine
  • 08: Scrip machine
  • 09: Coupon machine
  • 10: Ticket machine
  • 11: Point-of-banking terminal
  • 12: Teller
  • 13: Franchise teller
  • 14: Personal banking
  • 15: Public utility
  • 16: Vending
  • 17: Self-service
  • 18: Authorization
  • 19: Payment
  • 20: VRU
  • 21: Smart phone
  • 22: Interactive television
  • 23: Personal Digital Assistant (PDA)
  • 24: Screen Phone
  • 25: Internet terminal
  • 26: MICR terminal
  • 27: Mobile acceptance solution

NationalPointOfServiceCondition_TerminalEntryCapability

string (1)

Left

935

Terminal Entry Capability Mode (Field #58, Position 11 from the ISO-8583 specification).

  • 0: Unknown
  • 1: Manual/no terminal
  • 2: Magnetic stripe read
  • 3: QR code
  • 4: OCR
  • 5: ICC
  • 6: Key entered
  • 9: File
  • S: MICR reader
  • T: Contactless
  • U: Contactless via Mag Stripe Rules

PointOfServicePanEntryMode

string (2)

Left

936

The Point of Service PAN Entry Mode (Field #22, Positions 1-2 from the ISO-8583 specification). Useful when determining how the PAN was entered.

  • 00: Unspecified
  • 01: Manual
  • 02: Magnetic stripe
  • 03: Optical Code
  • 04: OCR
  • 05:Integrated circuit card
  • 06: Manual (key-entered)
  • 07: Contactless chip transaction using chip data rules
  • 90: Full magnetic stripe read

PointOfServicePinEntryMode

string (1)

Left

938

The Point of Service PIN Entry Mode (Field #22, Position 3 from the ISO-8583 specification). Useful when determining how the PIN was entered.

  • 0: Unspecified
  • 1: PIN entry capability
  • 2: No PIN entry capability
  • 6: PIN pad inoperative

PrivatelyDefinedData_TransactionLevel_CredentialOnFileIndicator

string (1)

Left

939

Credential On File Indicator (Field #63.8, Position 2 from the ISO-8583 specification). Indicates whether a Credential on File is present.

  • Y: Credential on File
  • N: Not a Credential on File

PrivatelyDefinedData_TransactionLevel_CryptocurrencyPurchaseIndicator

string (1)

Left

940

Cryptocurrency Purchase Indicator (Field #63.8, Position 5 from the ISO-8583 specification). Identifies Visa transactions used to purchase cryptocurrency.

  • Y: Purchase of Cryptocurrency
  • N: Not a Purchase of Cryptocurrency

AvsResult

string (1)

Left

941

Address Verification Service Result

  • A: Address matches, ZIP code does not
  • B: Street address match for international transaction, but postal code not verified due to incompatible formats
  • C: Street address and postal code not verified for international transaction due to incompatible formats
  • D: Street address and postal code match for international transaction
  • G: Address information not verified for international transaction. Issuer is not an AVS participant, or AVS data was present in the request but issuer did not return an AVS result, or Visa performs AVS on behalf of the issuer and there was no address record on file for this account.
  • I: Address information not verified
  • M: Street address not verified
  • N: Nothing matches
  • P: Postal code match for international transaction, but street address not verified due to incompatible formats
  • R: Retry, system unable to process
  • U: No address data
  • Y: Address and 5-digit ZIP code match
  • Z: 5-digit postal/ZIP code matches, street address does not match or street address not included in request.