Table 62. Parameters for Global Payment Configuration
|
|
Payee DDNs |
Select the application DNN that you defined on the Main Console for use with your Self-Service application. In the Command Center, an application is also referred to as a payee Data Definition Name (DDN). |
Payment Payee Account Plugin Implementation |
Select com.edocs.common.payment.plugin.DefaultPayeeAccountPlugin or select Custom if you're using a custom plugin. |
Gateway Account Plugin Implementation |
If you are supporting more than two gateway accounts based on convenience fee type or billing account type, choose the Custom plugin type, then specify the (customized) IGatewayAccountPlugin plug-in. Otherwise, use the default. For the main transaction, the default implementation gets the gateway account with the type MAIN_TRANSACTION_ACCOUNT, and for the fee transaction it gets the account with the type FEE_TRANSACTION_ACCOUNT. |
Payment Notification Service Implementation |
Always select com.edocs.common.notification.payment.ConsolidatedPaymentNotificationService' class. |
DDN for External Payment |
This field is for use with the DDN for external payments feature. It is possible to use multiple payee bank accounts for the biller application. For help using the DDN for external payments feature, contact your Oracle sales representative to request assistance from Oracle's Professional Services. Otherwise, leave as the default value. |
Enable Payment Reminder Audit |
Selecting Y causes any actions that affect the PAYMENT_REMINDERS table to be audited. These actions can be from the Web application or from the payment jobs. The value N disables auditing. The default is N. |
Enable Bill Summary Audit |
Selecting Y causes any actions that affect the PAYMENT_BILL_SUMMARIES table to be audited. These actions can be from Web application or from the Payment jobs. The value N disables auditing. The default is Y. |