Table 63. Parameters for Configuring a Check Gateway
|
|
DDN |
The selected application DNN. |
Payment Type |
check |
Gateway |
ach |
Batch Size for Payment Reminder Table |
Specifies the number of payment reminders to be read into memory from the Oracle Billing Insight database for the pmtReminder job. Note that specifying a batch size that is too small increases the number of times the database is accessed, and specifying a batch size value that is too large could result in an excessive amount of memory being used. A batch size of 100 is suggested for a medium-sized database, and a batch size of 1000 is suggested for a large database. You can enter a batch size of zero to disable batched table reads, however, doing so requires a lot of memory. Entering zero means that one partition ID is created for all payments, and that all payments are processed at once instead of in batches. The resulting batch file does not have multiple batch records, which some banks prefer. |
Send Email Notification when Payment Jobs are Done (With or Without Error) |
The value Y enables and N disables sending of email about the status of the Payment jobs that support job status notification. Additional email information is specified in the following fields. |
Mail-to Addresses (Separated by ";" Semicolon) for Job Status Notification |
One or more email addresses that must be sent job status notification, separated by semicolons. |
JNDI Name of IAccount |
Implementation of IAccount, which must match the enrollment model, single or multiple DDNs for each user account, used by applications that use this payment gateway (DDN). Select the JNDI name edx/ejb/AdminAccount. |
Implementation of IUserAccountAccessor |
The name of the class that handles getting Oracle Billing Insight user information, which is determined by the type of enrollment supported. Select the class com.edocs.common.payment.plugin.DefaultUserAccountAccessor. |
Implementation of IPaymentAccountAccessor |
The name of the class that handles getting payment user information. Select the class com.edocs.common.payment.payenroll.payacct.DefaultPaymentAccountAccessor. |
Enable Convenience Fee Payments for End User |
Indicates whether to enable convenience fees in the Self-Service application: Y, Yes or N, No. |
Enable Convenience Fee Payments for CSR |
Indicates whether to enable convenience fees in the Assisted Service application: Y, Yes or N, No. |
Convenience Fee Configuration Class |
The name of the custom class for calculating the convenience fee. The default value is: com.edocs.common.payment.cassette.plugin.DefaultConvenienceFeeConfig. |
Include Convenience Fee in Refunds |
Indicates whether to refund the convenience fee. |
Batch Size for Check Payment Table |
The number of scheduled checks to read into memory from the payment database as a batch job. Note that specifying a batch size that is too small increases the number of database accesses, and specifying a batch size value that is too large might result in an excessive amount of memory being used. A batch size of 100 is suggested for a medium-sized database, and a batch size of 1000 is suggested for a large database. A batch size of zero can be entered to disable batched table reads, but it is not recommended because it requires a lot of memory. Entering zero means that one partition ID is created for all payments, and that all payments are processed together, instead of in batches. The resulting ACH file will not have multiple batch records, which some banks prefer. |
Batch Submit Transaction Time Out |
The number of minutes after which batch submit transactions time out. |
Number of Business Days After Pay Date to Clear the Check |
The number of business days for a check to be marked as paid after submitting to the payment gateway without returns or failures. The default is five business days. |
Days to Activate Pending Subscribers |
The number of business days to wait before approving a customer for online payment. If a prenote file is returned before this time, then the customer is rejected for the causes stated in the prenote file. The default is three days. |
Batch File Name Prefix |
The text used as a prefix to each batch file name. |
Batch File Name Time Stamp |
The format used for each batch file time stamp. |
Batch File Name Suffix |
The text used as a suffix to each batch file name. |
ACH Prenote File Name Prefix |
The text used as a prefix to each ACH prenote file name. |
ACH Prenote File Name Time Stamp |
The format used for each ACH prenote file name |
ACH Prenote File Name Suffix |
The text used as a suffix to each ACH prenote file name |
Update Payment Enrollment in Case of NOC |
The value Y causes the pmtCheckUpdate job to update enrollment status when a NOC is returned. The value N means this value is updated by the customer through the user interface |
Send Email Notification in Case of NOC |
The value Y sends email to customers whose payment returns a NOC. The value N means the customer does not receive email when a NOC is returned. |
Skip Non-Business Days for Batch Entry Effective Dates |
Whether batch effective dates skip U.S. Federal holidays and weekends. |
Generate an Empty ACH File if No Checks to Submit |
Whether the pmtCheckSubmit job generates an empty ACH file if there are no checks to submit. |
Immediate Destination |
The routing number of the Biller DDN. A routing number is assigned to you by your bank, and follows a format specified by the Biller's bank (ODFI). The pmtCheckSubmit job inserts this information into the ACH File Header record's Company Name field. The pmtCheckUpdate job uses this value to validate entries in the ACH return file. Must be exactly 10 characters in length and must start with a blank. The leading blank is counted as one of the 10 characters. |
Immediate Origin |
The routing number of the biller's bank (ODFI). A routing number is assigned to you by your bank. The pmtCheckSubmit job writes this information to the ACH file header record's Immediate Destination field. The pmtCheckUpdate job uses this value to validate entries in the ACH return file. Must be exactly 10 characters in length. The value assigned to you by your bank might have a leading blank. If the value is less than 10 characters in length, including the leading blank, if there is one, then you must pad the entry with trailing blanks to reach a total length of 10 characters. |
Immediate Destination Name |
The name of the Biller. This information is assigned to you by your bank, and follows a format specific to the needs of the ODFI. The pmtCheckSubmit job inserts this information into the ACH File Header record's Immediate Destination Name field. The pmtCheckUpdate job uses this value to validate entries in the ACH return file. |
Immediate Origin Name |
The name of the biller's bank (ODFI). This information is assigned to you by your bank, and follows a format specific to the needs of the ODFI. The pmtCheckSubmit job inserts this information into the ACH File Header record's Immediate Destination Name field. The pmtCheckUpdate job uses this value to validate entries in the ACH return file. |
ACH File Output Directory |
The directory where ACH files are created to be sent to the originating bank. Payment does not create this directory. |
ACH File Input Directory |
The directory where the originating bank sends ACH return files. Oracle Billing Insight does not create this directory. |
ACH Template File Directory |
The directory where the ACH XML files are stored. |
Implementation of IAchPlugIn |
The plug-in allows modification of whether a check payment is submitted, plus other actions dependent on a check selected for payment. For example, to generate a remittance file with a format different from the standard ACH file specification. For information about implementing this class, contact Oracle Professional Services. The default value of this parameter is com.edocs.common.payment.cassette.bank.ach.DefaultAchPlugin. |
Flexible Field 1 (for plugin) |
You can specify an additional field for the IAchPlugin plug in. |
Flexible Field 2 (for plugin) |
You can specify an additional field for the IAchPlugin plug in. |
