CC Amex Batch Transaction UML


Added On:  02/13/12 
SQL Table:  CC_AMEX_BATCH_TRANSACTION 
Module:  UniCharge 
Type:  Entity  Status:  Active 
Java Class:  CcAmexBatchTransaction 
Entity that represents a batch transaction as it is defined in batch processing specification of Amex.
Added On:  02/13/12
SQL Column:  CARD_UPDATE_FLAG
Java Field:  cardUpdateFlag
Status:  Active
SQL Type:  varchar(1)
Java Type:  String
Attributes:
This field contains the Card Update Flag:

Y = Cardmember Number-related data has changed. Merchant should call customer to get new/updated Card information.

Character space = Cardmember Number data has not changed.

If unused, this field must be character space filled.
Added On:  06/09/16
SQL Column:  
Java Field:  cardmemberNumber
Status:  Active
SQL Type:  
Java Type:  String
Attributes: Transient
Added On:  02/13/12
SQL Column:  CC_AMEX_BATCH_FK
Java Field:  ccAmexBatch
Status:  Active
SQL Type:  bigint(20)
Java Type:  Long
References CC Amex Batch
Attributes:
Reference to the entity that represents credit cards Amex Batch file.
Added On:  02/13/12
SQL Column:  CHARGE_DESCRIPTION
Java Field:  chargeDescription
Status:  Active
SQL Type:  varchar(23)
Java Type:  String
Attributes:
This field contains a description of the purchase associated with the charge.
Descriptors are provided by the merchant, and they should accurately describe the merchant’s type of business, product or service sold, or department name.
Added On:  06/09/16
SQL Column:  CHARGE_TRANSACTION_FK
Java Field:  chargeTransaction
Status:  Active
SQL Type:  bigint(20)
Java Type:  Long
References Charge Transaction
Attributes:
Reference to the entity that represents real-time financial transaction.
Added On:  02/13/12
SQL Column:  DESCRIPTION1
Java Field:  description1
Status:  Active
SQL Type:  varchar(40)
Java Type:  String
Attributes:
These free-form text field may be used to provide supplemental descriptive information associated with the charge.
Added On:  02/13/12
SQL Column:  DESCRIPTION2
Java Field:  description2
Status:  Active
SQL Type:  varchar(40)
Java Type:  String
Attributes:
These free-form text field may be used to provide supplemental descriptive information associated with the charge.
Added On:  02/13/12
SQL Column:  DESCRIPTION3
Java Field:  description3
Status:  Active
SQL Type:  varchar(40)
Java Type:  String
Attributes:
These free-form text field may be used to provide supplemental descriptive information associated with the charge.
Added On:  02/13/12
SQL Column:  ID
Java Field:  id
Status:  Active
SQL Type:  bigint(20)
Java Type:  Long
Identifier / Primary Key
Attributes: Unique, Required
Identifier of the object used for references; auto-incremented integer value.
Added On:  02/13/12
SQL Column:  MERCHANT_ACCOUNT_CODE
Java Field:  merchantAccountCode
Status:  Active
SQL Type:  int(11)
Java Type:  Integer
Attributes: Required
Code of Merchant Account to which instance of this object is attributed to. Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.
Added On:  02/13/12
SQL Column:  MERCHANT_CUSTOMER_SERVICE_NUMBER
Java Field:  merchantCustomerServiceNumber
Status:  Active
SQL Type:  varchar(15)
Java Type:  String
Attributes:
Phone number of the merchant customer support for discussing any processing issues.
Added On:  02/13/12
SQL Column:  PARTNER_CUSTOMER_NUMBER
Java Field:  partnerCustomerNumber
Status:  Active
SQL Type:  varchar(22)
Java Type:  String
Attributes:
This field contains a unique, merchant-designated customer number that is assigned to Cardmembers who pay recurring bills with an American Express Card.
The Partner Customer Number is directly related to the American Express or American Express-supported Card account number (a.k.a. Cardmember Number) and is the primary key to other Cardmember data entered and/or stored in the Automated Bill Payment Platform (ABPP) enrollment database.
The Partner Customer Number is used to cross-reference charge details in Transaction Advice Basic (TAB) Records to Cardmember enrollment information in the ABPP database.
Added On:  02/13/12
SQL Column:  REFERENCE_NUMBER
Java Field:  referenceNumber
Status:  Active
SQL Type:  varchar(9)
Java Type:  String
Attributes:
If used, this field contains a reference number that is utilized by American Express to obtain supporting information on a charge, from a merchant. Supporting documentation should be readily available in case of inquiry.

This number can be any combination of characters and numerals defined by the merchant or authorized processor. However, it must be an index to the merchant’s record, so that charge information can be readily retrieved and promptly submitted within 10 calendar days (or within the period stipulated in the contractual agreement).

If unused, this field must be character space filled.
Added On:  02/13/12
SQL Column:  RESPONSE_CODE
Java Field:  responseCode
Status:  Active
SQL Type:  varchar(6)
Java Type:  String
Attributes:
In Billing Response Files, this field contains an ABPP Response Code that indicates the status of this record, from the original Billing File submission.

If transaction was approved/authorized, code C0000 is returned. Receipt of any other code indicates that this transaction was rejected.

If unused, this field must be character space filled.
Added On:  02/13/12
SQL Column:  ROC_NUMBER
Java Field:  rocNumber
Status:  Active
SQL Type:  varchar(10)
Java Type:  String
Attributes:
This field may contain the original Record of Charge (ROC) invoice, or another number associated with the charge.

If the REFERENCE_NUMBER field is used, then the ROC_NUMBER field may be character space filled, unless otherwise stipulated in your contract with American Express.
Added On:  02/13/12
SQL Column:  TAX_AMOUNT
Java Field:  taxAmount
Status:  Active
SQL Type:  varchar(15)
Java Type:  String
Attributes:
If used, this field contains the tax amount applicable to this transaction, in the currency that corresponds to the Service Establishment Number in the Transaction Batch Header (TBH) Record for this batch. All TAB Record tran-saction and tax amounts, and TBT total amounts, in a batch must be in the same currency.

If unused, this field must be zero filled.
Added On:  02/13/12
SQL Column:  TRANSACTION_AMOUNT
Java Field:  transactionAmount
Status:  Active
SQL Type:  varchar(15)
Java Type:  String
Attributes:
This field contains the total transaction amount (including tax), in the currency that corresponds to the Service Establishment Number in the Transaction Batch Header (TBH) Record for this batch. All TAB Record transaction and tax amounts, and TBT total amounts, in a batch must be in the same currency.

The maximum value that can be entered in this field is “000000009999999”, regardless of currency.
Added On:  02/13/12
SQL Column:  TRANSACTION_DATE
Java Field:  transactionDate
Status:  Active
SQL Type:  varchar(8)
Java Type:  String
Attributes:
This field contains the date that the transaction took place. This becomes part of the descriptive bill on the Cardmember’s statement.
The format is: YYYYMMDD
Added On:  02/13/12
SQL Column:  TRANSACTION_TYPE_ID
Java Field:  transactionTypeId
Status:  Active
SQL Type:  varchar(2)
Java Type:  String
Attributes:
Contains a code that indicates whether this transaction is a purchase debit or a purchase credit.

Valid entries include:
05 = Debit
06 = Credit