Property Glossary
Each event payload type can contain different properties. The table below defines properties that could appear in payloads.
Property Glossary
Property Name | Meaning |
---|---|
| The country where the acquiring institution is located. Applicable only to debit card events. |
| The network from which DPS acquired the transaction. Applicable only to debit card events. |
| The originator of the financial advice. Applicable only to debit card events. |
| 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. Possible values:
|
| 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. Possible values:
|
| 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. |
| A notation applied by Helix employees internally containing any special extra information about the transaction. Very rare. |
| The unique identifier for the customer in Helix that caused this event. |
| The date the transaction was first created in Helix. |
| A caller-specified, freeform value assigned to this particular transaction. |
| Text describing why a transaction was denied from taking place. Applicable only to debit card events. |
| 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. |
| 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 programmatic value for the type of fee this transaction represents. Possible values:
|
| 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 amount of gratuity applied in the transaction. Applicable only to debit card events. |
| The name of the institution from which the transaction originated. Rarely contains data. |
| Indicates whether the transaction is single or multi-currency. Applicable only to debit card events. |
| The unique identifier created by Helix used to group related transactions together that caused this event. |
| 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 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. |
| 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 four-digit message type identifier from the original request message. Applicable only to debit card events. |
| The |
| 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 method by which the card number was input to the merchant's device. Possible values:
|
| The eligibility of the transaction for partial authorization. Applicable only to debit card events. |
| The "type" of payload in the |
| The method by which the card holder was validated at the merchant's device. Possible values:
|
| 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. Possible values:
|
| The two-digit status code from the original request message. Applicable only to debit card events. |
| The Retrieval Reference Number as defined by the network provider. Applicable only to debit card events. |
| The ACH-specified return code applied to the transaction. |
| The date the funds associated with the transaction were applied to the |
| The special processing considerations for the transaction. Applicable only to debit card events. |
| 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 |
| The System Trace Audit Number as defined by the network provider. Applicable only to debit card events. |
| 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. Possible values:
|
| Possible values:
|
| 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 date the transaction was voided in Helix. |
Updated 4 months ago