Administrator Configurations

Administrators play a very vital role in the initial configuration for security and online payment. The following configuration points are the primary ones to enable online payment.

Security

A new Security Role ID CSS_READ has been delivered for the CSS Role, which can be used or another can be created. That role is connected to the following Resource Groups: ACCTSUM, AMTDUE, BATCH, INT_JOB, INVDUE, and INVPAID. These are the groups for the delivered widgets along with INT_JOB to create a cash receipt for payment. Please note that the details of each Access Control record needs to be reviewed. Also, ensure that the Resource ID Financial Jobs is part of Resource Group ID INT_JOB.  If defined to another group, then that group needs to be associated with CSS_READ.

For the ALERTWIDGET (500364) widget to be used, add the Resource Group ID of ALRT to the Security Role ID of CSS_READ. The payment gateway now supports both Stripe and PayPal methods. To process payments through either option, the user must configure the respective account.

Payment

The steps to configure payment through Stripe are as follows:

  1. Create/Sign Up a Stripe account from https://stripe.com/.

  2. Activate the account and link bank details.

  3. Get ClientKey and ClientSecretKey once the account is activated.  Refer to this URL for reference: Locate API keys in the Dashboard: Stripe: Help & Support and refer to the Stripe setup reference URLs: https://support.stripe.com/topics/getting-started and https://stripe.com/docs/payments/account.

Currently, the only supported payment type for Stripe is credit card. Other payment methods such as Amazon Pay, Affirm, and similar options, even if enabled in Stripe, are not supported.

  1. Update the stripe.conf file in Custom/Configuration/AppConfig/VLSEnv/fin/VLS/bin/adv__conf as indicated below

Example:

# stripe configuration

stripe {

# enabled or not

enabled=true

}

  1. Certification setup: Download the certificates mentioned in https://stripe.com/docs/tls-certificates.

  2. Import all the downloaded certificates into ADV3.keystore present in the RTFiles folder.

  3. Restart/Bounce the application to make the changes effective.

The steps to configure payment through PayPal are as follows:

  1. Create/Sign Up a PayPal account from https://PayPal.com/.

  2. Activate the account and link bank details.

  3. Get ClientKey and ClientSecretKey once the account is activated.  Refer to this URL for reference: Locate API keys in the Dashboard: PayPal: Help & Support and refer to the PayPal setup reference URLs: https://support.PayPal.com/topics/getting-started and https://PayPal.com/docs/payments/account.

The system supports all available PayPal payment options, including PayPal, Pay Later, debit card, and credit card payments.

  1. Update the PayPal.conf file in Custom/Configuration/AppConfig/VLSEnv/fin/VLS/bin/adv__conf as indicated below.

Example:

# stripe configuration

stripe {

# enabled or not

enabled=true

  1. Restart/Bounce the application to make the changes effective.

There are additional steps to configure Stripe and PayPal, once activated, on the Payment Configuration (PAYCNFG) page:

  1. Enter a Payment Type ID.

  2. Select the Payment Type: Stripe or PayPal.

  3. Enter the Client Key (received upon activating the payment account).

  4. Enter the Client Secret Key (received upon activating the payment account).

Additionally, these steps are configured for Stripe and PayPal on the Financial Payment Configuration (FPAYCNFG) page:

  1. Select the Payment Type ID from the picklist.

  2. The Payment Type is automatically inferred.

  3. Enter a Department if the payment account is not available site-wide with the wildcard of ALL.

  4. Enter a Unit if the payment account is not available site-wide or to all units within a department with the wildcard of ALL.

  5. Enter the Accounting Template used for collection.

  6. Enter the Event Type used for collection.

  7. Enter the Service Charge Line Description.

Configuring a common Accounting Template, Event Type, and Service Charge Line Description is recommended when different combinations of departments and units share the same Payment Type ID. The Service Charge Line Description is used as the line description in the new accounting line of the Cash Receipt (CR) transaction for the service fee once the payment is completed. In the case of bulk payments, if multiple service charge line descriptions are configured, the system sorts them and selects the first available record with a valid service charge line description.

The ability to make payments for multiple invoices is enabled only when at least one of the following conditions is satisfied. If none of these conditions are met, the option is disabled:

  • The Payment Type ID, Accounting Template, and Event Type stay consistent across different departments and unit combinations on Financial Payment Configurations. These details also remain consistent when the department and unit are set to ALL. 

  • The same payment method (Stripe or PayPal) is configured for all department and unit combinations using the same Payment Type ID. In this case, the common payment method is displayed during the payment process.

  • Both payment methods (Stripe and PayPal) can be configured for multiple department and unit combinations or set with ALL as the department and unit for the same Payment Type ID. In such cases, a prompt is presented during payment, allowing the user to choose the preferred payment method.

  • Multiple Payment Type IDs can be configured for the same department and unit combination. In this case, a prompt appears during payment, allowing the user to select the preferred payment method. When multiple Payment Type IDs are configured for the same department and unit combination under the same payment method, the system redirects to the first payment account after sorting in ascending order. When Payment Type IDs include both numbers and alphanumeric characters, the system prioritizes the numeric values during sorting.

Examples:

ID

Department

Unit

Accounting Template

Event Type

Service Charge Line Description

PayPal 2

DHA

DHA

DHA1

AR02

PayPal service fee 1

PayPal 1

DHA

DHA

DHA2

AR02

PayPal service fee 2

The system redirects to the first payment account after sorting, that is, PayPal 1, as per the example.