Property Glossary
Each event payload type contains various aliases and properties. The tables below define these aliases and properties that could appear in payloads.
Alias Glossary
Property Glossary
Property Name | Meaning |
---|---|
| The four-digit message type identifier from the original request message. Applicable only to debit card events. |
| The four-digit message type identifier from the response message. Applicable only to debit card events. |
| The two-digit status code from the response message. Applicable only to debit card events. |
| 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. Applicable only to debit card events. |
| 3 digit numeric code for the country where the acquiring institution is located. Applicable only to debit card events. |
| 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. Applicable only to debit card events. |
| The two-digit status code from the original request message. Applicable only to debit card events. |
| 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.: |
| The identifying reason for an advice and/or reversal. |
| The network from which DPS acquired the transaction. Applicable only to debit card events. |
| The fallback indicator (Field #63.4, Position 5 from the ISO-8583 specification). Indicates whether the transaction was processed as magnetic stripe even though the card and terminal are EMV capable. Applicable only to debit card events. |
| The special transaction indicator (Field #63.7, Position 1 from the ISO-8583 specification).
|
| 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.
|
| Transaction eligibility for Partial Authorization Indicator (Field #63.7, Position 3 from the ISO-8583 specification).
|
| The amount of the transaction that caused this event. |
| The amount of the mobile check deposit that was approved by the bank. Applicable only to mobile check deposit events. |
| The date the mobile check deposit was approved by the bank. Applicable only to mobile check deposit events. |
| The date the funds associated with the transaction were applied to the |
| The |
| The presence of the card holder at the time the transaction was originated. Valid values include:
|
| The card associated with the transaction. Applicable only to debit card events. |
| The presence of the physical card at the time the transaction was originated. Valid values include
|
| The amount of cash the end user received during a debit card withdrawal at a non-ATM device. Applicable only to debit card events. |
| The amount of cash deposited by the transaction. Applicable only to debit card events. |
| The amount of the check deposited by the transaction. Applicable only to debit card events. |
| The amount of the mobile check deposit that was submitted. Applicable only to mobile check deposit events. |
| The unique ID of the client with which the line item is associated. |
| A notation applied by Helix employees internally containing any special extra information about the transaction. Very rare. |
| GUID correlation identifier for tracking |
| (Field #60.2 - Advice Reason Codes, Position 1, from the ISO-8583 specification) |
| Tag of the card control that was evaluated against this authorization. Via IsoMessage.CardControlId. |
| Tag of the rule that matched this authorization. Via IsoMessage.CardControlRuleId. |
| The unique identifier for the customer in Helix that caused this event. |
| The date the transaction was first created in Helix. |
| Source of the rule that matched this authorization. |
| Result of executing the matched card control rule. |
| Program's result for In Auth processing |
| |
| |
| A property for holding client-defined data. There is no business logic in Helix for a custom field |
| A caller-specified, freeform value assigned to this particular transaction. |
| Helix's result for In Auth processing |
| Helix's timing for program's In Auth processing time |
| Indicator to identify transactions initiated via a contactless acceptance solution referred to as Tap to Phone that allows current-generation connected devices, such as smartphones and tablets to accept contactless card-present payments. |
| Indicator to identify a card lock state. |
| The reason the lock was applied to the card. |
| The type of lock applied to the card. |
| The date of the most recent interaction with the customer. |
| The Visa DPS Original Transaction Identifier |
| A value that indicates the degree of risk associated with the transaction. Higher values are more likely to be fraudulent. |
| Text describing why a transaction was denied from taking place. Applicable only to debit card events. |
| Identification of the risk factor. |
| A caller-specified description of the transaction that caused this event. Will be automatically filled with relevant data if transaction resulted from ACH or debit card activity. |
| Fraud condition indicator |
| Additional Fraud condition indicator |
| Fraud condition score reason |
| Program's reason code for an In Auth processing result |
| Identifies the business customer performing card transactions on a business account with multiple cardholders |
| Risk Services Manager (RSM) rule id that was applied which resulted in a debit card transaction decline. |
| The currency used in transaction amount and fee amount; conntains a code defining the local currency of the acquirer or source location of the transaction |
| Funds requested by the cardholder in the local currency of the acquirer or source location of the transaction, not including transaction fee amount |
| Amount to be transferred between the acquirer and the issuer |
| The factor used in the conversion from the transaction amount to settlement amount set by the acquirer. |
| Date and time the request was submitted |
| Identifies the type of card issuance
|
| Identifies the acquiring institution’s institution identification code (IID). |
| Identifies the version and authentication method
|
| IP address of the browser as returned by the hypertext transfer protocol (HTTP) headers to the 3D Secure (3DS) requestor |
| IP address that is the device public IP address used by the 3DS requestor application when it connects to the 3DS requestor environment |
| Identifier linked to a device that is consistent across 3DS transactions for the specific user device |
| Indicates device type. Valid values include:
|
| |
| |
| |
| |
| |
| The programmatic value for the type of fee this transaction represents. Valid values include:
|
| A human-readable description of the |
| A human-readable, automatically generated description of the transaction that caused the event. Driven by the |
| The unique identifier for the customer account that was debited. |
| Total balance of the customer account that was debited, after the debit was applied, including funds that have holds placed on them. Represents all settled transactions to date. |
| Masked version of the Account number of the customer account that was debited. e.g. |
| Balance available for immediate withdrawal from the customer account that was debited after the debit was applied. |
| The caller-specified category to which the customer account that was debited belongs. |
| Date the customer account was created. |
| A caller-specified, freeform value assigned to the customer account that was debited. |
| A caller-specified, freeform value assigned to the customer account that was debited. |
| A caller-specified, freeform value assigned to the customer account that was debited. |
| A caller-specified, freeform value assigned to the customer account that was debited. |
| A caller-specified, freeform value assigned to the customer account that was debited. |
| The first legal name used to identify the customer account that was debited. |
| The second legal name used to identify the customer account that was debited. |
| A caller-specified, user-friendly name for the customer account that was debited. |
| Balance of pending deposit transactions on the customer account that was debited, after the debit was applied. |
| Denotes the customer considered the primary owner for the account that was debited. |
| The caller-specified subcategory to which the customer account that was debited belongs. |
| A caller-specified, unique identifier for the customer account that was debited. |
| The amount the customer wants the fromAvailableAmount to reach on the account that was debited. |
| The date the customer would like the fromTargetAmount to be reached on the account that was debited. |
| The first date the availableAmount reached or exceeded the fromTargetAmount on the account that was debited. |
| The unique identifier for the customer in Helix impacted by this event. |
| |
| The name of the institution from which the transaction originated. Rarely contains data. |
| |
| Indicates the last mode of communication used to contact the customer. Valid values include: |
| The unique identifier created by Helix used to group related transactions together that caused this event. |
| The city of the merchant at which the transaction originated. Applicable only to debit card events. |
| The two-character country abbreviation of the merchant at which the transaction originated. Applicable only to debit card events. |
| A grouping of multiple Merchant Category Codes into fewer, more useful sets. Applicable only to debit card events. See Merchant Group Codes for more information. |
| The identification code of the merchant that accepted the card information. Applicable only to debit card events. |
| The location of the merchant at which the transaction originated. Applicable only to debit card events. |
| The two-character state abbreviation of the merchant at which the transaction originated. Applicable only to debit card events. |
| The postal code of the merchant at which the transaction originated. Applicable only to debit card events. |
| The |
| The id of card's network provider.
|
| The method by which the card number was input to the merchant's device. Valid values include:
|
| Conditionally sent by the acquirer.
|
| The "type" of payload in the |
| The method by which the card holder was validated at the merchant's device. Valid values include
|
| Indicates successful PIN validation. Applicable only to debit card events. |
| |
| The amount of the purchase for the transaction. Applicable only to debit card events. |
| The unique identifier of a mobile check deposit record. Applicable only to mobile check deposit events. |
| The date the mobile check deposit was rejected by the bank. Applicable only to mobile check deposit events. |
| The reason the mobile check deposit was rejected by the bank. Applicable only to mobile check deposit events. |
| The method of request from the debit rails. Valid values include:
|
| Visa DPS response code to Risk Factor message. Valid values include:
|
| The ACH-specified return code applied to the transaction. |
| The date the funds associated with the transaction were applied to the |
| The date the mobile check deposit was originally submitted by the customer. Applicable only to mobile check deposit events. |
| A human-readable description of the subcatgorization of the |
| A programmatic subcategorization of the |
| The amount of surcharge applied to the tranasaction amount. For instance, if the |
| A caller-specified unique value to represent the transaction that caused this event. |
| The identification code of the device at the merchant that accepted the card information. Applicable only to debit card events. |
| Location of the merchant's device in relation to the merchant's location. Valid values include:
|
| Valid values include:
|
| Total balance of the customer account that was credited, after the credit was applied, including funds that have holds placed on them. Represents all settled transactions to date. |
| The unique identifier for the customer account that was credited. |
| Masked version of the Account number of the customer account that was credited. e.g., |
| Balance available for immediate withdrawal from the customer account that was credited after the credit was applied. |
| The caller-specified category to which the customer account that was credited belongs. |
| Date the customer account was created. |
| A caller-specified, freeform value assigned to the customer account that was credited. |
| A caller-specified, freeform value assigned to the customer account that was credited. |
| A caller-specified, freeform value assigned to the customer account that was credited. |
| A caller-specified, freeform value assigned to the customer account that was credited. |
| A caller-specified, freeform value assigned to the customer account that was credited. |
| The first legal name used to identify the customer account that was credited. |
| The second legal name used to identify the customer account that was credited. |
| A caller-specified, user-friendly name for the customer account that was credited. |
| Balance of pending deposit transactions on the customer account that was credited, after the credit was applied. |
| Denotes the customer considered the primary owner for the account that was credited. |
| The caller-specified subcategory to which the customer account that was credited belongs. |
| A caller-specified, unique identifier for the customer account that was credited. |
| The amount the customer wants the toAvailableAmount to reach on the account that was credited. |
| The date the customer would like the toTargetAmount to be reached on the account that was credited. |
| The first date the availableAmount reached or exceeded the targetAmount on the account that was credited. |
| The unique identifier created by Helix for the particular transaction that caused this event. |
| |
| |
| A human-readable representation of the type of transaction that caused this event. |
| Programmatic value for the type of transaction that caused this event. See the |
| The version of the payload in the |
| The Set card risk factors requestID provided in the 200 response. The |
| The date the transaction was voided in Helix. |
Updated 17 days ago