ATM/Debit/Credit Activity Inquiry (2)

Description

The last four digits of the card associated with the transaction

The relationship account associated the card

Normally used with ATM cards, where the credit union utilizes the member’s account number as part of the PAN. This differentiates between two or more cards with the same PAN for processing purposes. (May or may not be used)

These are the names embossed on the card for Line 1 and Line 2.

Type of transaction, whether the member used a PIN number or whether they signed for authorization.

The initial request from the vendor. (Numeric code followed by text description )

How does this affect ATM/Debit card processing? (An AnswerBook item will open when you click on this link.)

CU*BASE response to the request for information for the original message type. (Numeric code followed by text description)

• NOTE: Keep in mind that an “Advice” means that CU*BASE has performed a required action (force post) versus a “Request” means that the vendor is asking CU*BASE whether the action can be performed.

Last response sent to the vendor base on Original message type. (Numeric code followed by text description)

How does this affect ATM/Debit card processing? (An AnswerBook item will open when you click on this link.)

CU*BASE response to the request for information for the last message type.

(Numeric code followed by text description)

• NOTE: Keep in mind that an “Advice” means that CU*BASE has performed a required action (force post) versus a “Request” means that the vendor is asking CU*BASE whether the action can be performed.

The Processing Code contains a series of alphanumeric characters used to describe the effect of a transaction on the customer account and the accounts affected.

When looking at the new ATM/Debit Activity screen what is the Process Code and how does it affect how member's transaction is being processed on CU*BASE? (An AnswerBook item will open when you click on this link.)

(Numeric code followed by text description)

• The first two positions are the origination of the transaction, the second two digits are the From: account type, and the last two digits (other than zero) are the To: account type.

Account Types are defined as:

10  Savings

20 DDA - Checking

30 LOC - Credit Card transaction

The local date and time when the member made the transaction. This date may reflect a time zone difference. For example a transaction time might be a Mountain Standard Time (MST) while CU*Answers, for example, is Eastern Standard Time (EST).

The date the transaction posted to the members account.

If the member has ODP and/or ANR available and your credit union configuration allows for a member to utilize ODP and/or ANR for approvals, this indicates the time the authorization request came into CU*BASE whether ODP and/or ANR was used to approve the transaction.

Yes- Approved utilized and approved

No – Not used or not configured

Yes – Denied (considered for approval but insufficient funds were available)

Use the lookup for a view only look at the credit union configuration for ODP/ANR. This is helpful to tell what parameters the credit union allows.

The associated CU*BASE account and suffix related to this transaction

The associated CU*BASE account and suffix related to this transaction. This is generally used with a transfer (ATM).

Available balance of the account at the time of the authorization request

Description

The original amount requested

The amount requested plus any charges (i.e. an ATM charge)

The amount of any surcharge assessed at an ATM machine (i.e. charge for use of machine)

The actual amount posted to the member’s account

Also known as International Service Assessment of foreign conversion fees. This fee might be charged, for example, if the member’s transaction is done in a foreign country and a monetary conversion is needed.

A fee the credit union may charge for use of the card. The credit union service charge configuration determines whether or not this charge should be assessed to the member. (For example this might be charged when the member exceeds the number of free transactions.)

Use the lookup to view a view-only version of the credit union’s configuration of its service charge group associated with this card.

The Posting Status Indicates the State of the Posting Transaction.

(blank) = waiting to be posted (pending)

S = Posted while in Stand-In (during EOD/BOD)

A= Posted Successfully In Active Mode (not during Stand-In mode)

Location and or merchant description according to Reg E standards
(as much as can be displayed). This is also what member sees on statement.

• This is displayed according to Reg E for ATM and Debit Card transaction descriptions. For Signature type transactions, the requirement of the Reg is to display the name and address of the place the transaction was performed.  (This information is provided by the vendor. ) For POS transactions, the requirement is to display the address of the location of the place the transaction was performed.  For all other third party transactions, for example Account-to Account (A2A) transactions or EDB, the Reg requires that this field display the phone number. 

Member Transaction Generated

Posted amount to member’s account

The running balance on the account after this transaction was posted

Account base and suffix that the transaction was posted to

Offset G/L associated with the transaction

The date when the transaction hit the credit union’s books on CU*BASE. 

• Learn more about business date

The date the transaction happened.  

• Learn more about activity date

The time the activity happened.  Refer to Activity date above.

CU*BASE transaction description

CU*BASE transaction sequence number

Additional Network Information

Four character ID used by CU*BASE to identify the vendor

Type of BIN associated with the card

• Use the lookup to view a view-only version of the BIN configuration

Unique transaction identifier sent from the merchant to identify this transaction

• Not all merchants make this unique and it is not enforced by the vendor

The ISO Message Authorization ID used in a pre-approval and in matching holds with completions so they are released properly.

A unique Activity/Event Sequence number that is assigned to group a set of ISO Messages. An Activity Record is created for one unique ISO Event. It keeps track of the activity against this event, which can be made up of one or more Incoming ISO transactions.

A sequential Transaction number is assigned to each Event that results in posting to the Member’s account. Normally, there is one Transaction per Event, however multiple transactions could occur when there is a reversal, over/under dispense, and a Pre-authorizations followed by a Financial Advise.

A Unique ISO Message Sequence number assigned by CU*BASE that points to the Incoming Message that created a Unique ISO Activity/Event Record.

The ISO Sequence Number on the Activity/Event Record points to the first in a group of ISO messages that belongs to this Record. The ISO Sequence number on the Transaction Record points to the ISO Message that caused the posting.

Message Trace or Audit Number of the Message sender (ISO BIT011)

Message Codes are generated to communicate the status of the posting event. The code lets CU*BASE know whether or not the posting was successful and if a warning or abnormal condition occurred. The Description of the code resides in a file that contains ISO Response/Message meanings.

The Link between the CU Transactions and the ISO files. The format is

VVVAAAAAAAAA TTT where VVV = 3 char Vendor Code, AAAAAAAA = Unique Activity Sequence Number and TTT = Activity Transaction Number. This link was designed to be able to view all the CU*B transactions generated by the ISO Posting, i.e., including Back End Fees.

ATM network used to process the transaction

Identifies ATM terminal the transaction where the transaction was performed. May not be present on all transactions

The maintenance Date/Time is updated every time the Event/Activity record is changed.

• The Date/Time is updated when the Event is Added to the system and updated each time additional activity occurs against the Event, e.g., when addition Incoming Messages come thru the switch and when the posting occurs to the Members account.

The name of the program that last updated the Event/Activity record.

• NOTE: Normally the value will indicate the Message Approval Module (PISAPR2) or the Posting Module (PISPST1).

The maintenance Date/Time is updated every time the Event/Activity record is changed.

• The Date/Time is updated when the Event is Added to the system and updated each time additional activity occurs against the Event, e.g., when addition Incoming Messages come thru the switch and when the posting occurs to the Members account.