Class WSAddendaTransaction

---

Properties

NAME	TYPE	LENGTH	REQUIRED	DESCRIPTION
EntityId	int		Y	Unique identifier that is generated by EPS. (See - Required Data Elements)
LocationId	int		Y	Unique identifier generated by EPS for each location. (See - Required Data Elements)
PaymentOrigin	enum of Type WSPaymentOrigin		Y	Identifies by what method the transaction was originated.(See - Optional Data Elements & PaymentOrigin Element Relationships) Valid values are: Signature_Faxed Signature_Original Corporate_Trade_Exchange
AccountType	enum of Type WSAccountType			Valid values are: Checking Savings If Null and the RoutingNumber element is supplied, the default value of ‘Checking’ is used. for handling of Checking or Savings accounts (See - Optional Data Elements)
OperationType	enum of Type WSOperationType			Valid values are: Sale Credit SDCredit (See - Special Requirements for rules) SDSale (See - Special Requirements for rules) Reversal If null, the default value of ‘Sale’ is assumed. (See - Optional Data Elements)
SettlementType	enum of Type WSSettlementType			Valid values are: ACH None If null, the default value of ‘ACH’ will be assumed. (See - Optional Data Elements)
TransactionStatus	enum of Type WSTransactionStatus			Do NOT include this element in your request. The appropriate value will be set by EPS.
SettlementStatus	enum of Type WSSettlementStatus			Do NOT include this element in your request. The appropriate value will be set by EPS.
EffectiveDate	dateTime			Date and time of the transaction. If null, the current date and time is assumed. NOTE: This element does not require the Time to be included. (See - Optional Data Elements)
Description	string	50		This optional element can be used to define or explain the purpose of this transaction.
TotalAmount	decimal		Y	Dollar amount of the transaction. This element cannot be zero (0) or negative.
BatchNumber	string	40		Supply only if a unique userassigned batch number was created using CreateProcessingBatch and the user wants to include this transaction in that batch. If not, leave it blank or don’t include it in the request.
TerminalNumber	string	20		The default value for terminalNumber is ‘__WebService’. (See - Optional Data Elements)
TransactionNumber	string	50	Y	Unique user-assigned identifier of the transaction being created.
Field1	string	50		Optional information associated with the transaction. Data is stored with the transaction. Indexed field.
Field2	string	50		Optional information associated with the transaction.
Field3	string	50		Optional information associated with the transaction. NOTE: If isHealthcareClaimPmt is set to ‘True’, any data entered this field will be truncated to the first 46 characters.
RoutingNumber	string	9	Y	Bank Routing/Transit or ABA number. (See - PaymentOrigin Element Relationships)
AccountNumber	string	17	Y	This element represents the customer’s account number. Checking or Savings accounts: 417 digits. (See - PaymentOrigin Element Relationships)
CheckNumber	string	17		Check serial number
IsBusinessPayment	bool			Should always be ‘1’ (True)
NameOnAccount	string	50	Y	Customer’s name as it appears on their account.
IPAddressOfOriginator	string	15		IP address of person sending request.
NotificationMethod	enum of Type WSNotificationMethod			Method by which a merchant’s customer will be notified of an ACH or Credit Card transaction. Valid values are: Merchant_Notify Merchant_Recording Postcard Email If null, the default value ‘Merchant_Notify’ is assumed.(See - Optional Data Elements)
FaceFeeType	enum of Type WSFaceFeeType			Valid values are: __None Face Bill_Convenience_Face NSF_Fee Bill_Convenience_Fee If set to‘__None’ or Null, the default value ‘Face’ will be used. (See - Optional Data Elements)
OwnerApplication	enum of Type WSOwnerApplication			Valid Value is: Web_Service Can be Null; can’t be empty (See - Optional Data Elements)
IsHealthcareClaimPmt	bool			Valid values are: 1 (True) or 0 (False). Used for CCD+ transactions only to identify a Healthcare Claim Payment. NOTE: If this flag is checked, then EPS will insert the text “HCClaimPmt” in the Company Entry Description positions in the origination file.(See Field3 Note)
Addenda	String[]	80		A CTX transaction can have up to 9,999 addenda records; CCD+ transactions (including Healthcare Claim Payments) are limited to a single (1) addenda record.