Class AuthorizeAcctVerifyMoneyCenterTransactionRequest
Properties
NAME | TYPE | LENGTH | REQUIRED | DESCRIPTION |
---|---|---|---|---|
storeId | long | Yes | Unique user ID generated by EPS. | |
storeKey | string | Yes | Unique password generated by EPS. | |
customerNumber | string | 50 | Yes* | This element is a unique identifier that references a specific customer (Payee). *It is required, along with the accountReferenceId element, if the AccountNumber is not provided in the request.(See - Optional Data Elements) |
accountReferenceId | string | 50 | Yes* | This element is a unique identifier that references a specific customer (Payee) account. *It is required, along with the customerNumber element, if the AccountNumber is not provided in the request.(See - Optional Data Elements) |
moneycenterTransaction | WSMoneyCenterTransaction | |||
holdDays | tinyInt | 1 | This is an optional element which defines the hold days at the transaction level. Possible values are
Note: This element cannot be empty or blank. You must provide a value of 255 or null if you don’t want to include hold days at the transaction level. The permission Create Transaction Hold Days (under the Customer Services Privilege) is required to apply hold days. This element is applicable for ACH Only |
WSMoneyCenterTransaction
NAME | TYPE | LENGTH | REQUIRED | DESCRIPTION |
---|---|---|---|---|
EntityId | int | Yes | Unique identifier that is generated by EPS. | |
LocationId | int | Yes | Unique identifier generated by EPS for each location | |
PaymentOrigin | WSMoneyCenterPaymentOrigin | Valid values are:
| ||
AccountType | WSMoneyCenterAccountType | Valid values are:
Note: If the AccountNumber is not provided, and accountReferenceId and customerNumber are, this value will be ignored.(See - Optional Data Elements) | ||
OperationType | WSMoneyCenterOperationType | Yes | Valid values are:
| |
EffectiveDate | dateTime | Date of the transaction. If null, the current date is assumed. | ||
Description | string | 50 | This optional element can be used to define or explain the purpose of this transaction. | |
TotalAmount | decimal | Yes | Dollar amount of the transaction. This element cannot be zero (0) or negative.(See - Same Day ACH Requirements) for rules. | |
BatchNumber | string | 40 | Use if processing transactions in a batch. | |
TransactionNumber | string | 50 | Yes | Unique user-assigned identifier of the transaction being created. This field can’t be Null or blank. |
Field1 | string | 50 | Optional information associated with the transaction. | |
Field2 | string | 50 | Optional information associated with the transaction. | |
Field3 | string | 50 | Optional information associated with the transaction. | |
RoutingNumber | string | 9 | Yes | Bank Routing/Transit or ABA number. |
AccountNumber | string | 17 | This element represents the customer's (Payee) account number. Checking or Savings accounts: 4-17 digits. | |
CheckNumber | string | 17 | ||
IsBusinessPayment | bool | yes | Identifies the ACH only transaction as either drawn on a business or personal account. Valid values are:
| |
NameOnAccount | string | 50 | Yes | Vendor's (Payee) name as it appears on their account. |
BillingStateRegion | string | 2 | Yes | The State/Region where this vendor (Payee) account is located. Examples of possible values are:
|
IPAddressOfOriginator | string | 15 | IP address of person sending request. | |
EmailAddress | string | 60 | Yes | Email address of Payor. |
Addenda | string[] | 80 | A CTX transaction can have up to 9,999 addenda records; CCD+ transactions are limited to a single (1) addenda record. |